Repository navigation
v2.5.2
Important
The debug level comes from APP_DEBUG, and is 0 when it is not set. On a development machine, set APP_DEBUG=2 in config/.env.local.
Debug level and .env loading (PR #36)
config/core.phpreads the debug level withConfigure::write('debug', env('APP_DEBUG') ?? 0);.- The
.envfiles are loaded with symfony/dotenv'sloadEnv()instead ofbootEnv(). The files and their order do not change.APP_DEBUGkeeps the value you set (bootEnv()turned it into1or0), andconfig/.env.local.phpis no longer read.
Database configuration (PR #38)
config/database.php.default:$testis empty, and the constructor copies$defaultto it only whenAPP_ENVistest, so the tests use the database ofconfig/.env.test. In any other environment thetestconnection is not configured, so tests cannot run on the database of that environment.- In
$default, the keys thatDATABASE_URLsets (datasource,host,login,password,database) are commented out, so they cannot be mixed with the DSN. WithoutDATABASE_URL, thedefaultconnection fails instead of using placeholder values.
Updating an Application
- In
config/core.php, replacebootEnv(CONFIG . '.env')withloadEnv(CONFIG . '.env'), and theConfigure::write('debug', ...)line withConfigure::write('debug', env('APP_DEBUG') ?? 0);. - Set
APP_DEBUG=2inconfig/.env.localon development machines. Leave it unset (or0) in production. - In
config/database.php, copy the empty$testand the constructor fromconfig/database.php.default.
Full Changelog: v2.5.1...v2.5.2