I have a staging area at the customer's server.
1. Compare existing code to my new code for database updates only 2. Checkout my new code over the staging area at customer's server 3. Stop current service. 4. Backup old code + database. (Just database, actually, as the I have the release version of the running code, but for a quick restore you might want to have a backup of it as well) 5. Overwrite code with code from staging area. 6. Update database. 7. Start new release and be happy. Testing is done on a different server / port. It connects to a copy of the production database that is replicated when the deployment plan starts, so that there is real production data inside the test environment. When customer gives "OK", deploy. In case of small issues, those are fixed without a rollback. For major issues that weren't caught while testing, we perform a rollback. If database has to be rolled back, then changes after the update are lost. -- Jorge Godoy <[email protected]> On Wed, Aug 26, 2009 at 11:04, <[email protected]> wrote: > > hello frinds, > > how would you deploy a growing tg2 app? > > -- > alex > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
