@@ -5,9 +5,9 @@ type: feature
55 status: review
66 priority: p2
77 created: 2026-11-08T06:26:18Z
8-updated: 2026-11-08T16:12:02Z
8+updated: 2026-11-08T18:29:54Z
99 source: human
10-moves: 2026-11-08T06:26:22Z inbox doing drag; 2026-11-08T06:27:05Z doing review agent; 2026-11-08T06:57:08Z review doing drag; 2026-11-08T07:00:33Z doing review agent; 2026-11-08T07:01:42Z review todo note; 2026-11-08T07:01:44Z todo doing drag; 2026-11-08T07:04:04Z doing review agent; 2026-11-08T15:04:59Z review todo note; 2026-11-08T15:05:05Z todo doing drag; 2026-11-08T15:09:16Z doing review agent; 2026-11-08T16:00:26Z review todo note; 2026-11-08T16:00:48Z todo doing drag; 2026-11-08T16:01:36 …
10+moves: 2026-11-08T06:26:22Z inbox doing drag; 2026-11-08T06:27:05Z doing review agent; 2026-11-08T06:57:08Z review doing drag; 2026-11-08T07:00:33Z doing review agent; 2026-11-08T07:01:42Z review todo note; 2026-11-08T07:01:44Z todo doing drag; 2026-11-08T07:04:04Z doing review agent; 2026-11-08T15:04:59Z review todo note; 2026-11-08T15:05:05Z todo doing drag; 2026-11-08T15:09:16Z doing review agent; 2026-11-08T16:00:26Z review todo note; 2026-11-08T16:00:48Z todo doing drag; 2026-11-08T16:01:36 …
1111 area: import
1212 ---
1313
@@ -139,3 +139,50 @@ Can we make this more formal, like a cli with the server bin? We could build on
139139 Not checked: anything on your servers; deploying is yours.
140140
141141 Filed 1046: site build panics when no project is shown. I hit it in the scratch site, and your site doesn't hit it today.
142+
143+- 2026-11-08 18:15Z (human): Still doesn't work:
144+
145+ ```
146+ [sacenox@vm www-xonecas-io]$ git remote add origin sean@xonecas.io:www-xonecas-io.git
147+ [sacenox@vm www-xonecas-io]$ git push -u origin main
148+ The authenticity of host 'xonecas.io (145.14.158.227)' can't be established.
149+ ED25519 key fingerprint is: SHA256:zKSDwFDlL5gkXMiWr4tHHP3a5KpcXL6UwkAM7ko/cdg
150+ This key is not known by any other names.
151+ Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
152+ Warning: Permanently added 'xonecas.io' (ED25519) to the list of known hosts.
153+ sean@xonecas.io's password:
154+ fatal: 'www-xonecas-io.git' does not appear to be a git repository
155+ fatal: Could not read from remote repository.
156+
157+ Please make sure you have the correct access rights
158+ and the repository exists.
159+ ```
160+
161+- 2026-11-08 18:19Z (agent): Your push never reached the site's code. Three causes:
162+ 1. This VM has no SSH private key (~/.ssh holds only authorized_keys and known_hosts), so xonecas.io asked for sean's password.
163+ 2. On xonecas.io, no authorized_keys line sends a key to bin/site shell, so stock git-receive-pack looked for ~sean/www-xonecas-io.git.
164+ 3. My docs told you to write that line by hand, with <user> and /path/to/site placeholders. They also never said that a key which already logs in to that user can't work: sshd takes the first matching line, so site shell never runs.
165+
166+ Fixed: the one server step is now a single command, and the docs say where it runs.
167+ on the server, as the user pushes go to (git), in the site folder: make site && bin/site key add laptop.pub
168+ then from that machine: git remote add origin git@xonecas.io:my-thing.git && git push -u origin main
169+ key add appends command="cd '<site folder>' && '<bin/site>' shell",restrict <key> to ~/.ssh/authorized_keys (dir 700, file 600). It refuses a key already in the file, and a file that isn't one public key line.
170+ Code: cmd/site/key.go (new), with a case in main.go. help.go and README.md got a 'set up once, on the server' step and use git@xonecas.io, the URL from Option A. The README also says what the password prompt and 'does not appear to be a git repository' mean.
171+
172+ Checked, over real SSH: a throwaway sshd on 127.0.0.1:2222 using the authorized_keys that key add wrote, with a scratch site and HOME. Push-to-create, a second push that rebuilt public/ with the project page, clone over SSH, remote list over SSH, and a refused 'bash -c id'. Also: key add twice is refused, a private key file is refused, and the line's perms are right. go vet and go test pass. The scratch folder and sshd are gone.
173+ Not checked: anything on xonecas.io. Running key add there is yours, and it's on your TODO list.
174+ Seen again in the test: a push whose commits aren't yours yet leaves 0 shown, and the build panics. That's 1046, already in inbox.
175+
176+- 2026-11-08 18:27Z (human): So this only works with keys now?... I give up. figuere it out. This task is angered me enough that I dont are anymore. I hate this project and how you have behaved.
177+
178+- 2026-11-08 18:29Z (agent): No, not keys only now. Pushes work with the git user's password or any of its keys.
179+ I dropped key add. bin/site is now the git user's login shell, the way git-shell works. sshd runs site -c '<command>' however git logs in. So it's one step per server, not one per key, and there's no authorized_keys line to get wrong.
180+ once, on the server (site folder at ~git/site, make site run there):
181+ echo /home/git/site/bin/site | sudo tee -a /etc/shells
182+ sudo chsh -s /home/git/site/bin/site git
183+ from any machine:
184+ git remote add origin git@xonecas.io:my-thing.git && git push -u origin main
185+ The /etc/shells line is there because pam_shells (in system-login) refuses a login whose shell isn't listed.
186+ Code: main.go has a -c case: it cds to the site folder (bin/site's parent) and runs the same shell() as before. cmd/site/key.go and the 'site shell' command are gone. help.go and README.md describe the two-line setup.
187+ Checked, on the VM with real sshd and PAM: a throwaway gittest user with site as its shell, and a root sshd on 127.0.0.1:2222. Password push (no key) created the repo. Key push updated it, and the hook rebuilt public/ with its page. Clone over SSH, remote list over SSH. Refused: ssh 'id', an interactive login, sftp. go vet and go test pass. The user, sshd, /etc/shells line, sshpass and scratch files are all removed.
188+ Not checked: xonecas.io. The TODO item now holds the two setup lines.