Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: phranque
I almost never review anything until it hits the staging server. Rarely someone will ask for input from something on the development server -- I can think of twice in the past year.
Despite not being a team I will be moving to having a test environment inbetween. I am moving to automate various tasks (uploading common code to multiple websites, database schema changes etc) and I want to be able to run that against a test environment before I run it against live.
The test environment will probably be virtual though.
A play pen where we can try out crazy ideas.
For current business-as-usual or project developments
System testers do thier testing here
Used for content publishing practice (by the client) - it can then be deployed to PP and Prod from here.
Mirror of prod (in hardware terms too), used for testing architectural issues and also acts as a backup should a part of Prod fail.
Obviously our production site for the public
In addition to these it is a little more complicated since sometimes we might introduce more machines in say Development if we have more than 1 stream of work on at once. Also, sandpit and dev share the same CMS database. Likewise with databases, some environments may have dedicated database servers or some might share one. the other variant is we have 1 physical server with many instances of a database on it.