Production from a Parking Spot
"The office is wherever I park. Production is somewhere I haven't been in years."
Right now, this laptop is open on the dinette of a 2024 Benimar T463 Special Edition. Jolie is asleep on the bench. Le is in the kitchen, six feet behind me. Outside, Caldas da Rainha, Portugal. Inside, rogerle.com servers are serving traffic to clients on three continents, and none of them are in this motorhome.
That's the whole post in one sentence. The office is here. Production lives elsewhere. People conflate the two, then ask me how the internet survives when we move.
🛰️ Office vs. Infrastructure
The motorhome is a workstation. The servers are in a datacenter that doesn't move.
It sounds obvious. It isn't — because when people read "manages a hosting business from a motorhome," their imagination puts the racks behind the bench seat. Nobody who's actually run a server thinks that. You don't put production on a vehicle that loses power every time you forget to plug in the EHU.
What lives in the motorhome:
- The development machines — Mac primary, Linux Mint laptop as backup, iPad Pro for off-hours.
- The deploy pipeline.
tar czvf package.tar.gz, scp, ssh into AlmaLinux,--strip-components=1,chown -R nginx:nginx, restart php-fpm. - The thinking.
What does not live in the motorhome:
- nginx serving traffic.
- MariaDB holding data.
- The DNS records pointing rogerle.com at anything.
Get that distinction wrong and you build the wrong architecture. Get it right and you can park anywhere with a clear view of the sky.
🔌 Power and Signal
Office workers don't think about either of these. Motorhome operators think about them constantly.
Power. Two leisure batteries, solar on the roof, EHU when the campsite gives me one. Laptop battery is for emergencies — not for an eight-hour SSH session. If the inverter is off, I'm reading docs on the iPad and saving real work for later — or firing up the Bluetti power station if I actually need to ship something.
Signal. Starlink mini, mounted on skylight, online wherever the sky is open. The exception is Portugal — when we're home, it's local cellular and fiber. Three years ago this paragraph would have been about hunting signal, multi-SIM rigs, and learning where carrier coverage maps lied. Today it's a non-issue ninety-five percent of the time. Tree cover, heavy weather, narrow valleys can still take you offline — and when they do, the old habit kicks back in: queue the work, deploy when you can.
🛠️ The Toolkit
Lean on purpose. Things break when you carry them around in a vehicle.
- Mac primary. Chrome and Firefox. Tabby for SSH.
- Linux Mint laptop as second machine. Same tools, different keyboard, for when the Mac is charging.
- iPad Pro for reading, admin checks, ticket triage.
- vi for editing on the server. Nano is for tourists.
- Vanilla PHP, vanilla JS. That's the default, not a religion. I'm trying Laravel + Alpine + Tailwind on a new project right now to see what they offer. Production stays vanilla until something clearly beats it. After thirty years, I'm still curious about the next thing — that's how I got here in the first place with the help of the Awesome Crew (Claude AI).
- tar.gz packages. The whole deploy is four commands and a verification curl. No CI/CD. No build pipeline. No Docker.
If the runway is short and the connection is sketchy, complexity is the enemy.
⚠️ What Breaks
In rough order of frequency:
- Starlink drops mid-SSH. Solved with
moshor accepting the session is gone. - Power browns out because the fridge cycled and the inverter is on the edge. Solved by knowing the motorhome better than your laptop knows it.
- Le needs the table for dinner. Solved by closing the laptop. Production keeps running.
That's the list. Three years in, I expected more.
🧱 What Doesn't
The servers. They don't break, because they're not in the motorhome, and because I treat them like they need to survive without me. Uptime monitoring runs from a third location and pings me through the helpdesk. Logs rotate. Backups happen on a schedule that doesn't ask permission.
The discipline of working from a parking spot makes the infrastructure better, not worse. You can't SSH in to fix something at three in the morning when Starlink is sulking and Le is asleep on the other side of the curtain. So you build it so you don't have to.
🧭 The Point
"Production from a parking spot" doesn't mean production lives in the parking spot. It means the operator does — and the operator's job is to make sure the operator can leave.
Everything I've built for thirty years has been quietly preparing for this. The vanilla stack. The tar.gz deploys. The discipline of doing one thing at a time. The reason it works isn't the motorhome. It's the years of choosing simple things on purpose.
This is just where I'm sitting today.
*Written from Caldas da Rainha, Portugal, with Jolie asleep on the bench and Le making coffee. All systems operational from the bench seat.*