Overview
Jellyfin is useful for media server hosting. 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 Jellyfin from jellyfin/jellyfin:latest on container port 8096.
- Image: jellyfin/jellyfin:latest
- Port: 8096
- Volumes: /config, /cache, /media
Production notes for this catalog app
Media libraries can be large. Plan storage and backup strategy separately from the control-plane backup.
Why host Jellyfin with Better-PaaS
Better-PaaS is designed for apps like Jellyfin: 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 Jellyfin needs. For Jellyfin, pay special attention to private media streaming with persistent libraries.
- 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 Jellyfin run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does Jellyfin need persistent storage?
Most media apps need some persistent storage or database plan. Treat app data and config as something to back up.