weichen/Agent-System-Dev
1
0
Fork 0
Code Issues 1 Pull Requests 6 Actions 2 Packages Projects Releases Wiki Activity

Seed model and search settings on service start #49

Merged
weichen merged 4 commits from feature/svc-auto-seed into main 2026-09-30 11:56:50 +00:00
Conversation 0 Commits 4 Files Changed 4
+88 -2
4 Commits
Author SHA1 Message Date
weichen e371a3c4fa Record the sync checkpoint
ci / test (pull_request) Failing after 1m56s
Details
2026-09-30 11:56:42 +00:00
weichen 5c2fa4562b Record the svc-auto-seed task card results 2026-09-30 11:56:41 +00:00
weichen 81ac0ca5c2 Seed model and search settings on service start 
Why: a freshly deployed environment boots with an empty settings store,
so the first run dies with "main model unconfigured" and the user has
to open the settings UI before anything works - the opposite of
one-command bring-up.

Evidence: live matrix - full seed (chat+lightweight+tavily) lands in
the settings store (API view shows baseUrl/model with the key masked),
restart without flags does not re-seed and the settings persist,
.svc.env sourcing seeds a fresh environment from the one-time config
file, and a no-flag start stays silent. Also wrapped a /proc read race
in pid_alive that printed tr noise during stop.

Impact: --model-base/--model-key/--model-name, --light-base/-key/
-name, --tavily-keys on start/deploy (idempotent, only provided
fields); SVC_MODEL_*/SVC_LIGHT_*/SVC_TAVILY_KEYS env vars; <repo>/
.svc.env one-time config file (gitignored) makes every future deploy
self-configuring; auth-protected instances fall back to a clear hint.

Refs: feature/svc-auto-seed task card.
 2026-09-30 11:56:41 +00:00
weichen 82c2417edb Record the task card for feature-svc-auto-seed 2026-09-30 11:54:54 +00:00