add-ideas/govoplan-core
1
0
Fork 0
Code Issues 45 Pull Requests Actions Packages Projects Releases Wiki Activity

Sync wiki from project files

Albrecht Degering
2026-07-07 12:51:41 +02:00
parent cc92e60e0f
commit 2b7eb080e2
1 changed files with 26 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
Repo-docs-RELEASE-DEPENDENCIES.md

@@ -1,4 +1,4 @@
<!-- codex-wiki-sync:875c35f000f5984fa2fe7e49 -->
<!-- codex-wiki-sync:c3f079496ca96e9e3c28b8e0 -->
> Mirrored from `/mnt/DATA/git/govoplan-core/docs/RELEASE_DEPENDENCIES.md`.
> Origin: `repository`.
@@ -80,6 +80,23 @@ govoplan-module-installer \
--restart-command '<restart govoplan server>'
```
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 '<restart govoplan server>'
```
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 <run-id> --format json
govoplan-module-installer --lock-status --format json
govoplan-module-installer --list-requests --format json
govoplan-module-installer --show-request <request-id> --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