Configuration
Shared file conventions and safe configuration changes.
Last reviewed September 2026
File conventions
#Customer-facing settings use config.yml, messages.yml, menus.yml and product-specific files. GUI slots are zero-based unless a product page says otherwise.
Safe updates
#Where implemented, reload validates a complete candidate and atomically swaps the active immutable snapshot. Invalid candidates leave the current runtime configuration active.
- Back up files before structural changes.
- Preserve customer values during versioned updates.
- Use focused examples rather than replacing complete files.
Secrets
#License keys, passwords, database credentials and webhook URLs must stay out of screenshots, paste sites and diagnostics.