kai/pi-agent-config
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: state the Gitea repo structure and SSH push auth in the README and every scenario root

Browse Source 
One Gitea repo (kai/pi-agent-config, SSH key auth as user git on :222) holds the runtime config, all scenario agent configs, and the curator backend; no per-agent repos. Each scenario now carries a root README pointing at the shared repo and push flow so a directory's provenance and push method are unambiguous.
This commit is contained in:
Kai
2026-08-30 20:37:11 -07:00
parent 88b06d782f
commit 53ffa2fd7f
4 changed files with 110 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scenarios/pi-grok/README.md
+21
View File
@@ -0,0 +1,21 @@
# pi-grok — Pi agent scenario
This directory is the **pi-grok** Pi agent. It is tracked as part of the
`pi-agent-config` repository — it is **not** a standalone repository.
- Gitea repo: `kai/pi-agent-config` on `192.168.50.45` (web `:3000`, SSH `:222`).
- Remote: `origin -> gitea-45:kai/pi-agent-config.git`, branch `main`.
- Auth: SSH key only (`~/.ssh/id_ed25519_gitea`, Git user `git`); no HTTP token.
- Push and pull from the repository root, not from here:
```bash
git pull --rebase origin main
git push origin main
```
See the repository [`README.md`](../../README.md), section “Gitea repository and
push authentication”, for the full SSH config and caveats.
## Layout
- `profile.toml` — the launch contract (single source of truth).