Welcome Guest, Not a member yet? Register   Sign In
Subversion workflow - Should your production site be a working copy?
#3

[eluser]johnpeace[/eluser]
I get around the config file problem by just writing everything so it's $_SERVER['HTTP_HOST'] independent. Something like:

Code:
if($_SERVER['HTTP_HOST'] == 'localhost') {
  // do localhost config
} elseif($_SERVER['HTTP_HOST'] == 'dev.server') {
  // do dev server config
}...

So the same config files will work on all of the machines. There are only 2-3 config changes that are in blocks like this, so it's not as bad as it looks.

The dev server is a working copy that is automatically updated on a successful commit.

I hadn't thought of tagging a revision as 'stable' and exporting that to the live site...that's a great idea.

What we've been doing is just committing/updating the dev server working copy and then after testing that, cp the files to the production server directory.


Messages In This Thread
Subversion workflow - Should your production site be a working copy? - by El Forum - 03-03-2010, 08:04 AM



Theme © iAndrew 2016 - Forum software by © MyBB