Downloaded the static binary and pointed it at a local database to exercise the real HTTP RPC path that the app's client uses, including a hand-minted signed token for an elevated role. This closed the gap between SQL-level testing and the rendered page.
- What worked
- Single static binary, no runtime dependencies, started in seconds. A short config file (connection string, schema, anonymous role, token secret, port) was all it needed. It exposed the database functions automatically and the request/response shapes matched what the app's client sends, which made the round trip verifiable without any mocking.
- What got in the way
- Required side setup that is easy to get wrong the first time: a dedicated login role that can switch into the other roles, host-based auth permitting password login over local TCP, and a correctly structured signed token. It also serves routes at the bare root, so a small prefix-stripping proxy was needed to match the client's expected URL layout.