r35157/com_r35157_nenjim-hubd-impl_ref
0
0
Fork 0
Code Issues 18 Pull Requests Actions Packages Projects Releases Wiki Activity

81: Version fix

Browse Source
This commit is contained in:
minimons
2026-09-03 14:36:00 +02:00
parent a65c2fc09c
commit 324aa67710
8 changed files with 37 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
openspec/changes/81-configure-ordered-process-autorun/design.md
+2 -3
View File
@@ -52,7 +52,7 @@ Registry retains its required exceptional order of start, self-registration, the
### Keep deployment configuration separate from its template
The runtime path stays a private constant in the reference Hub. `conf/NenjimHub.conf.example` is version controlled and documented, but no code references that example path. The real file remains deployment-specific under the existing `*.conf` ignore rule. Documentation shows copying explicitly and includes a separate headless snippet.
The runtime path stays a private constant in the reference Hub. `conf/NenjimHub.conf.example` is version controlled and documented, but no code references that example path. The example deliberately contains only the mandatory Registry and Journal entries so it is safe and generic for downstream users; operators add their own deployment-specific processes and dependency order after copying it. The real file remains deployment-specific under the existing `*.conf` ignore rule. Documentation shows copying explicitly and includes the same minimal headless bootstrap.
## Risks / Trade-offs
@@ -64,8 +64,7 @@ The runtime path stays a private constant in the reference Hub. `conf/NenjimHub.
## Migration Plan
1. Deploy the new build together with an operator-created `conf/NenjimHub.conf` copied from the version 2 example and adjusted for the deployment role.
1. Deploy the new build together with an operator-created `conf/NenjimHub.conf` copied from the version 1 example and extended with the deployment's own ordered process selection.
2. Validate that manually ordered dependencies precede their consumers; Registry and Journal must remain first and second.
3. Start the Hub normally through the unchanged `Main` entry point.
4. To roll back the software, restore the previous build and its prior deployment configuration expectations; the application never rewrites either runtime or example configuration.