From 2b7eb080e22802b01ab6bd1d6044aea56ff128fe Mon Sep 17 00:00:00 2001 From: Albrecht Degering Date: Tue, 7 Jul 2026 12:51:41 +0200 Subject: [PATCH] Sync wiki from project files --- Repo-docs-RELEASE-DEPENDENCIES.md | 27 ++++++++++++++++++++++++++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/Repo-docs-RELEASE-DEPENDENCIES.md b/Repo-docs-RELEASE-DEPENDENCIES.md index 18b35fd..e3a1252 100644 --- a/Repo-docs-RELEASE-DEPENDENCIES.md +++ b/Repo-docs-RELEASE-DEPENDENCIES.md @@ -1,4 +1,4 @@ - + > Mirrored from `/mnt/DATA/git/govoplan-core/docs/RELEASE_DEPENDENCIES.md`. > Origin: `repository`. @@ -80,6 +80,23 @@ govoplan-module-installer \ --restart-command '' ``` +To let the admin UI trigger package work without executing pip/npm inside a +FastAPI request, run the installer daemon under the process supervisor: + +```bash +govoplan-module-installer \ + --daemon \ + --migrate \ + --build-webui \ + --health-url http://127.0.0.1:8000/health \ + --restart-command '' +``` + +Admin > System > Modules can then queue the saved install plan as a supervised +request. The daemon claims one queued request at a time and writes request/run +records below `runtime/module-installer`. For process-manager one-shot usage or +tests, use `--daemon-once`. + The installer uses a runtime lock, snapshots `pip freeze` plus WebUI `package.json`/`package-lock.json`, writes a run record below `runtime/module-installer/runs`, and marks planned rows as applied only after @@ -140,8 +157,16 @@ Inspect installer history and lock state from the operator shell: govoplan-module-installer --list-runs --format json govoplan-module-installer --show-run --format json govoplan-module-installer --lock-status --format json +govoplan-module-installer --list-requests --format json +govoplan-module-installer --show-request --format json ``` +Package catalogs are file-backed. Set `GOVOPLAN_MODULE_PACKAGE_CATALOG` to a +JSON file matching `docs/module-package-catalog.example.json`; the admin UI will +show those entries and can add them to the install plan. This keeps the release +approval decision outside the running server while avoiding hand-typed package +refs. + Install rows must use tagged package/git refs or registry packages, not local `file:` or workspace links. WebUI package changes still require `npm install` and a WebUI rebuild/reload because the current shell resolves WebUI modules from