Self-host Vikunja with Levelrail

Verified

An open-source task and project manager for teams that outgrew sticky notes.

  • Authorgo-vikunjaVerified by Levelrail
  • LicenceAGPL-3.0-or-later
  • Memory256 MiB
  • Archarm64
  • Services2

How to self-host Vikunja

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • vikunja/vikunja:0.24.1
  2. Create the app

    2 services start in a single Compose app, with 2 named volume mounts for your data, on port 3456.

  3. Fill in the secrets

    3 secrets are generated and stored encrypted, 7 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Vikunja requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 tested
Ports
3456
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
AGPL-3.0-or-later, network copyleft (agpl) license
  • Verified. Verified on arm64 with image tag 16-alpine. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 3456 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 Vikunja. 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 Vikunja docs page.

Deploy Vikunja your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Vikunja from the CLI

levelrail-cli templates deploy vikunja --name my-vikunja

Deploy Vikunja with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/vikunja/deploy

Vikunja configuration

Vikunja services

ServiceImagePortsVolumes
db postgres:16-alpine none vikunja_db_data -> /var/lib/postgresql/data
vikunja vikunja/vikunja:0.24.1 3456 vikunja_data -> /app/vikunja/files

Vikunja environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Preset by the template
VIKUNJA_DATABASE_DATABASE vikunja Preset by the template
VIKUNJA_DATABASE_HOST vikunja Preset by the template
VIKUNJA_DATABASE_PASSWORD vikunja Generated at deploy
VIKUNJA_DATABASE_TYPE vikunja Preset by the template
VIKUNJA_DATABASE_USER vikunja Preset by the template
Show all 10 variables
  • VIKUNJA_SERVICE_JWTSECRETvikunjaGenerated at deploy
  • VIKUNJA_SERVICE_PUBLICURLvikunjaPreset by the template

Ports and volumes

Ports
3456
Volumes
2 named mounts: vikunja_db_data -> /var/lib/postgresql/data, vikunja_data -> /app/vikunja/files

Vikunja FAQ

How much memory does Vikunja need?

The catalog lists about 256 MiB of memory for Vikunja across its 2 services.

Does Vikunja run on arm64?

For Vikunja, arm64 is tested; amd64 is image published.

What licence is Vikunja under?

Vikunja is licensed under AGPL-3.0-or-later, which is network copyleft, so source sharing also applies when it is offered as a hosted service.

Does Vikunja need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does Vikunja bundle?

The template includes Postgres, running as its own service.

Which ports does Vikunja use?

Vikunja listens on port 3456 inside the stack.

Where does Vikunja keep its data?

In named volumes: vikunja_db_data mounted at /var/lib/postgresql/data and vikunja_data mounted at /app/vikunja/files.

Can I deploy Vikunja 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 vikunja for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, vikunja/vikunja:0.24.1 is what you deploy there.

levelrail-cli templates deploy vikunja --name my-vikunja