Self-host Joplin Server (3.7.2) with Levelrail
A self-hosted sync target for the Joplin note-taking app, replacing Dropbox or OneDrive sync.
- Memory256 MiB
- Archarm64
- Services2
How to self-host Joplin Server (3.7.2)
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16joplin/server:3.7.2
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 22300.
-
Fill in the secrets
2 secrets are generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Joplin Server (3.7.2) requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 22300
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 22300 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Joplin Server (3.7.2). New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Joplin Server (3.7.2) docs page.
Deploy Joplin Server (3.7.2) your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Joplin Server (3.7.2) from the CLI
levelrail-cli templates deploy joplin-server --name my-joplin-server Deploy Joplin Server (3.7.2) with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/joplin-server/deploy Joplin Server (3.7.2) configuration
Joplin Server (3.7.2) services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16 | none | joplin_db_data -> /var/lib/postgresql/data |
| joplin | joplin/server:3.7.2 | 22300 | none |
Joplin Server (3.7.2) environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| POSTGRES_USER | db | Preset by the template |
| APP_BASE_URL | joplin | Preset by the template |
| DB_CLIENT | joplin | Preset by the template |
| POSTGRES_DATABASE | joplin | Preset by the template |
| POSTGRES_HOST | joplin | Preset by the template |
| POSTGRES_PASSWORD | joplin | Generated at deploy |
Show all 9 variables
- POSTGRES_USERjoplinPreset by the template
Ports and volumes
- Ports
- 22300
- Volumes
- 1 named mount: joplin_db_data -> /var/lib/postgresql/data
Joplin Server (3.7.2) FAQ
How much memory does Joplin Server (3.7.2) need?
The catalog lists about 256 MiB of memory for Joplin Server (3.7.2) across its 2 services.
Does Joplin Server (3.7.2) run on arm64?
For Joplin Server (3.7.2), an arm64 image is published; amd64 is image published.
Does Joplin Server (3.7.2) need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Joplin Server (3.7.2) bundle?
The template includes Postgres, running as its own service.
Which ports does Joplin Server (3.7.2) use?
Joplin Server (3.7.2) listens on port 22300 inside the stack.
Where does Joplin Server (3.7.2) keep its data?
In a named volume: joplin_db_data mounted at /var/lib/postgresql/data.
Can I deploy Joplin Server (3.7.2) on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id joplin-server for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16, joplin/server:3.7.2 is what you deploy there.