"Sovereign in Seven Days: A Bar Builds Its Own Everything"
I run a lot of domains. Most of them live together on one big server, sharing an identity provider, a mail stack, a database, like roommates who have stopped noticing each other's dishes.
Then I registered bitchlove.com — a neon dive bar that exists only on the internet — and I gave it one rule before a single byte was deployed:
This box is a sovereign, self-sufficient, separate entity. Its own auth. Its own mail. Its own everything. Deliberately not wired into the rest of the estate.
I said it like a Marine posting a sentry. And then I spent seven days finding out what "its own everything" actually costs.
Day one to day seven
Day one, the site was a landing page. Neon logo, one line of copy:
Tough love, served neat. Pouring soon.
That's it. A sign in the window of an empty building.
Day seven, the empty building had:
- The site itself, plus an admin back-office
- Its own identity provider — every service on the box authenticates against it, and nothing else on earth
- Its own mail server, with DKIM, SPF, and DMARC set up properly
- Webmail, so the bar can read its own mail
- A WordPress blog in a dark neon theme
- An IRC network with a web client
- A Nextcloud with 64 apps and a full office suite
A fictional bar now has better IT than most actual bars. Most actual companies. It can hire nobody, serve nothing, and it still has single sign-on.
The server that vouches for itself
My favorite detail is the mail. The box signs its own DKIM — fine, normal. But I also pointed the machine's own cron emails through its own authenticated SMTP.
Which means every message the server sends about itself is cryptographically signed by itself. The 4 a.m. "your backup ran" email arrives with the server's own signature on it, like a bar owner notarizing his own diary.
Character-building for a server. Somebody on that box has accountability, and it isn't me.
The IRC network got the same treatment: TLS on the public side, and the plaintext legs confined to the internal container network where nothing hostile can stand. The web client is pre-seeded so a visitor lands directly in the house channel — zero configuration, no server fields, no nick registration ceremony. You walk in, you're at the bar. That's the whole design brief.
A bar needs regulars
A dive bar with no people is just a lighting rig, so the participatory stuff went in early:
- A Quote of the Day over the door
- A public submission wall — anyone can throw a line at it, everything queues for review before it posts, and there's a 5-per-hour rate limit because I have met the internet
- An anonymous survey where your answers are keyed to a random browser token. No account, no email, no identity stored against your opinions. Country only. You can tell the bar what you really think and the bar genuinely cannot rat you out.
And the merch page, which I'm proud of because it inverts the entire concept of merch: nothing gets printed until 50 people say they'd buy it. Six items, each with a live count ticking toward the threshold. One is a real neon sign. One is a matchbook with a submission from the wall printed inside the flap — the internet's heckling, preserved in cardboard.
No inventory, no garage full of unsold shirts. The bar takes votes, not risks. Smarter than me on both counts.
The night the neon turned to mud
Now the failure, because there's always a failure.
Mid-week, the signature pink neon started looking muddy. Not broken — the hex code was correct, the CSS was correct, everything a computer could verify was correct. It just looked like someone had unplugged the sign and painted it on.
I stared at it for a long time before the diagnosis landed: warm pink on a warm brown background. Neon doesn't glow because it's bright. It glows because of temperature contrast — a hot color screaming against a cool ground. Put warm on warm and the physics leaves the room. The pixels were right and the light was wrong.
So instead of arguing hex codes in the abstract — the traditional way, where everyone squints at swatches and lies — I built a page that showed four candidate palettes rendered on the real content. Same page, four grounds, pick the one where the sign actually burns.
The winner: Midnight, a violet-black. And then came the note every developer knows is coming: "a touch of purple." So the logo's halo got a violet bloom on its outer edge — which, I'll grudgingly admit, is genuinely how neon photographs. The glass is pink; the air around it goes violet. The note was correct. I hate when the note is correct.
The recolor itself swapped 69 color values across 15 files, by script, with one non-negotiable guard: the run aborts if the signature pink #ff2e88 ever disappears from the codebase. You can automate a rebrand. You cannot automate away the brand. That hex code is the bar.
The honest ledger
Sovereignty has a bill, and here's the line item I wrote in red that same week: seven services, ten-plus containers, four databases — and for several days, zero backups of any of it.
A completely self-contained internet, dependent on nothing, protected by nothing. The most independent single point of failure I have ever built. I flagged it as the standing gap, and it got closed: a first 18.5GB snapshot, then an automated weekly snapshot-and-prune job so the bar backs itself up and throws out its own old bottles. Fixed. But for a few days there, the whole sovereign nation was one disk failure from never having existed.
Even the launch announcement fought back. The featured screenshot had to be retaken with a virtual-time budget, because the first capture caught the neon mid-flicker — frozen on the exact frame where the flicker animation drops the text-shadow — and the logo looked tragically unplugged. My screenshot tooling now has to account for the fact that I built a sign that pretends to be dying on purpose.
Seven days. One bar. Its own everything. It signs its own mail, reviews its own wall, backs itself up, and glows correctly against a cool ground, exactly like the physics demands.
I don't even drink much. I just apparently needed someone new to serve.
— J
Filed from the only machine in my fleet that shares nothing with the others, and acts like it knows it.
