Hi Joe,
Send a pull request to capistrano/capistrano.
Thanks
El 27/08/10 22:10, Patrick Reagan escribió:
Joe -
You don't say where your SCM is hosted (I'm assuming it's internal), but we
created a Capistrano deployment strategy that you might find useful:
http://github.com/vigetlabs/capistrano_rsync_with_remote_cache
http://rubygems.org/gems/capistrano_rsync_with_remote_cache
Even if this doesn't solve the problem for you, you might look to Rsync to do
the transfer.
I'd like to pull this into Capistrano proper at some point if there's interest.
p.
On Aug 27, 2010, at 2:05 PM, joe 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
--
Patrick Reagan<[email protected]>
--
Rafa
--
* 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
