Migrating from dev to prod

Friday 09 July 2010 8:26:05 am

Hi Daniel

This is a recurrent question. There are actually 2 issues to fix :

1. Pushing your files into production
2. Adapting your config files to production

For first point, you might consider a simple scripting engine, such as Apache ANT

For second point, take a look at NovenINIUpdate ;)

You can also take a look at the presentation I made at the last eZ Conference in Berlin.

Friday 09 July 2010 9:32:39 am

One way of keeping different configuartions for dev/test/prod environments I find myself using a lot is simply to define separate siteaccesses for them, eg frontsa_dev, frontsa_prod, adminsa_dev, adminsa_prod.

Cons: you will end up with quite a few duplicated settings files

Pros: no need to use deployment scripts to change your dev settings to prod; easier to check any differents between the two config sets

Another tip: use a single svn repo where you have all of your code versioned, starting from ezp root, and including all settings and extensions

Cons: makes the svn repo slightly bigger; unruly developers might end up committing changes to ezp kernel code

Pros: setting up a new dev workstation / test server amounts to a single "svn checkout"; no need to mess with svn:externals or complex setups

Principal Consultant International Business
Member of the Community Project Board

Monday 12 July 2010 3:03:01 pm

Using different siteaccess can quickly become tricky, dangerous and hard to maintain to say the least.

If you have one site, you may manage three or four different siteaccess, but if you have five (or more) website it's just not possible...

But you can try with this http://issues.ez.no/IssueView.php?Id=16205

We deployed it few weeks ago, and it becomes a lot easier to maintain.