openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

memory: add K3s infra to long-term memory

Browse source
This commit is contained in:
Hoid 2026-02-18 13:47:53 +00:00
parent 07db17080f
commit 8407a3a941
1 changed files with 11 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

11
MEMORY.md
View file

@ -4,6 +4,17 @@
- `projects/ideas/product-ideas.md` — All product ideas + SnapAPI CEO setup plan - `projects/ideas/product-ideas.md` — All product ideas + SnapAPI CEO setup plan
- Selected next product: **SnapAPI** (Screenshot API) — ready to launch when user says go - Selected next product: **SnapAPI** (Screenshot API) — ready to launch when user says go
## K3s Infrastructure (2026-02-18)
- 3-node K3s cluster: k3s-mgr (188.34.201.101), k3s-w1 (159.69.23.121), k3s-w2 (46.225.169.60)
- Hetzner LB: 46.225.37.135 (ID 5834131)
- CNPG PostgreSQL 17.4 (2 instances) + PgBouncer pooler in `postgres` namespace
- DocFast: `docfast` (prod, 2 replicas) + `docfast-staging` (1 replica)
- CI/CD: push main→staging, tag v*→prod via Forgejo registry
- Deployer SA with namespace-scoped RBAC (no secret access)
- Forgejo needs PAT for registry (GITHUB_TOKEN lacks package scope)
- Old server (167.235.156.214) kept for git push + SMTP relay only
- Total infra cost: €17.06/mo (3x CAX11 + LB)
## Game Save Files ## Game Save Files
- `memory/d2r.json` — Diablo II: Resurrected progress (Necro "Baltasar", Summoner build) - `memory/d2r.json` — Diablo II: Resurrected progress (Necro "Baltasar", Summoner build)
- `memory/bg3.json` — Baldur's Gate 3 progress (Act 1, level 3) - `memory/bg3.json` — Baldur's Gate 3 progress (Act 1, level 3)