Overview
ntfy is useful for pub-sub notifications. 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 ntfy from binwiederhier/ntfy:v2 on container port 80.
- Image: binwiederhier/ntfy:v2
- Port: 80
- Volumes: /var/cache/ntfy, /etc/ntfy
Why host ntfy with Better-PaaS
Better-PaaS is designed for apps like ntfy: 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 ntfy needs. For ntfy, pay special attention to topic-based notifications over HTTP.
- 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 ntfy run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does ntfy need persistent storage?
Most notifications apps need some persistent storage or database plan. Treat app data and config as something to back up.