PHPackages keyboardcowboy/drush-denver - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Utility & Helpers](/categories/utility) 4. / 5. keyboardcowboy/drush-denver ActiveDrupal-drush[Utility & Helpers](/categories/utility) keyboardcowboy/drush-denver =========================== Customize modules, variables and permissions for each environment. 2.2.3(7y ago)17561[4 issues](https://github.com/KeyboardCowboy/drush-denver/issues)GPL-2.0+PHPPHP >=5.4.0 Since Mar 25Pushed 7y ago1 watchersCompare [ Source](https://github.com/KeyboardCowboy/drush-denver)[ Packagist](https://packagist.org/packages/keyboardcowboy/drush-denver)[ Docs](https://github.com/KeyboardCowboy/drush-denver)[ RSS](/packages/keyboardcowboy-drush-denver/feed)WikiDiscussions 2.1.x Synced 1mo ago READMEChangelog (4)Dependencies (2)Versions (26)Used By (0) Drupal Environment Personalizer =============================== [](#drupal-environment-personalizer) The Drupal ENVironemnt personalizER allows you to define macro settings to apply to your site in one command, such as enabling and disabling modules and setting variables. Installation ------------ [](#installation) Extract this repository into any of Drush's searchable paths for plugins: 1. A `.drush` folder in your HOME folder. 2. Anywhere in a folder tree below an active module on your site. 3. `/usr/share/drush/commands` (configurable) 4. In an arbitrary folder specified with the `--include` option. 5. Drupal's `/drush` or `/sites/all/drush` folders. *See `drush topic docs-commands` for more details* Configuration ------------- [](#configuration) These can be defined in two different files and only apply to the site directory in which they are defined. 1. `sites/[default|example.com]/drush/env.drushrc.yml` 2. `sites/[default|example.com]/drush/[dev.]env.drushrc.yml` Like aliases, in the first file you can define multiple aliases keyed on the definition name such as 'dev,' 'stage' or 'chris.' In the second example you can define each environment in a separate file and prefix the filename with the definition name. The definitions are formatted as such: # Settings for your local environment. modules: enable: - module\_name disable: - module\_name ``` variables: your_var: your_var_value another_var: NULL permissions: RoleName: permission_name: 0 commands: # Using longhand notation. command-name: alias: @self arguments: arg1: arg1-val options: opt1: opt1-val # Using shorthand notation. command-name: - yes - arg1 - arg2 - --option1 ``` How to Use It ------------- [](#how-to-use-it) You must be inside a Drupal site directory or use an alias for these commands to work. 1. Create a starter file `drush env-dir --make` 2. See which environments are available. `drush env``drush env-list` 3. Inspect the contents of an environment definition. `drush env [en-name] --info` Ex. `drush env dev --info` 4. Run the environment settings for a single definition. `drush env [env-name]` Ex. `drush env dev` 5. Combine multiple environments. The settings for the latter overriding the former. `drush env [env-name1]+[env-name2]` Ex. `drush env dev+chris` ### Health Score 26 — LowBetter than 43% of packages Maintenance0 Infrequent updates — may be unmaintained Popularity16 Limited adoption so far Community8 Small or concentrated contributor base Maturity68 Established project with proven stability Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~48 days Recently: every ~43 days Total 25 Last Release 2904d ago Major Versions 1.x-dev → 2.0.02016-07-26 PHP version history (2 changes)1.3.1PHP >=5.3.0 2.0.0PHP >=5.4.0 ### Community Maintainers ![](https://www.gravatar.com/avatar/6067f952738d7618fb6fbcf8998f07451cd09ed5a0885513e1084ae416571303?d=identicon)[KeyboardCowboy](/maintainers/KeyboardCowboy) --- Top Contributors [![KeyboardCowboy](https://avatars.githubusercontent.com/u/1002715?v=4)](https://github.com/KeyboardCowboy "KeyboardCowboy (24 commits)") --- Tags environmentDrush ### Embed Badge ![Health badge](/badges/keyboardcowboy-drush-denver/health.svg) ``` [![Health](https://phpackages.com/badges/keyboardcowboy-drush-denver/health.svg)](https://phpackages.com/packages/keyboardcowboy-drush-denver) ``` ### Alternatives [vlucas/phpdotenv Loads environment variables from `.env` to `getenv()`, `$\_ENV` and `$\_SERVER` automagically. 13.5k602.4M5.4k](/packages/vlucas-phpdotenv)[symfony/dotenv Registers environment variables from a .env file 3.8k226.7M2.3k](/packages/symfony-dotenv)[foroco/php-browser-detection Ultra fast PHP library to detect browser, OS, platform and device type by User-Agent parsing 1554.7M7](/packages/foroco-php-browser-detection)[wolfcast/browser-detection The Wolfcast BrowserDetection PHP class facilitates the identification of the user's environment such as Web browser, version, platform family, platform version or if it's a mobile device or not. 1391.0M7](/packages/wolfcast-browser-detection)[imliam/laravel-env-set-command Set a .env file variable from the command line 118352.4k10](/packages/imliam-laravel-env-set-command)[silverstripe/environmentcheck Provides an API for building environment tests 35503.8k13](/packages/silverstripe-environmentcheck) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)