I don't need convincing, Patrick, I'm a confirmed Capistrano user on
projects where it was in place or I put it in place (except for
Heroku, which deploys via Git; Nick Zadrozny's suggestion about
tagging the Git branch so it can be found again easily could be useful there).
Now I must tell the client that the first thing I must do is spend
some hours on something that produces no visible benefit at all. I
did this on another project on a managed host (there wasn't even a
script, I guess they just copied files in) and it took quite a few
hours to get all the soft links and other stuff right and the tech
people to point Apache and other things to the new code location.
Blew their budget, but had to be done if I was going to continue to
work on the site.
Scott
At 12:13 PM 1/15/2010, you wrote:
You should definitely use Capistrano, Scott.
It's well-documented and can handle most deployments. And by
learning it now, you'll be able to apply that knowledge to future
Rails app deployments.
Trust me on this. Months from now... when you reflect on this thread
and realize how much time you've saved with Capistrano, you can buy
me a beer. ;)
-- Patrick
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
--
SD Ruby mailing list
[email protected]
http://groups.google.com/group/sdruby
