Backtalk6858/claude-projects
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

note: next session — sync POST /allowlist to sudo-bridge-server01

Browse Source 
Bridge was added to primary only; server-01 needs redeploy of latest
image + allowlist.json sync before it can autonomously add entries.
This commit is contained in:
Backtalk6858
2026-06-22 20:52:59 -05:00
parent 23bbcb4a6d
commit be89611060
1 changed files with 5 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agent-builder/.claude/context.md
+5
View File
@@ -202,6 +202,11 @@ Coolify service UUID: `ilus0cfdkheipodw1viurg1d`
- 524 on destructive commands: Cloudflare kills long-poll at ~100s; approval must be tapped quickly; command still runs if approved before timeout, response just lost - 524 on destructive commands: Cloudflare kills long-poll at ~100s; approval must be tapped quickly; command still runs if approved before timeout, response just lost
**NEXT SESSION — in order:** **NEXT SESSION — in order:**
0. sudo-bridge-server01 — sync POST /allowlist endpoint
- POST /allowlist was added to sudo-bridge (primary) this session but server-01 bridge container was NOT redeployed — it's still running the old image without the endpoint
- Both bridges share gitea.local/backtalk6858/sudo-bridge:latest — code is already in the image, just need to redeploy server-01 bridge (Coolify UUID: o2kz1puml1mmneyiqd96mouj) via pull + restart
- Also: server-01 allowlist.json needs the 4 new entries added today (iptables-save, 99-local-routing.conf, sysctl -p, journalctl -u) — these are primary-only entries so only add if relevant to server-01 use cases
- Verify: curl POST /allowlist and GET /allowlist on sudo-bridge-server01.reverseproxyserver.net after redeploy
1. id=51 Secrets Proxy — sandbox precondition scaffolding 1. id=51 Secrets Proxy — sandbox precondition scaffolding
- Problem: sandbox dry-run is meaningless if the required state doesn't exist (e.g. file to delete isn't there, service isn't running) - Problem: sandbox dry-run is meaningless if the required state doesn't exist (e.g. file to delete isn't there, service isn't running)
- Feature: before running command in proxy-sandbox-mirror, classify what the command needs to be present, check if it exists, and create/set it up if missing — so the sandbox test is a faithful replica of what would happen on the host - Feature: before running command in proxy-sandbox-mirror, classify what the command needs to be present, check if it exists, and create/set it up if missing — so the sandbox test is a faithful replica of what would happen on the host