Environment affecting the configuration files in CLI mode

Could be because CLI also runs in an "environment", and when it can't find CI_ENV, it defaults to wrong option, but you can easily set similar variables in any environment.

For Windows machines, you can search environment variables from your settings page.

For Unix/Linux, you have to create/update a specific file that gets loaded when you log in or when user account is active - more here https://unix.stackexchange.com/questions...-variables

For cron, you can set these variables from cron file, check the second and third answer from here - https://stackoverflow.com/questions/2229...b-will-use