Self-host Linkwarden with Levelrail
A bookmark manager that archives full page snapshots, not just links, so pages stay readable.
- Authorlinkwarden
- LicenceAGPL-3.0
- Memory1 GiB
- Archarm64
- Services3
How to self-host Linkwarden
-
Pull the images
3 images are pulled on your server.
Show images
postgres:16-alpineghcr.io/linkwarden/linkwarden:v2.9.3getmeili/meilisearch:v1.11.1
-
Create the app
3 services start in a single Compose app, with 3 named volume mounts for your data, on port 3000.
-
Fill in the secrets
5 secrets are generated and stored encrypted, 4 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.
Linkwarden requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0, network copyleft (agpl) license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 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 Linkwarden. 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 Linkwarden docs page.
Deploy Linkwarden your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Linkwarden from the CLI
levelrail-cli templates deploy linkwarden --name my-linkwarden Deploy Linkwarden with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/linkwarden/deploy Linkwarden configuration
Linkwarden services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| db | postgres:16-alpine | none | linkwarden_db_data -> /var/lib/postgresql/data |
| linkwarden | ghcr.io/linkwarden/linkwarden:v2.9.3 | 3000 | linkwarden_data -> /data/data |
| meilisearch | getmeili/meilisearch:v1.11.1 | none | linkwarden_meili_data -> /meili_data |
Linkwarden environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
| DATABASE_URL | linkwarden | Generated at deploy |
| MEILI_HOST | linkwarden | Preset by the template |
| MEILI_MASTER_KEY | linkwarden | Generated at deploy |
| NEXTAUTH_SECRET | linkwarden | Generated at deploy |
| NEXTAUTH_URL | linkwarden | Preset by the template |
| MEILI_MASTER_KEY | meilisearch | Generated at deploy |
Show all 9 variables
- MEILI_NO_ANALYTICSmeilisearchPreset by the template
Ports and volumes
- Ports
- 3000
- Volumes
- 3 named mounts: linkwarden_db_data -> /var/lib/postgresql/data, linkwarden_data -> /data/data, linkwarden_meili_data -> /meili_data
Linkwarden FAQ
How much memory does Linkwarden need?
The catalog lists about 1 GiB of memory for Linkwarden across its 3 services.
Does Linkwarden run on arm64?
For Linkwarden, an arm64 image is published; amd64 is image published.
What licence is Linkwarden under?
Linkwarden is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Linkwarden need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Linkwarden bundle?
The template includes Postgres, running as its own service.
Which ports does Linkwarden use?
Linkwarden listens on port 3000 inside the stack.
Where does Linkwarden keep its data?
In named volumes: linkwarden_db_data mounted at /var/lib/postgresql/data, linkwarden_data mounted at /data/data and linkwarden_meili_data mounted at /meili_data.
Can I deploy Linkwarden 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 linkwarden for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, ghcr.io/linkwarden/linkwarden:v2.9.3, getmeili/meilisearch:v1.11.1 is what you deploy there.