I’m using MODx in a commercial environment where we have a dedicated development server. It’s relatively easy to copy all the assets and a dump of the database and put that over on the dev server, however, certain settings shouldn’t be changed.
In particular, the
Tools-->Configuration-->File Manager --> File Manager Path setting is likely to change from host to host. And the
Interface & Features --> Resource Path is also likely to be different between a dev and a prod host.
In Expression Engine, there was a configuration file that lived in the system folder with a hash. You had to know the correct hash keys, but essentially, you could do something like:
$settings['file_manager_path'] = '/path/to/my/dev/manager';
And then you could copy the database over in its entirety, but when you did an SVN checkout or an rsync to grab the most recent files from the production machine or from the repository, you’d simply ignore that configuration file so the dev server would be able to maintain its own settings.
I could write a script that overwrites these values based on my own configuration file / environment variables, but I’m wondering if there’s a better way.
Thanks!
☆ A M B ☆