Overview
Linkding is useful for bookmark management. 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 Linkding from sissbruecker/linkding:latest on container port 9090 with health checks against /.
- Image: sissbruecker/linkding:latest
- Port: 9090
- Volumes: /etc/linkding/data
- Key env vars: LD_SUPERUSER_NAME, LD_SUPERUSER_PASSWORD
Why host Linkding with Better-PaaS
Better-PaaS is designed for apps like Linkding: 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 Linkding needs. For Linkding, pay special attention to private bookmark archiving on a custom domain.
- 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 Linkding run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does Linkding need persistent storage?
Most productivity apps need some persistent storage or database plan. Treat app data and config as something to back up.