Put the files in version control like git and use the standard deploy recipes. Then you can deploy anywhere without having to have an operation source directory.
On Aug 27, 2010, at 1:05 PM, joe <[email protected]> wrote: > I currently have a deploy file that works great when pushing a website > from one internal server (development) to another internal server > (staging). I now need to push from development to an external server > (production), but the production server is unable to talk to any of > our internal servers. > > This means I cannot be ssh'd into the production server and do > something like "scp u...@development:/path/to/website /path/to/ > production/website". > > Anyone have any suggestions on how to get around this? I also need to > push the database to a different server. Currently, my script does > everything with a single server but I know Capistrano is capable of > handling multiple servers for one application. > > Any ideas are greatly appreciated. > > Thanks, > > > Joe > > -- > * You received this message because you are subscribed to the Google Groups > "Capistrano" group. > * To post to this group, send email to [email protected] > * To unsubscribe from this group, send email to > [email protected] For more options, visit this group at > http://groups.google.com/group/capistrano?hl=en -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
