Implement an App Requirement Engine

robert commented

2026-05-04 09:22:44 +02:00

Collaborator

Each App must have a list of requirements.
Each requirements will be a hook to another app with optional cli commands (executed on a container) to call on the required app before installation (e.g. creating an MQTT user) and before every start (e.g. starting an API).
For longer cli scripts files in the app folder should be created.

If an App is required, it needs to be installed.

To consider:

Do we have to avoid circular dependancies? If yes, why and how?
apps with dependancies need working default req scripts using .env files for variables
User needs to be informed, whenever a required app is installed.

Each App must have a list of requirements. Each requirements will be a hook to another app with optional cli commands (executed on a container) to call on the required app before installation (e.g. creating an MQTT user) and before every start (e.g. starting an API). For longer cli scripts files in the app folder should be created. If an App is required, it needs to be installed. To consider: - Do we have to avoid circular dependancies? If yes, why and how? - apps with dependancies need working default req scripts using .env files for variables - User needs to be informed, whenever a required app is installed. -

daniel commented

2026-08-25 17:20:59 +02:00

Owner

Umgesetzt in 26.17–26.19: requires im Manifest + on_install/on_start-Hooks, längere Skripte unter scripts/ im App-Ordner, benötigte Apps werden automatisch mitinstalliert. Zu den offenen Punkten: Zyklen werden erkannt und abgelehnt (furtka/deps.py), Hook-Variablen kommen per .env/FURTKA_CONSUMER_ENV_*, und das UI zeigt vor der Installation „Installing X also installs Y" mit Bestätigung. Validiert mit mosquitto + zigbee2mqtt.

daniel closed this issue

2026-08-25 17:20:59 +02:00

Rows
Columns

Implement an App Requirement Engine #11