Docs Navigation Open

Configuration Reference

Review the main configuration surfaces used by Evolution CMS: system settings, runtime environment, URLs, cache behavior, and package-level config.

Configuration Layers

  • System settings — values stored in the database and edited through the manager.
  • Environment/runtime config — values supplied by the runtime and bootstrapping layer.
  • Package config — config files owned by installed packages.
  • Resource-level settings — template choice, TVs, cache flags, menu flags, and other per-resource decisions.

System Settings in Code

use EvolutionCMS\\Models\\SystemSetting;

$value = SystemSetting::where('setting_name', 'site_name')->value('setting_value');
$title = evo()->getConfig('site_name');

Package Config Pattern

Modern packages keep config in files and merge it through a service provider.

$this->mergeConfigFrom(__DIR__ . '/../config/example.php', 'example');

Practical Rules

  • do not put package config into random snippets when a config file belongs in the package
  • do not treat TVs as global config
  • keep deployment-specific secrets out of content fields

See Extending Evolution and Creating an Extra.

Previous

Glossary

Keep the most important Evolution CMS terms in one concise lookup page.

Next

Permissions

Use roles for actions and groups for scope: that is the practical permission model in the manager.