Overview
PocketBase is useful for lightweight backend apps. Better-PaaS gives it a practical home on your own server with a one-click app workflow, domain routing, HTTPS, logs, and persistent storage habits.
Catalog image and ports
Better-PaaS deploys PocketBase from ghcr.io/muchobien/pocketbase:latest on container port 8090 with health checks against /.
- Image: ghcr.io/muchobien/pocketbase:latest
- Port: 8090
- Volumes: /pb_data
Production notes for this catalog app
The admin UI is usually at /_/. The root path can return JSON until public files are uploaded.
Why host PocketBase with Better-PaaS
Better-PaaS is designed for apps like PocketBase: small services that need reliable routing, a domain, persistent data, and quick redeploys without manually editing reverse proxy files.
Deployment checklist
Before going live, decide the domain, persistent volume, backup cadence, and any environment variables PocketBase needs. For PocketBase, pay special attention to SQLite-backed APIs, auth, and admin UI.
- Choose the app catalog template or Docker image
- Add required environment variables
- Attach a persistent volume if data must survive redeploys
- Deploy and inspect logs
- Add a custom domain after the app is healthy
Operations after launch
Watch logs during the first deploy, confirm storage survives a redeploy, and include the app data in server backups. If the service exposes an admin area, use a strong password and restrict access where appropriate.
FAQ
Can PocketBase run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does PocketBase need persistent storage?
Most cms apps need some persistent storage or database plan. Treat app data and config as something to back up.