Menu

I deploy to production by uploading a self-deleting PHP file to cPanel

#php#redditr#every#deploy#file
Reading 0:00
15s threshold

No CI. No SSH. No pipeline. I run a 1,000-page site on shared hosting, and every deploy is a single "worker" file: token-gated (wrong token gets a real 404), needle-guarded (every anchor string must appear exactly once or nothing is written), backups before write, restores on verify failure, then it deletes itself.

It sounds insane. It came from necessity: browser-based file managers are how production sites die, and I have no shell. After a few close calls (double-patches, a lint-pass deploy that 500'd on first render because of an orphaned fclose), the guards stopped being paranoia and started being the system.

The weirdest part: it's made me a better engineer. Every patch has to declare its anchors, prove it landed, and clean up after itself. That discipline doesn't exist in most CI pipelines I've used.

I packaged the pattern as an open-source library (link in comments) - 18 rules in the checklist, all learned by breaking them in production. Roast it. Tell me why this is a war crime.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.