Enabling and disabling modules based on environment

Submitted by Benjamin Melançon on February 26, 2011 - 12:15pm

A drush command. Text file with modules to enable on dev, and then run it manually or somehow automatically.

drush? make text file with all the modules and git it to drush pm_enable

If we have a defined practice for environment-specific module enabling/disabling and i'd love to disable views_ui, update, etc. on live

It would be run after sync commands-- pull data from live, but then enable update on the test site, and all site building modules on dev

Searched words:

drupal approach for automatically enabling modules on dev

Comments

Your name: *

E-mail: *

The content of this field is kept private and will not be shown publicly.

Homepage:

Subject:

Comment: *

You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
You can use Markdown syntax to format and style the text. Also see Markdown Extra for tables, footnotes, and more.
Web page addresses and e-mail addresses turn into links automatically.
Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
Lines and paragraphs break automatically.