Sunday, AM, Features Added, Dev Cycle Reworked
Before 11am
Some mornings you answer email.
Some mornings you quietly rearrange the entire stack before most people finish their first cup of coffee.
Today was the second kind.
By 11am the site had a public Index Viewer, a new Go trace router running every minute, TLS moved to the edge, authentication added to the dev environment, and Windows port forwarding rewritten so the edge certificate could route cleanly back into WSL.
None of that was scheduled. It was just what needed to happen.
And the interesting part is how all of it connects.
The Index Viewer
This started because I needed to see something.
Instead of dragging full OpenSearch Dashboards onto the public host, I built a controlled Index Viewer. You choose from an allowed list of indexes and you can browse the data. No free-form query input. No cluster controls exposed. Just a safe window into live operational data.
It exists because I needed it for something specific. But now it is part of the site.
Every time I build something like that, the curtain pulls back a little more. The reader is not just seeing a polished page. They are seeing the operational layer underneath. The site stops being static content and starts behaving like an instrument panel.
The Go Trace Router
Then I wrote a trace router in Go that runs from cron once per minute.
It observes, aggregates, shapes the data, and feeds the Web Trace view.
It is not flashy. It just runs.
But that is the shift. The site now has a pulse. Every minute it updates its own understanding of how traffic is moving through the stack.
That is different from publishing content. That is building a system that watches itself.
Moving TLS to the Edge
Dev was serving its own certificate inside WSL.
It worked. But it was unnecessary complexity.
So I moved TLS termination to the edge. Nginx handles the certificate. Dev serves plain HTTP internally. Simpler trust boundary. Fewer moving parts in the VM. Clear separation between public encryption and internal service.
When you can remove components instead of stacking more on top, that is progress.
Locking Dev Down
Dev was reachable. Not editable, not dangerous, but reachable.
So I added authentication at the Nginx layer.
Now dev sits behind a gate. Still accessible when I need it from wherever I am. But not casually browsable.
It is not paranoia. It is just discipline.
The Windows and WSL Surgery
To make the edge certificate route correctly back into dev running inside WSL over WireGuard, I had to rework Windows port forwarding and firewall rules.
Traffic now flows cleanly:
Browser
→ Linode
→ Nginx
→ WireGuard
→ Windows
→ Port proxy
→ WSL
→ App
If you understand that path end to end, changes like this take minutes.
If you do not, they take days.
That is the difference.
What This Really Means
On the surface it looks like:
A public Index Viewer
A trace system
A secured dev environment
Cleaner TLS
Simplified WSL
But underneath it is something else.
Every change makes the backend more visible.
The site is not just content anymore. It is infrastructure in motion. You can see how it works. You can see where traffic flows. You can see how data is shaped and exposed.
That transparency is intentional.
All Before 11am
There were no meetings.
No tickets.
No committee.
Just understanding the stack from the browser all the way down to the OS and back again.
Speed is not about typing fast.
Speed is about knowing where the edges are.
And sometimes, before 11am, you redraw them.