You can do just about anything with Capistrano. In your case, you would just have to customize (redefine) the default deployment tasks to handle your directory structure.
I typically just have an "after setup" tasks that copies my httpd configs, and what not, to the shared dir of the the deployment path, then creates sym links to them. - Jason On Dec 1, 2006, at 4:32 PM, stu wrote: > > Hi, > > When it comes to deploying Rails sites I've been enjoying having > Capistrano around to do predictable, repeatable deployments. > > The projects I'm working on typically have a whole bunch of > subdirectories containing scripts, cron jobs, logfiles, libraries, > various assets etc etc. One of those subdirectories is always a > project Rails site. > > I'd like to be able to deploy the whole project tree, including the > Rails subdirectory, but I'm wondering if Capistrano can be used in > that > way? > > Has anyone done anything similar to this with Capistrano? I'd welcome > any whole-project Capistrano experiences people on the list would be > willing to share. > > TIA, > > Stu > > > > --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
