Designing an API gateway on a laptop
An allowlist and a token check in front of an API, built in Caddy on a laptop, and the problems that turned up long before production.
Ideas and imagination are boundless
I'm an engineer, whose expertise and passion lies in development work, microservice architecture, software architecture, solution designing, network infrastructure setup (clusters, cloud), problem solving, data algorithms, big data, data mining, machine learning (ML), natural language processing, artificial intelligence (AI), and always ready to debug that elusive issue, and learn new things.
An allowlist and a token check in front of an API, built in Caddy on a laptop, and the problems that turned up long before production.
Three apps in one stack and three different answers to where a config value really comes from, so the same env setup doesn't behave the same way twice.
Cookies and Origin checks only behave like production if the hostnames do, so every local site gets real HTTPS from a local CA, except Firefox has its own idea about which CAs to trust.
There was no way to run the whole platform locally, so I wrote a small Go CLI that renders plain docker compose projects from a service catalog, and most of what I learned had nothing to do with compose.
A key swap on the Magic Keyboard read back as applied and still did nothing when launchd ran it, and the fix was a permission I'd given to the wrong binary.
A small script and a LaunchAgent turn Wi-Fi off while the CalDigit TS5 has a working network, and back on when it doesn't.
The site had been stuck on an old Hugo for years. Splitting the move into eleven tasks and giving each one to an agent got it done in an afternoon.
I renamed four nodes because the old domain annoyed me. The cluster stayed green for weeks while sitting one reboot away from losing every worker.
If you want to know a little more about me, check out my LinkedIn, GitHub, and Blog.