config.env.php.example

<?php
/*
   CONFIG.ENV.PHP - SETTINGS OF THIS MACHINE
   -----------------------------------------
   Copy this file to config.env.php in the root of the installation and keep
   it out of version control (.gitignore lists it). It is read before
   config.php, by the web entry points and by the command line scripts.

   EXP_ENV names the environment of this machine. eZINI then reads, next to
   every settings file, a variant with the environment name after ".ini":

     settings/override/site.ini.append.php
     settings/override/site.ini.test.append.php   (read after it when EXP_ENV is 'test')

   The variant overrides the settings of its own layer only (base settings,
   an extension, a siteaccess or settings/override), and it is also read when
   the standard file does not exist. Each environment has its own INI cache.

   Common names:
     dev  - a developer machine: PHP errors are shown in the browser
     test - a test or staging copy: PHP errors are shown in the browser
     prod - the live site: settings as in php.ini

   A name must be lowercase letters, digits, "-" or "_", starting with a
   letter, at most 32 characters. Without EXP_ENV, or with an invalid name,
   only the standard settings files are read.

   Templates can read the name with {exp_environment()}.
*/

//define( 'EXP_ENV', 'dev' );