Configuration reference ​

These variables are read by the current application's configuration files. Copy .env.example for installation, then set values for the actual runtime. Do not commit .env or secrets.

Application and services ​

This project reads CACHE_DRIVER, not CACHE_STORE. Check config/cache.php when configuring the runtime. Storage adapters must be installed and configured for the chosen remote disk.

The application time zone is UTC in config/app.php. A campus can select its own time zone for display and local dates. Use school_now(), school_today(), and school_time() for the appropriate campus-clock behavior. Stored timestamps and campus-local date fields have different purposes. The supported language keys are ar, bn, br, de, en, es, fr, ja, kr, nl, pl, pt, ro, ru, and zh. Use the application's keys exactly, including br and kr.

Detailed feature settings ​

The feature screen edits whole-feature switches only. Detailed settings are stored in FeatureSetting.config and read through FeatureManager. Portal flags use the PortalArea values: results, attendance, timetable, calendar, notices, invoices, documents, requests, library, boarding, graduation, programmes, and syllabi. An unspecified portal flag defaults to true. Attendance uses daily_register and lesson_register, also defaulting to true.

An authorized application integration can pass a complete configuration array to FeatureManager::enable(). This replaces the stored configuration array; it does not merge individual flags. For example, a stored portal configuration can include:

{
  "results": true,
  "invoices": true,
  "requests": false
}

{
  "results": true,
  "invoices": true,
  "requests": false
}

The omitted areas retain their default behavior. This is a stored feature configuration, not a block to paste into .env. Preserve existing choices when updating the array and record the responsible actor. See feature switches and security.

Backups and release checks ​

BACKUP_FILES_DISK is not currently read by config/monitoring.php. Configure the missing file-source setting before relying on --with-files. See backup operations for the complete procedure.

After changing configuration, refresh cached configuration in the correct runtime. Restart long-running workers so they load the new configuration. See deployment.