Rails - Jan 2005 - [Maybe OT] One Button Deployment of Rails App

Has anyone set up a one button deployment system for their Rails app?

Say you''re developing a few sites for different clients.  You add a
feature, test it, and want to deploy the application.  How do you do
that?  I''d imagine that, at the very least, the config/database.yml
file needs to be changed for the life site.  And probably some other
stuff needs to be changed when the site goes live (or gets updated).

So, how do you do it?  What''s the Right(tm) way?  

I guess I''m also looking for some general admin tips.  A friend and I
are doing a couple Rails sites and I seem to be spending a lot of time
setting up Rails stuff, starting/restarting webrick, figuring out the
database situations on the testing and live servers, etc.  Any ideas?

Thanks,
Joe

I use a script which logs on the server using net::ssh, checks out the
latest version of the app from svn
in its own directory, runs all unit tests and if that works well it
symlinks the new directory to the docroot and restarts apache
gracefully.

Obviously its totally hardcoded for my environment but it might be
useful to you anyways...
http://rafb.net/paste/results/DyrvgY89.html


On Mon, 24 Jan 2005 17:01:26 -0800, Joe Van Dyk
<joevandyk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:
> Has anyone set up a one button deployment system for their Rails app?
> 
> Say you''re developing a few sites for different clients.  You add
a
> feature, test it, and want to deploy the application.  How do you do
> that?  I''d imagine that, at the very least, the
config/database.yml
> file needs to be changed for the life site.  And probably some other
> stuff needs to be changed when the site goes live (or gets updated).
> 
> So, how do you do it?  What''s the Right(tm) way?
> 
> I guess I''m also looking for some general admin tips.  A friend
and I
> are doing a couple Rails sites and I seem to be spending a lot of time
> setting up Rails stuff, starting/restarting webrick, figuring out the
> database situations on the testing and live servers, etc.  Any ideas?
> 
> Thanks,
> Joe
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
> 

-- 
Tobi
http://www.hieraki.org   - Open source book authoring
http://blog.leetsoft.com - Technical weblog