Evening devlog: a ten-year-old backup, restored
A ten-year-old backup script restored our old blog on PicoPaaS, plus WordPress boot actions, Blob storage naming, a WordPress-to-Ghost migrator, and an honest status on backups.
Since WordPress runs on PicoPaaS this afternoon, we have kept going. Here is the evening's worth of changes, including one restore that surprised us and one backup system that is only half proven.
A ten-year-old backup, restored
The shape of the evening: restore the old blog, find what breaks on a modern WordPress, and turn each fix into a platform or image feature so the next person does not have to repeat it.
The old personal blog is now fully restored and running on PicoPaaS. The source was a backup made by a shell script written more than ten years ago. Nobody ever tested it by restoring, and we fully expected to spend the evening patching around gaps. It worked. That is a nice reminder that boring tools (tar, mysqldump) age well.
WordPress boot-time admin actions
The WordPress example image can now do a few admin chores at container start, driven by env vars:
WP_REMOVE_PLUGINSremoves named plugins before WordPress loads.- A password reset for a chosen user. Outbound mail is blocked on the platform, so the new password is printed once to the app logs.
- Clearing login lockouts, for when a security plugin locks you out of your own site.
We used these to drop Jetpack and an old code highlighter. The highlighter was a fun bug: the old prettify script expected the code block whitespace of its day, while WordPress 7 styles blocks with white-space: break-spaces, so code blocks collapsed. Removing the plugin (WP_REMOVE_PLUGINS=code-prettify) fixed it, and the note is in the WordPress docs.
Downloads under /kab/
The downloads directory was broken. Two causes: nginx directory listings are now opt-in via WP_AUTOINDEX_PATHS (so only paths you name are listable), and redirects are now relative instead of pointing at an internal port-8080 address.
Both fixes are small, but they matter for anyone hosting a downloads folder: you now decide which paths are browsable, and links no longer send visitors to an address they cannot reach.
Blob storage, and volumes up to 10 GiB
Now that persistent volumes exist, plain "Storage" was ambiguous. It is now "Blob storage" in the UI and docs, and the apps list summarises each app as DB (engine) + blob storage + volume. Admins also get a volume ceiling, default 10 GiB.
WordPress to Ghost
We wrote a migration script and walkthrough for moving a WordPress export to Ghost. A dry run on the old blog found 78 posts, 2 pages and 17 images, and we tested it end to end against a local Ghost: everything imported, and a rerun skipped all of it. The author will run it himself against a real Ghost on PicoPaaS as a usability test, so expect rough edges to turn into fixes. One known limit: Ghost cannot redirect old ?p=N URLs.
The rename is display text only. API fields and contracts are unchanged, and the user guide now has a short table on when to use blob storage and when to use a persistent volume.
Backups: what is and is not done
We want to be modest here. The design uses restic with an encrypted repository per app, covering database dumps and blob storage, written to a dedicated backup bucket. Phase 1 has shipped and is enabled on the platform.
The first live run hung. The backup namespace's network policy blocked Spaces' private VPC address, and restic retries silently for about fifteen minutes before giving up. The fix is an egress rule for Spaces, plus progress lines in the job output and timeouts so a stall is visible quickly instead of looking like a hang.
We also simplified retention to one daily, one weekly and one monthly snapshot. For long-term archival, owners should download their backups; downloads are coming next. Scheduled backups are opt-in for now.
The live restore drill has not been done yet. A backup you have not restored is a hope, not a backup, so that is the next thing on the list. We will write it up either way.