A record -> 192.168.8.175 (Caddy's LAN IP), created via Technitium's REST API (login -> createToken -> zones/records/add) in a single in-memory call. Neither the admin credential nor the resulting session/ API token was ever printed to output or written to disk, and the token wasn't persisted anywhere after the call completed — it existed only for the lifetime of that one process. Verified: dig @192.168.8.2 +short oikos.hubris.network -> 192.168.8.175. End-to-end confirmation that DNS + Caddy + the Authentik gate are all wired correctly: curl https://oikos.hubris.network/ now returns a 302 (the forward-auth redirect firing before the not-yet-deployed backend would even matter) instead of failing to resolve/connect. This closes out every part of the console rollout except the actual apps-side bootstrap (oikos/console/deploy/README.md "One-time setup"), which remains pending direct operator execution. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB