UnionOfRAD/lithium — Issue #188: Environment ignored when using the console
Author: L-P
Created: 2011-11-04 09:27:50+00:00
State: open

Hi,
I have a li3 app (usign 4bcc5718f63f9a08b8780c24ad35ad9b5bce2e1a) and created a Cron command
to use from crontab. I have three environments : dev, valid and
prod. They work perfectly when calling the app via HTTP.

When using the console if I do not provide an environment name via --env,
the dev environment is used and I get the following warning :
`Lithium console started in the dev environment. Use the --env=environment key to alter this.`

This is normal but when I specify `--env=prod` or `--env=valid` the dev
parameters are still used thus making the MySQL DB unusable (no, I don't
want to use root@localhost in production). The warning vanishes though.