Prod and Dev environments/management
| From: | DL Neil | Date: | Tue, 09 Oct 2001 18:34:22 +0000 |
| Subject: | Prod and Dev environments/management | ||
| Groups: | php.db | ||
| Request: | Send a blank email to php-db+get-13153@lists.php.net to get a copy of this message | ||
Request advice (and if possible, relevant code snips) on keeping Test/Dev environment
databases/tables safely separated from Production data.
Do you keep separate MySQL (et al) databases, eg dbOrders_Tst, dbOrders_Prd, or simply have
differently named tables within one db, eg tblOrders_Tst, tblOrders_Prd?
Once separated, when coding your PHP, how do you 'point' the script to the appropriate
db/tables?
Alternatively, how do you ensure that testing/playing/dev work doesn't foul production data?
Enquiring minds...
=dn
PS my personal dev env is NTWusS 4.0, PHP4, MySQL, and Apache