Panel Menus, Routes and Assets
Understand how Eenos generates My Apps entries, loads Django apps and serves Python or PHP routes and static files across panels.
The installed app manifest and generated panel registries connect your package to My Apps. You do not need to edit the built-in panel sidebar or hardcode a new item in its source.
Registration flow
- Installation reads
app.confand writes/var/eenos/apps/<appname>.yaml. - Menu rebuilding reads globally enabled manifests and enabled panel sections.
- It generates
/var/eenos/preferences/wap_apps.yaml,rapp_apps.yamlanduapp_apps.yamlas applicable. - Each panel loads its registry for application settings, routing and menu presentation.
Only enabled Python entries are returned for Django application loading; names are sorted. The selected panel adds them to INSTALLED_APPS and includes <appname>.urls. Python menu records use apps/<appname>/; PHP records use /<appname>/. The panel sidebar handles the current language prefix for Python links.
Startup and errors
Django settings and URL registration are loaded by panel processes. Installation and managed enable/disable actions rebuild menus and restart eenosweb.service. The standalone appmanager --build action rebuilds menu files only; it does not itself restart the panel service.
A URL import failure can be logged while URL loading continues. A broken app import during Django initialization can still disrupt a panel. Check the actual application startup and direct route, not merely whether a menu record exists.
Three independent interfaces
| Panel | Intended scope |
|---|---|
| WAP | Administrator-authorized server operations. |
| RAPP | Reseller-owned resources and permitted delegated operations. |
| UAPP | The authenticated hosting account's resources. |
You can reuse an app's presentation or business logic, but enforce the correct scope for every panel and endpoint. Enabling an app or hiding its menu is not authorization.
Templates and assets
Python templates can inherit the current panel's base.html. Use panel-provided classes and components rather than bundling a replacement panel framework. Namespace your own templates and asset paths.
WAP app assets are copied to its default theme; RAPP/UAPP copy to existing theme directories. A theme created after installation may need the app assets deployed separately. Test asset URLs for every advertised theme.
Avoid editing generated registries to repair a missing entry. Check the manifest, global/panel state, installed interface files and recorded installation errors, then use supported management operations. See lifecycle.