Hi Tridem wrote: > I'm looking for a good way to arrange my production and development > environments. > Currently I have a module for each purpose. > > /modules/default (production) > /modules/dev (development) > > Both paths are bootstrapped bepending on the setEnv set in 2 different > hosts: > www.whatever.de (production) > dev.whatever.de (development)
Why do you have modules for each purpose? What would you like to separate? Use a SCM like SVN. Your stable application (the version, you can use in production) is located in "trunk" - your king. If you need to fix a small bug, fix it in trunk. If you develop the next milestone/feature, create a branch (and keep it in sync with your king (trunk)), which you will reintegrate into trunk, when you are finished. Your resources (e.g. databases) should be defined in configuration files. For example, if ENV is set to "development", use section "development" from your config.xml... if ENV is set to "production", use the "production" section from your configuration file. In this setup, it should be easy to find/debug bugs in each environment. You don't have to keep the same file twice and copy fixes from one environment into the other environment like you would have to do, if you would separate your modules. -- Regards, Thomas
