adam/foundry
1
0
Fork 0
Code Issues 7 Pull requests 6 Projects 1 Releases Packages Wiki Activity Actions

docs(omniroute): document zero-config key mode #18

Open
claude wants to merge 1 commit from fix-omniroute-key-docs into main
pull from: fix-omniroute-key-docs
merge into: adam:main
Conversation 0 Commits 1 Files changed 1 +23 -8
claude commented 2026-08-16 20:11:59 -05:00
Owner
Copy link

Doc-only. The omniroute stack is deployed and healthy in zero-config key mode — omniroute auto-generates its keys and persists them to /app/data/server.env inside the named volume, next to storage.sqlite. Key + DB co-reside in the same persistent volume, so the old "key in RAM, DB on disk" boot-loop cannot recur.

The committed compose header wrongly said the four secrets were REQUIRED and Dockhand-injected. Reframed as optional key overrides (only useful for portable DB-backup restores), with a note that pinning after provider creds exist requires clearing the volume first. No runtime change.

Doc-only. The omniroute stack is deployed and healthy in **zero-config** key mode — omniroute auto-generates its keys and persists them to `/app/data/server.env` inside the named volume, next to `storage.sqlite`. Key + DB co-reside in the same persistent volume, so the old "key in RAM, DB on disk" boot-loop cannot recur. The committed compose header wrongly said the four secrets were REQUIRED and Dockhand-injected. Reframed as **optional** key overrides (only useful for portable DB-backup restores), with a note that pinning after provider creds exist requires clearing the volume first. No runtime change.
The stack runs in zero-config mode: omniroute auto-generates its keys and
persists them to /app/data/server.env inside the named volume, alongside
storage.sqlite. Key+DB co-reside, so the old boot-loop can't recur. The
four env secrets were never required — reframe them as optional overrides
for portable DB-backup restores, not mandatory Dockhand injections.

Doc-only; no runtime change.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix-omniroute-key-docs:fix-omniroute-key-docs
git switch fix-omniroute-key-docs

Merge

Merge the changes and update on Forgejo.
git switch main
git merge --no-ff fix-omniroute-key-docs
git switch fix-omniroute-key-docs
git rebase main
git switch main
git merge --ff-only fix-omniroute-key-docs
git switch fix-omniroute-key-docs
git rebase main
git switch main
git merge --no-ff fix-omniroute-key-docs
git switch main
git merge --squash fix-omniroute-key-docs
git switch main
git merge --ff-only fix-omniroute-key-docs
git switch main
git merge fix-omniroute-key-docs
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
lab-honing
Lab-access honing backlog (from 2026-07-11 session review)

No labels
lab-honing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
adam/foundry!18
No description provided.