Skip to Content
Browse documentation

App Installation, Updates and Removal

Manage Eenos extension installation and panel availability, implement update scripts and understand disable and uninstall limitations.

The administrator uses /usr/local/eenos/scripts/appmanager. These commands can execute trusted app code, change files and restart panel services. They are deployment examples, not steps to run on a production server merely to inspect an app.

Install and inspect

/usr/local/eenos/scripts/appmanager --install /root/exampleapp-1.0.0.tar.gz
/usr/local/eenos/scripts/appmanager --list

Use the actual archive path and review the output and Eenos logs. Listing can contact each configured version-check URL; it is not guaranteed offline.

Disable and enable

/usr/local/eenos/scripts/appmanager --disable exampleapp --panel uapp
/usr/local/eenos/scripts/appmanager --enable exampleapp --panel uapp
/usr/local/eenos/scripts/appmanager --disable exampleapp --all
/usr/local/eenos/scripts/appmanager --enable exampleapp --all

Always select scope explicitly. Omitting --panel makes enable/disable default to all panels. A globally disabled app cannot be enabled by a single-panel enable action. The all-panels enable action sets the global flag and all present panel flags on; review which interfaces are actually installed before using it.

Managed availability changes rebuild menus, restart eenosweb.service, and rename applicable recorded vhosts to/from .disabled with an EenosD reload. They do not install missing interfaces.

Disabling does not remove app scripts or hooks, cancel app-owned workers, or implement resource authorization. Review those separately if you need to stop all app activity.

Rebuild menus

/usr/local/eenos/scripts/appmanager --build

This rebuilds registry files only. It does not by itself reload Python application imports or restart the panel service.

Implement an updater

Set auto_update to an installed executable path, commonly a uniquely named file from your package's scripts/ directory. The manager checks that the file exists and is executable, then invokes it:

/usr/local/eenos/scripts/appmanager --update exampleapp

Your updater owns version verification, downloads, backup, deployment/migrations, manifest version changes and failure recovery. The manager does not infer a download archive from version_check_url, and a version-check mismatch does not automatically install an update.

Remove

/usr/local/eenos/scripts/appmanager --remove exampleapp

Removal globally disables the app, removes recorded hooks/scripts/vhosts, panel code and app asset directories, then removes its manifest. It does not uninstall shared pip dependencies or automatically remove custom databases, app-created services or external data. There is no generic uninstall-hook directory in the reviewed implementation.

Use unique resource names and document intentional data preservation and explicit cleanup. Verify the result instead of relying only on a completion message. See the full appmanager command reference for all flags.