>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2314095. --> Reported by: [jdillick](https://www.drupal.org/user/2264216) >>> <h2>Environment Makefile</h2> <h2>Sandbox</h2> <p><a href="https://www.drupal.org/sandbox/jdillick/2313227">Environment Makefile Sandbox</a></p> <h3>Git Clone Instructions</h3> <pre><pre>git clone --branch 7.x-1.x http://git.drupal.org/sandbox/jdillick/2313227.git environment_makefile<br>cd environment_makefile</pre></pre><p>Environment makefile allows you to auto-enable or disable modules based on your site's makefile and environment. This would allow you to specify development modules such as devel, or production-only modules such as production monitor in one makefile that will be enabled or disabled when you run Drush.</p> <h2>Requirements</h2> <ul class="task-list"> <li>Drupal 7.x</li> <li>PHP 5.3+</li> </ul> <h2>Configuration</h2> <p>To configure production environments, have your system administrator configure the ENVTYPE environment variable, setting to <em>production</em>, <em>staging</em>, <em>dev</em>, or <em>local</em> as appropriate.</p> <p>In linux, add a /etc/profile.d/envtype.sh file:</p> <div class="highlight highlight-bash"> <pre><span class="c">#!/bin/bash</span> <span class="nv">ENVTYPE</span><span class="o">=</span>production <span class="nb">readonly </span>ENVTYPE <span class="nb">export </span>ENVTYPE </pre></div> <p>Configure your virtual host in Apache with:</p> <pre><pre>SetEnv ENVTYPE production</pre></pre><h3>Optional Configuration</h3> <p>To set an alternate set of production environments, use strongarm or $conf array to set the <em>environment_makefile_product_environments</em> variable:</p> <div class="highlight highlight-php"> <pre><span class="nv">$conf</span><span class="p">[</span><span class="s1">'environment_makefile_product_environments'</span><span class="p">]</span> <span class="o">=</span> <span class="k">array</span><span class="p">(</span> <span class="s1">'prod'</span><span class="p">,</span> <span class="s1">'stag'</span><span class="p">,</span> <span class="s1">'test'</span><span class="p">,</span> <span class="p">);</span> </pre></div> <h3>Makefile location</h3> <p>environment_makefile assumes your makefile will be located in a makefiles directory adjacent to the Drupal webroot, and named to match the parent directory:</p> <pre><pre>example.com/<br>&#9500;&#9472;&#9472; makefiles<br>&#9474;&nbsp;&nbsp;&nbsp;&nbsp; &#9492;&#9472;&#9472; example.com.make<br>&#9492;&#9472;&#9472; webroot</pre></pre><p>If you would like to specify the full path to your makefile, use strongarm or $conf to set the <em>makefile_path</em> variable.</p> <h2>To Use</h2> <p>environment_makefile uses an augmented drush make file to manage the enabling and disabling of modules in your Drupal deployment environments.</p> <p>In your makefile, you can specify modules and submodules that should be enabled or disabled by using the following groupings:</p> <ul class="task-list"> <li> <em>enabled</em>: these modules will be enabled in all environments</li> <li> <em>disabled</em>: these modules will be disabled in all environments</li> <li> <em>dev_only</em>: these modules will be disabled in production environments, and enabled everywhere else.</li> </ul> <h3>Example Makefile</h3> <pre><pre>core = 7.x<br><br>api = 2<br><br>projects[drupal][version] = "7.28"<br><br>disabled[] = overlay<br>disabled[] = dashboard<br><br>projects[ctools][subdir] = "contrib"<br>projects[ctools][version] = "1.4"<br>enabled[] = ctools<br>enabled[] = views_content<br>dev_only[] = bulk_export</pre></pre><h2>Drush Support</h2> <p>Drush is the primary means of initiating environment_makefile.</p> <div class="highlight highlight-bash"> <pre>drush @alias environment-makefile <span class="c"># alias envm</span> </pre></div>