This week, I released a Drupal 6 module called Environments (shortname Envts), my first released module and EchoDitto's first for Drupal 6. Its purpose is to help developers manage "two-dimensional" Drupal site environments. Drupal is fairly good at running multi-site builds, with sites folders and different settings.php files. Modules like Domain Access are good at managing those sites one-dimensionally - a single list of hosts with primary (mysite.com), secondary (special.mysite.com), etc, and deep integration with Views and other modules.

But this single list of sites is built for one environment: one set of domains, such as for a live site. For example:

• dartcenter.org [primary]
• dartsociety.org [secondary]

Domain Access is good at listing these domains and filtering nodes by them. But in our work, there's never only one environment. There's a development environment -

• dartcenter.dev.echoditto.com [primary]
• dartsociety.dev.echoditto.com [secondary]

- and each developer usually has a local server environment -

• dartcenter.ben.local [primary]
• dartsociety.ben.local [secondary]

- and sometimes there's a staging server between dev and live -

• staging.dartcenter.org [primary]
• staging.dartsociety.org [secondary]

- and so forth.