Setting Environment

This are just guidelines of how your environment could be setted. First step, use a Version Control System like Subversion or Git. Don't version config/config.php When developing the app (on your local machine) set on config/config.php

   !defined('AK_ENVIRONMENT') && define('AK_ENVIRONMENT','development');

Web requests you make will run against the development DB. Once you're done with local changes, commit to your repository and checkout on the production machine where you will need to set

   !defined('AK_ENVIRONMENT') &&  define('AK_ENVIRONMENT','production');

Regarding Unit Tests, any time you call

  ./script/test unit

the environment will be set for you to 'testing'. The right thing to do is to locally test before committing. Akelos still don't have a remote deployment script, so you will need to run migrations on the remote server if there are database scheme changes.

 
setting-environment.txt · Last modified: 2008/10/04 10:01 by arnoschn