Handling API drift after a deploy
A browser tab can outlive several deploys. One response header, a latch, and links that quietly become full page loads bring everyone back onto the current build.
I'm Pat O'Meara. I build and run Maintainly, a maintenance management app for the people who keep physical things working.
I write here about Laravel, Statamic, and the unglamorous parts of keeping software alive once the launch is over.
A browser tab can outlive several deploys. One response header, a latch, and links that quietly become full page loads bring everyone back onto the current build.
Vite, Tailwind v4, and a handful of shell aliases. The whole front-end toolchain for this site fits on one screen.
Keeping content in git instead of a database changes how a small site is built, reviewed, and deployed — mostly for the better.
Queued jobs are easy to write and awkward to test. A few habits keep the assertions honest without booting a real worker.