Package and Test an Eenos App
Build a single-root app archive and review dependency installation, lifecycle scripts, deployment order and release acceptance checks.
Prepare a clean release directory with app.conf, the enabled interfaces and only the supporting files needed for this release. Include README, license, compatibility, dependency and upgrade/removal instructions.
Create the archive
From the directory containing exampleapp/:
tar -czf exampleapp-1.0.0.tar.gz exampleapp/
tar -tzf exampleapp-1.0.0.tar.gzSupported installer extensions are .tar, .tar.gz and .tgz. It extracts with --strip-components=1; use exactly one enclosing package directory. Do not package app.conf flat at archive root or add an extra wrapper around the app directory.
Inspect member paths, symlinks and executable content before distribution. Exclude credentials, private keys, customer data, development caches and unrelated panel files. Use simple trusted archive/work paths: current deployment commands are assembled as shell strings.
Installation order
The current deployment sequence is: pre scripts; manifest creation; pip requirements; WAP/RAPP/UAPP files and assets; vhosts; hooks; scripts; menu rebuild; panel service restart; post scripts.
Pre/post directories execute top-level regular files. The installer sets execute permissions and runs them; it does not provide a documented dependency scheduler or guaranteed numeric filename order. Keep ordering within a single controlled script when it matters, and make setup repeatable.
Dependencies from requirements.txt are installed into the shared Eenos Python environment. Pin compatible dependencies and avoid replacing the panel's framework. Python requirements are not a PHP Composer installer.
Installation is not transactional
Several deployment steps log errors and continue. A final completion message or zero shell status does not prove that every command succeeded. The installer does not provide automatic rollback of files, dependencies, hooks, vhosts or app-owned data.
Development acceptance
Use a disposable Eenos development server before asking an administrator to install your app. Verify the package name and all enabled interfaces, logged-out access rejection, role/ownership checks, CSRF behavior for mutations, correct static assets, and direct routes as well as menu navigation.
Test fresh install, repeat install, update from the previous version, global and per-panel disable/enable, and removal. Check that unrelated apps remain intact. Exercise dependency failures and partial deployment recovery; preserve a versioned release and rollback procedure.
If your app creates a database, worker or external service, document its migration, backup and cleanup separately. Do not assume the generic app remover will discover or reverse those effects.
Use the administrator lifecycle commands only when intentionally deploying or changing the test server.