one screen to run the whole thing
Tuesday morning. Coffee going cold. I'm counting browser tabs again.
Radio admin. The static build folder. Gumroad in three places. The affiliate spreadsheet. The email tool. A terminal where the deploy lives. The thing that checks if the box is still breathing. Twelve open windows to do one small job, and the job was just "post a thing and see if anyone touched it."
That's when I started building the cockpit.
The problem nobody warns you about
When you own your whole press, you own the whole cockpit too. Nobody's handing you a tidy dashboard. The platforms give you dashboards so you'll stay inside their walls and never notice the walls. I left the walls. The bill for that is twelve tabs and a head full of where-did-I-put-that.
So I'm running a one-person network off a box that costs less than a sandwich, and the bottleneck isn't the box. It's me, holding a map nobody drew.
What I'm building
One screen. Plain PHP, the way I like it, sitting where I can reach it and nobody else can.
Top of the screen is the heartbeat. Is the radio on air. Is the site up. When did the last deploy land. Green or red, no scrolling. I want to glance and know, the way you glance at a fuel gauge.
Under that, the controls I actually reach for. Stage a draft. Promote it live. Push the next batch of songs to the station. Pull today's sales without opening four merchant tabs. Each one a button, each button doing exactly one thing I used to do by hand across six tools.
I wrote the first version today and it's ugly. A list of links and two status lights, half of them lying because I hadn't wired the checks yet. Doesn't matter. The shape is right. A pilot doesn't fly the paint job.
The paranoid part
Here's where the old Air Force wiring kicks in. A cockpit that can do anything can also do anything by accident, or by somebody who isn't me. So the rule, written down before I write the dangerous code: it reads broad, acts narrow. It can look at everything. It can only touch a short list, and the touching needs me at the keys.
No key to the kingdom living on a public server. The brain stays home, on my machine, and reaches out. The server never holds the thing that could burn it all down. If somebody walks through the front door someday, they find a screen showing lights and a few blunt buttons, not the master keys.
Why bother
Because the network only matters if one tired guy can run it on a slow morning. Press, signal, store, brain. Four engines, one throttle. The win isn't that it looks like mission control. The win is that I close eleven tabs.
It's nowhere near done. The status lights still fib. The buttons that move money aren't wired, on purpose, until I trust the rails under them. But this morning I posted, promoted, and checked the take from one screen, coffee still in reach.
Eleven tabs closed. That's the whole report.