I usually keep a production-like environment called staging. The staging area has the same features of the production enviroment but with all debugging settings enabled.
Each new release is first deployed in staging at least once, then deployed to production. If something fails or some unit test doesn't pass, the release is fixed then deployed again. I have a sync task that keep staging database in sync with the production one on request. -- Simone On Fri, Mar 6, 2009 at 3:49 AM, Peter Booth <[email protected]>wrote: > I usually develop against a clone of production. Is the question how can I > back out if the release fails? > The flawed approach I have used is: > > 1. deploy code > 2. dump a copy of production > 3. migrate the copy DB > 4. start new production against migrated DB > > The flaw in this is that if the app is still running after step 2, then the > migrated DB used in step 4 may miss some updates that occurred in > production. > > > > On Mar 5, 2009, at 9:23 PM, Lee Hambley wrote: > > Peter, > Running the migrations locally won't affect the "live" / "production" > database? > > - Lee > > 2009/3/6 Peter Booth <[email protected]> > >> >> How does capistrano make this different than doing a migration locally? >> >> Peter Booth >> (917) 445 5663 [email protected] >> >> On Mar 5, 2009, at 6:20 AM, Mike <[email protected]> wrote: >> >> > >> > Hi All, >> > >> > I have deployed my rails application using Capistrano it run well, Now >> > i want to update my application for that i have the latest code i ll >> > update it, i don't how to alter,add table to my database without >> > losing the existing data. plz guide me to do so.. >> > >> > I follow the tutorial for deployment in Capistrano site : >> http://www.capify.org/ >> > But i didn't get the exact solution for that. For new deployment it >> > helped me a lot. >> > >> > I use subversion for scm >> > >> > Capistrano 2.x version for deployment >> > >> > Mysql db >> > >> > [r...@web01nrt gems]# httpd -v >> > Server version: Apache/2.2.3 >> > Server built: Jan 15 2008 20:33:30 >> > >> > [r...@web01nrt gems]# ruby -v >> > ruby 1.8.6 (2007-09-24 patchlevel 111) [i686-linux] >> > >> > Application layer server : Mongrel 1.1.5 and i used mongrel_cluster >> > >> > For your additional information : >> > >> > actionmailer-1.3.6 >> > actionpack-1.13.6 >> > actionwebservice-1.2.6 >> > activerecord-1.15.6 >> > activesupport-1.4.4 >> > cgi_multipart_eof_fix-2.5.0 >> > daemons-1.0.10 >> > fastthread-1.0.1 >> > gem_plugin-0.2.3 >> > mongrel-1.1.5 >> > mongrel_cluster-1.0.5 >> > mysql-2.7 >> > rails-1.2.6 >> > rake-0.8.2 >> > rmagick-2.6.0 >> > sources-0.0.1 >> > >> > > >> >> >> > > > > > > > > -- Simone Carletti Site & Blog: www.simonecarletti.com Email: [email protected] LinkedIn: http://linkedin.com/in/weppos Nick: weppos | Skype: weppos --~--~---------~--~----~------------~-------~--~----~ To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano -~----------~----~----~----~------~----~------~--~---
