Environments Plugin

A plugin to handle environment-level configuration

Requirements

• CakePHP 3.x

Installation

[Using Composer]

View on Packagist, and copy the json snippet for the latest version into your project's composer.json. Eg, v. 1.0.0 would look like this:

{
	"require": {
		"josegonzalez/cakephp-environments": "3.0.0"
	}
}

Enable plugin

You need to enable the plugin your config/bootstrap.php file:

Plugin::load('Josegonzalez/Environments');

If you are already using Plugin::loadAll(); before usage, then this is not necessary.

Usage

Setup a directory structure as follows:

config/environments.php
config/environments/production.php
config/environments/staging.php
config/environments/development.php

We specify multiple environment files to separate the various configurations and make it easy to inspect a given environment. This is not necessary, but useful if you are configuring a large amount of information.

Your environments.php should contain the following:

<?php
use Josegonzalez\Environments\Environment;

include dirname(__FILE__) . DS . 'environments' . DS . 'production.php';
include dirname(__FILE__) . DS . 'environments' . DS . 'staging.php';
include dirname(__FILE__) . DS . 'environments' . DS . 'development.php';

Environment::start();
?>

Then, you need to include the environments.php file you created in your application, for example in bootstrap.php:

include dirname(__FILE__) . DS . 'environments.php';

This will:

• Load the environments plugin in cases where it may not already be loaded
• Include every environment, in order of specificity (development is usually last)
• Start the environment

Environment Configuration

Each environment may be configured as follows:

Josegonzalez\Environments\Environment::configure($name, $params, $config = null, $callable = null);

Example usage of the \Josegonzalez\Environments\Environment::configure() call is available in the config/environments folder of this plugin.

• $name: Usually something like production or development. Good practice is to name it the same as the file it was in, so that there isn't any confusion as to what a given env file contains

• $params: An array or boolean of environment variables used to check whether this environment applies. If a boolean and set to true, this environment is automatically initiated. A value of true should only be used for development:

  If a previous environment is not enabled, this one will be set

  \Josegonzalez\Environments\Environment::configure(
      'development',
      true,
      ['debug' => true]
  );

  If an array, the keys may be function names that are called, with the values being passed to it:

  \Josegonzalez\Environments\Environment::configure(
      'development',
      [
      	'some_function' => 'aValueForThisCheck',
      	'another_function' => 'aDifferentValueForThisCheck',
  	]
  );

  In all other cases, we simply check the environment:

  \Josegonzalez\Environments\Environment::configure(
      'octo_development',
      [
      	'SERVER_NAME' => 'octo-example.dev',
      ]
  );
  
  \Josegonzalez\Environments\Environment::configure(
      'bear_development',
      [
      	'SERVER_NAME' => 'bear-example.dev',
      ]
  );
  
  \Josegonzalez\Environments\Environment::configure(
      'development',
      [
  		'CAKE_ENV' => 'development',
  	]
  );

  If we are running in CLI, the only check enforced is CAKE_ENV, and the value MUST be the name of the environment:

  CAKE_ENV=production Console/cake bake all

  If the CAKE_ENV environment variable is set at all, it takes precedence over everything, including a boolean value for $params.

• $config: If set, an array of keys => values that are set via Configure::write(). Useful for batch-setting api keys, database connection information, etc.

• $callable: A PHP callable, such as ['ClassName', 'functionName']. It is also possible to use an anonymous function. This is the preferred method of setting information that might depend upon the value of some function call.

License

Copyright (c) 2014 Jose Diaz-Gonzalez

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.