Idea behind this module is to have settings for each instance of the site separated, including multi-site setups. It allows to enable/disable modules (with support of module pools, allowing only one module from each pool to be enabled) and set variables based on settings defined in settings.php files.
Settings can be applied on each page load or using drush command, based on module settings.
All config is done ONLY through settings.php files, allowing us to achieve "loose coupling" of modules.
Please check README.txt file supplied for more details (You'll need them).
How it can be used:
You can Drush sync database, for example put Prod db to Local environment
Apply instance settings - it will disable unneeded modules, enable needed modules and features, making sure it not overlap with Prod-only related features, and set variables.
Example:
drush sql-sync PROD_DRUSH_ALIAS LOCAL_DRUSH_ALIAS
drush instance-settings-apply
OR
drush isa
Other environment setup related modules, and why create new module:
Environment
Environments should be set through Drupal hooks, supports Drush, no module pools.
Modules disable/enabled logic implemented in Drupal hooks, so your module should "know" about other modules existence, which is not good as I believe it should be decoupled.
Environment modules
Only allows to enable/disable module based on settings. No Drush, no module pools, no variables setup.
Tadaa!
Need to configure settings through UI, supports Drush, no module pools.
Project information
- Project categories: Administration tools, Developer tools
3 sites report using this module
- Created by aroq on , updated
Stable releases for this project are covered by the security advisory policy.
There are currently no supported stable releases.