NYCPHP Meetup

[Mitch Pirtle]

Brian Pang wrote:

>trying to bring this back OT
>
>When possible, I like to set up a subdomain on the same server such that
>www.domain.com is my production environment and
>dev.domain.com is my dev environment
>(sometimes I'll also do a 3rd QA setup)
>  
>

This is where CVS really shines, as I track everything except the config 
file in CVS, then can export that project to the production websites 
directory and the configuration is still good.

In a sense, a good practice that I try to follow is dev->test->prod, and 
I can use CVS to manage the whole shebang with simple export steps.  You 
can even cron the export to test, so the test version is always current 
(within a day/hour/minute etc.).

I've lately started keeping all configuration information in a separate 
config class, and that has really helped things out immeasurably.  As 
long as the configuration info includes the URLs and directory paths, 
the only thing different in each of these sites is the values in the 
config class.  Everything else should just work.  And yes, I did learn 
this practice through working with Mambo...

What other ways are there that are easy to do?  Do I smell a 
PHundamentals opportunity?  ;-)

-- Mitch