Staging database good practices

Posted by Tom on Stack Overflow See other posts from Stack Overflow or by Tom
Published on 2010-05-19T04:03:02Z Indexed on 2010/05/19 4:10 UTC
Read the original article Hit count: 448

Hi,

I'm about to deploy to production a fairly complex site and for the first time need a staging environment where I can test things in a more realistic environment, especially with regard to some external services that cannot be run locally.

My general plan is to develop & test first locally, push simple changes (small bug fixes, HTML/CSS, JS, etc) direct to production, and for larger changes, push first to staging subdomain for thorough testing and then to production.

I don't think that I need to keep the staging and production databases in sync (occasional manual updating would do) but I'm wondering if there are any general good practices with regard to maintaing a staging environment in relation to a production environment, especially when it comes to databases.

Any general thoughts/advice/experience would be appreciated.

© Stack Overflow or respective owner

Related posts about staging

Related posts about production