Assuming you have a symlink setup in ./shared/images to point to ./current/public/images after each deploy, then you could add a task like you're suggesting, that simply exports the ./project/public/images directory from svn and pushes that into /shared/images on the server.
On Tue, Jul 1, 2008 at 12:35 PM, chris johnson <[EMAIL PROTECTED]> wrote: > > Hi all. > > I just came across the deploy:upload task: very cool. I need to be > able to push some image files up to our farm periodically, and would > prefer not to do a full deployment for each new image push. > > It seems like I can do something like the following: > cap deploy:upload FILES=public/images/ > > However, this seems like it would upload all images, which is > inefficient. Of course I could explicitly name each new image file I > want uploaded, but this is tedious. > > So... Is there a clean way for handling this situation? Ideally, it > would be something like the remote_cache strategy, only uploading new > images. Something like cap deploy:images would be lovely :-) > > Any direction here? > Thank you much. > -Chris > > > -- 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 -~----------~----~----~----~------~----~------~--~---
