Thanks for the response and clarification Jamis. That should do it. -Chris
On Jul 8, 4:24 pm, Jamis Buck <[EMAIL PROTECTED]> wrote: > deploy:upload does not create subdirectories for single-file uploads. > You'll want to manually create those first, e.g.: > > cap invoke COMMAND="mkdir -p /path/to/current/public/images/people/ > bob" > > And then the deploy:upload. > > - Jamis > > On Jul 8, 2008, at 5:11 PM, Anthony Ettinger wrote: > > > > > Yes, it does create the directories though. > > > On Tue, Jul 8, 2008 at 4:07 PM, chris johnson <[EMAIL PROTECTED]> > > wrote: > > >> No; these servers are mature and have had many cap deployments to > >> them > >> already. Isn't cap deploy:setup just for the initial setup? > > >> On Jul 8, 4:03 pm, "Anthony Ettinger" <[EMAIL PROTECTED]> wrote: > >>> Have you tried cap deploy:setup first? > > >>> On Tue, Jul 8, 2008 at 4:00 PM, chris johnson > >>> <[EMAIL PROTECTED]> wrote: > > >>>> Hi there. > > >>>> Just tried uploading a new image via the following cap command: > > >>>> cap deploy:upload FILES=public/images/people/bob/center.png > > >>>> Each server reports: "uploading failed: No such file" > > >>>> The /bob/ subdirectory does not exist on our servers, but I would > >>>> guess that the upload command would create the directory, no? If > >>>> not, > >>>> is there an option to force directory creation? Trying to upload > >>>> the > >>>> whole directory (as per below) yields the same results: > > >>>> cap deploy:upload FILES=public/images/people/bob > > >>>> Any answers? > >>>> Cheers. > > >>> -- > >>> Anthony Ettinger > >>> 408-656-2473http://anthony.ettinger.name > > > -- > > Anthony Ettinger > > 408-656-2473 > >http://anthony.ettinger.name > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
