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

Add the svc.sh environment service manager #45

Merged
weichen merged 4 commits from feature/svc-env-script into main 2026-09-30 11:38:57 +00:00
Conversation 0 Commits 4 Files Changed 5
+208 -1
4 Commits
Author SHA1 Message Date
weichen c1eea4b05b Record the sync checkpoint
ci / test (pull_request) Failing after 1m31s
Details
2026-09-30 11:38:44 +00:00
weichen f0e7831ed1 Record the svc-env-script task card results 2026-09-30 11:38:43 +00:00
weichen 35d114307d Add the svc.sh environment service manager 
Why: deploying a new build meant manually finding and killing the old
process, rebuilding and re-launching with the right flags; dev and prod
instances could collide on ports, data dirs or kill each other.

Evidence: live matrix on the worktree - dev deploy (stop -> make build
-> start with health check), redeploy swaps the pid and keeps seeded
data, prod deploys alongside dev on separate port/data with fully
isolated /api/projects, port takeover is refused with the owning
process named while the running env stays up, stop clears pidfile and
frees the port. A pid-capture bug (compound-background subshell wrote
the wrapper pid instead of the server) was caught and fixed during the
first live run.

Impact: scripts/svc.sh <dev|prod> [deploy|stop|start|restart|status|
logs]; runtime/<env>/{data,svc.pid,svc.log,svc.env} isolation; defaults
dev 127.0.0.1:8788 / prod 127.0.0.1:8787 overridable via SVC_* env
vars (incl. SVC_PROD_DSN for the PG tier); make svc ENV=... shortcut;
runtime/ gitignored. Safety: only processes started by the script are
stopped (pidfile + /proc cmdline double check).

Refs: feature/svc-env-script task card.
 2026-09-30 11:38:43 +00:00
weichen c2e5ca5211 Record the task card for feature-svc-env-script 2026-09-30 11:19:29 +00:00