GeneralBots/gb
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: Add CI deployment rules and SSH hostname setup

Browse source
This commit is contained in:
Rodrigo Rodriguez (Pragmatismo) 2026-03-21 21:07:20 -03:00
parent 9677c90907
commit ff146657e0
1 changed files with 24 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
AGENTS-PROD.md
View file

@ -225,8 +225,9 @@ Proxy container needs its own fail2ban for HTTP flood protection:
## CI/CD (Forgejo Runner) ## CI/CD (Forgejo Runner)
- **ALWAYS use CI for deployment** — NEVER manually scp binaries. CI ensures consistent, auditable deployments.
- Runner container must have **no cross-container disk mounts** - Runner container must have **no cross-container disk mounts**
- Deploy via SSH: `scp binary <system-container>:/opt/gbo/bin/botserver` - Deploy via SSH: `scp binary <system-container>:/opt/gbo/bin/botserver` (only from CI, not manually)
- SSH key from runner → system container must be pre-authorized - SSH key from runner → system container must be pre-authorized
- sccache + cargo registry cache accumulates — daily cleanup cron required - sccache + cargo registry cache accumulates — daily cleanup cron required
- ZFS snapshots of CI container can be huge if taken while cross-mounts were active — delete stale snapshots after removing mounts - ZFS snapshots of CI container can be huge if taken while cross-mounts were active — delete stale snapshots after removing mounts
@ -236,6 +237,28 @@ Each submodule has its own workflow at `.forgejo/workflows/<name>.yaml`.
**botserver workflow:** `botserver/.forgejo/workflows/botserver.yaml` **botserver workflow:** `botserver/.forgejo/workflows/botserver.yaml`
### CI Deployment Flow
1. Push code to ALM → triggers CI workflow automatically
2. CI builds binary on `pragmatismo-alm-ci` runner
3. CI deploys to `pragmatismo-system` container via SSH
4. CI verifies botserver process is running after deploy
5. If CI fails → check logs at `/tmp/deploy-*.log` on CI runner
**To trigger CI manually:**
```bash
# Push to ALM
cd botserver && git push alm main
# Or via API
curl -X POST "http://alm.pragmatismo.com.br/api/v1/repos/GeneralBots/BotServer/actions/workflows/botserver.yaml/runs"
```
### SSH Hostname Setup (CI Runner)
The CI runner must resolve `pragmatismo-system` hostname. Add to `/etc/hosts` if missing:
```bash
lxc exec pragmatismo-alm-ci -- bash -c 'echo "10.16.164.33 pragmatismo-system" >> /etc/hosts'
```
### Deploy Step — CRITICAL ### Deploy Step — CRITICAL
The deploy step must **kill the running botserver process before `scp`**, otherwise `scp` fails with `dest open: Failure` (binary is locked by running process): The deploy step must **kill the running botserver process before `scp`**, otherwise `scp` fails with `dest open: Failure` (binary is locked by running process):