picopaas-release
Backups health cleanup, account API keys, admin defaults
Cleaner backup health for deleted apps, live volume usage, API keys on the Account page, per-user key management for admins, and per-app defaults with node-capped ceilings.
picopaas-release
Cleaner backup health for deleted apps, live volume usage, API keys on the Account page, per-user key management for admins, and per-app defaults with node-capped ceilings.
picopaas-release
A UI polish round: copy buttons for custom-domain DNS, queued backup deletes, volume usage bars, renames that no longer redeploy, cleaner logs and consistent buttons.
picopaas-release
Today's round was mostly refinements and admin tooling: per-app backup controls, ceilings and failure reasons, a new Admin Settings tab, platform logs, bug fixes, n8n and Grafana recipe updates.
picopaas-release
Backups are now one package per backup, with the database dump, blob storage archive and volume, downloadable as a single checksummed .tar.gz. We also caught and fixed a bug that had been breaking our own MySQL dumps.
picopaas-release
We priced a port to Azure and AWS and looked at making apps Kubernetes CRDs. The verdict is that we are staying on DigitalOcean, with AWS as plan B.
picopaas-release
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.
picopaas-release
We restored my old personal blog onto PicoPaaS end to end: a non-root nginx and PHP-FPM image, persistent volumes, presigned uploads and a one-time restore. Here is what it took, how patching works, and what is next.
picopaas-release
Today we shipped pod events and audit log downloads, admin promote and demote with a recovery CLI, fixes from our own pentest, and the first four database scaling fixes. The live end-to-end run passed 19 tests with none failing.
picopaas-release
We asked what it would take to run a real WordPress blog on PicoPaaS. The answer is yes, with a custom image and a few habits, and no persistent volume needed to start.
picopaas-release
This blog felt sluggish right after we added an outbound bandwidth cap. The cap was innocent: Ghost was being CPU-throttled. Here's how we measured it and what fixed it.
picopaas-release
The app page is now two pages: App health for status, logs and metrics, and Settings for everything you can change.
picopaas-release
We made the platform harder to abuse: more outbound ports and address ranges are blocked, each app gets an outbound bandwidth cap, and there are now terms of use.