Templates & Themes
Distinguish Eenos panel themes from generated service templates and choose a safe customization workflow for each component.
Panel themes render the hosting control panel. Service templates generate configuration or alert content. They use different engines, paths and activation mechanisms.
Panel themes
Panel HTML uses Django templates, with matching static assets. Custom theme identifiers are distinct from light/dark appearance and branding settings. Preserve forms, actions, CSRF tokens, routes and scripts while changing presentation.
The current WAP base loader reads a global theme name from /var/eenos/preferences/theme.yaml and falls back to default when the file is absent, unreadable/invalid YAML or the selected directory is missing. Its template root is /usr/local/eenos/wap/templates/. This is not a per-account WAP theme selector; a WAP theme rollout needs a separately reviewed global deployment and worker loading plan. The old statement that WAP has no theme loading support is incomplete for the current code.
Service template guides
| Component | Guide |
|---|---|
| DNS zone rendering | Versioned DNS templates |
| Apache/Nginx/OpenLiteSpeed virtual hosts | Web application templates |
| Website PHP pools | PHP-FPM templates |
| Email notifications | Alert templates |
| Antivirus | ClamAV templates |
| IMAP/POP3 | Dovecot templates |
| SMTP | Exim templates |
| Mailing lists | Mailman templates |
| FTP | Pure-FTPd templates |
| Spam filtering | SpamAssassin templates |
Engines and precedence
Most service defaults live under /usr/local/eenos/templates/. Mako and Jinja are both used; .jinja commonly identifies Jinja files, but extensions alone are not authoritative. Alert .html files can be Mako, while panel .html files are Django templates. Follow the component's renderer and current source data contract.
There is no universal override rule for every component. Some support global custom files only; DNS, webserver and FPM have specific account/domain precedence. Follow each guide's paths, including versioned directories where required.
Safe rollout
Copy the exact compatible default into the supported custom location and edit that copy. Keep shipped defaults intact: updates can replace them, and custom files do not automatically receive new upstream fixes. Compare custom overrides against defaults after updates.
A template edit generally affects a later generation/rebuild operation, not an already running service immediately. Back up the prior custom and generated files, render in staging, validate the generated configuration with the service's supported tools, and plan activation and rollback. Never reload a service merely because template rendering returned success; inspect the output and native configuration validation too.