Configuration

mela:install publishes config/mela-cms.php into the site.

Key	Default	Meaning
locales	['en']	Languages the site is published in. The first is the default. A starting value: the Languages page overrides it
locale_urls	'path'	Where the other languages live: 'path' for example.com/it, 'subdomain' for it.example.com
admin_locale	null	Language of the admin panel. null uses the app locale. Also a starting value
admin_path	'admin'	URL path of the admin panel
panel_provider	AdminPanelProvider::class	The class that builds the admin panel. Your own class that extends it changes the panel. See Admin panel
pages	['settings' => ManageSettings::class, 'languages' => ManageLanguages::class]	The admin pages the core adds. Works like resources
profile_page	EditProfile::class	The page where a user edits their own account. null removes it; your own class replaces it
resources	['pages' => PageResource::class, 'media' => MediaResource::class, 'users' => UserResource::class]	The admin screens the core adds. Set an entry to null to remove the screen, or to your own class to replace it
public_pages	true	The core answers every address no route of the site matches with the published page at that address. See Pages
sitemap	[Page::class]	What /sitemap.xml lists: model classes with a url() method, and paths. See SEO
media	See Media	Disk, directory, accepted types, maximum size, image sizes and quality of the media library

A key the site's file does not have takes the core's default, also when the config is cached. So a new core version can add keys without asking the site to publish the file again.

The site's mela-cms.json

At the root of the site, mela-cms.json records which version of each workflow template the site took or kept. mela:install and mela:update write it. Commit it, and do not edit it by hand. See Updating the core.