@@ -2,13 +2,13 @@
22 id: 1011
33 title: Write the hand-off doc for hosting the site and git remotes
44 type: feature
5-status: doing
5+status: blocked
66 priority: p2
77 area: docs
88 created: 2026-11-07T19:30:00Z
9-updated: 2026-11-08T01:09:39Z
9+updated: 2026-11-08T02:09:03Z
1010 source: agent
11-moves: 2026-11-07T19:30:00Z inbox todo agent; 2026-11-08T01:09:39Z todo doing drag
11+moves: 2026-11-07T19:30:00Z inbox todo agent; 2026-11-08T01:09:39Z todo doing drag; 2026-11-08T02:09:03Z doing blocked agent
1212 ---
1313
1414 We never deploy and never touch the VPS, so this is a document for xonecas to act on. It is not a deployment.
@@ -22,3 +22,15 @@ Cover:
2222 - the risks to IRVC as a live production service, and how to roll back.
2323
2424 Done when: the doc is attached here and every command in it has been run against a local stand-in, with anything not testable marked as such.
25+
26+## Notes
27+
28+- 2026-11-08 02:09Z (agent): Blocked: one decision before I write the doc, because it changes every command in it. Nothing is written yet.
29+
30+ Today the site builds from repos/, bare mirrors that 'site import' fetches from GitHub and GitLab with --prune. If you also push to the VPS, the two collide: the next import would delete or overwrite anything pushed only to the VPS. So which remote is the source of truth?
31+
32+ (a) GitHub stays the source. The VPS mirrors it every 10 minutes on a systemd timer and rebuilds. Your workflow doesn't change and nothing is pushed to the VPS. Read-only clones come from xonecas.io. No code change.
33+ (b) The VPS is a push target for some repos (RECOMMENDED, closest to the ticket). 'git remote add xonecas ssh://<you>@xonecas.io/srv/git/<name>.git', and a post-receive hook rebuilds the site. Those repos are listed in sources.txt as VPS paths and are never pruned from GitHub. Others keep coming from GitHub. Needs a small code change: import treats a local path as a source that is already there.
34+ (c) The VPS is the only remote. You push there, and the hook pushes on to GitHub as a mirror and rebuilds. Same code change as (b), and GitHub becomes a copy.
35+
36+ Either way the doc covers: the Caddy site block for xonecas.io and the www redirect, leaving the IRVC block alone ('caddy validate' before reload, the old file kept for rollback); public clones at https://xonecas.io/projects/<name>.git over plain HTTP (git's dumb protocol, static files, so Caddy needs no CGI); and the build running on the VPS. I'll install Caddy in this VM as the stand-in and run every command there.