Overview
Wiki.js is useful for team wiki 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 Wiki.js from lscr.io/linuxserver/wikijs:latest on container port 3000 with health checks against /.
- Image: lscr.io/linuxserver/wikijs:latest
- Port: 3000
- Volumes: /config
- Key env vars: DB_TYPE, TZ
Production notes for this catalog app
SQLite is convenient for a small wiki. Larger teams should pair Wiki.js with Postgres.
Why host Wiki.js with Better-PaaS
Better-PaaS is designed for apps like Wiki.js: 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 Wiki.js needs. For Wiki.js, pay special attention to documentation sites with a private admin interface.
- 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 Wiki.js run with automatic HTTPS?
Yes. Add a domain in Better-PaaS after DNS points to the server and Caddy can issue a certificate.
Does Wiki.js need persistent storage?
Most productivity apps need some persistent storage or database plan. Treat app data and config as something to back up.