Build a PHP App
Package PHP interfaces for EenosD with per-panel vhosts, correct paths and an explicit authentication and authorization design.
PHP app interfaces are copied into /usr/local/eenos/3rdparty/apps/<panel>/<appname>/. They are not Django apps and do not automatically inherit the logged-in Django user's session or permissions.
Official reference package
Download the PHP sample. It includes separate WAP/RAPP/UAPP interfaces and matching vhost files. Its pages demonstrate presentation and PHP execution; they are not a complete authenticated app framework.
For your own app, set language = php, use a unique name such as examplephpapp and place its interface under wap/examplephpapp/, rapp/examplephpapp/ or uapp/examplephpapp/ as appropriate.
EenosD configuration
Supply matching files in the plural vhosts/ directory:
vhosts/wap.examplephpapp.conf
vhosts/rapp.examplephpapp.conf
vhosts/uapp.examplephpapp.confOnly include the routes you intend to expose. The installer records matching vhosts by filename independently of the panel's installation flag; an off menu flag is not proof that a supplied PHP route is inaccessible.
The sample uses /run/eenos-user-fpm.sock, the panel-specific third-party app root and /usr/local/eenos/etc/eenosd/fastcgi_params. Review these against the actual EenosD/PHP-FPM configuration before adapting the location blocks. Match only your own app route and avoid overriding another panel location.
The loader's default PHP menu destination is /<appname>/, separate from Python's localized apps/<appname>/ routing. PHP requests need an appropriate configured location and handler; a menu entry alone does not configure serving.
Authenticate before exposing app data
Implement and review an explicit authentication/session mechanism and role/ownership checks. A direct request to the PHP URL must not bypass them. Do not infer identity from a query parameter, referer or the fact that the browser came from My Apps.
The old guide included a shell-based /etc/shadow password check. Do not use that as an application authentication design: it couples web code to privileged password storage and shell input. PAM authentication alone also does not implement account scope, suspension policy, CSRF protection or session management.
The framework does not provide a verified PHP SSO adapter in the code reviewed for these guides. Integrate a reviewed authentication boundary for your app rather than inventing a trusted panel-session header. Keep protected endpoints inaccessible until that boundary is implemented.
Runtime privileges and assets
Use an unprivileged runtime for app requests. The sample comments mention a root FPM socket; do not select it merely to work around file-permission errors. Privileged changes need a narrow, validated backend operation, especially for RAPP and UAPP users.
Place shared static assets under static/<appname>/. Sample PHP templates use /static/default/<appname>/; adapt asset paths if you support other themes. PHP HTML is separate from Django template inheritance, so build its page layout deliberately and verify both themes if advertised.
Review security and packaging before distributing a PHP app.