Self-host Wakapi with Levelrail

Verified

A self-hosted, WakaTime-compatible backend for tracking coding time and stats.

  • AuthormuetyVerified by Levelrail
  • LicenceMIT
  • Memory256 MiB
  • Archarm64
  • Services2

How to self-host Wakapi

  1. Pull the images

    2 images are pulled on your server.

    Show images
    • postgres:16-alpine
    • ghcr.io/muety/wakapi:2.13.0
  2. Create the app

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

  3. Fill in the secrets

    5 secrets are generated and stored encrypted, 5 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.

Wakapi requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 tested
Ports
3000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Verified. Verified on arm64 with image tag 2.13.0. Our CI ran this exact image version and it answered on its health path. Evidence
  • 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 Wakapi. 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 Wakapi docs page.

Deploy Wakapi your way

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

Deploy Wakapi from the CLI

levelrail-cli templates deploy wakapi --name my-wakapi

Deploy Wakapi 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/wakapi/deploy

Wakapi configuration

Wakapi services

ServiceImagePortsVolumes
db postgres:16-alpine none wakapi_db_data -> /var/lib/postgresql/data
wakapi ghcr.io/muety/wakapi:2.13.0 3000 wakapi_data -> /data

Wakapi environment variables

VariableServiceValue
POSTGRES_DB db Preset by the template
POSTGRES_PASSWORD db Generated at deploy
POSTGRES_USER db Generated at deploy
WAKAPI_DB_HOST wakapi Preset by the template
WAKAPI_DB_NAME wakapi Preset by the template
WAKAPI_DB_PASSWORD wakapi Generated at deploy
WAKAPI_DB_PORT wakapi Preset by the template
WAKAPI_DB_TYPE wakapi Preset by the template
Show all 10 variables
  • WAKAPI_DB_USERwakapiGenerated at deploy
  • WAKAPI_SECURITY_PASSWORD_SALTwakapiGenerated at deploy

Ports and volumes

Ports
3000
Volumes
2 named mounts: wakapi_db_data -> /var/lib/postgresql/data, wakapi_data -> /data

Wakapi FAQ

How much memory does Wakapi need?

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

Does Wakapi run on arm64?

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

What licence is Wakapi under?

Wakapi is licensed under MIT, which is permissive, with few conditions on reuse.

Does Wakapi need configuration before it starts?

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

Which database does Wakapi bundle?

The template includes Postgres, running as its own service.

Which ports does Wakapi use?

Wakapi listens on port 3000 inside the stack.

Where does Wakapi keep its data?

In named volumes: wakapi_db_data mounted at /var/lib/postgresql/data and wakapi_data mounted at /data.

Can I deploy Wakapi 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 wakapi 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/muety/wakapi:2.13.0 is what you deploy there.

levelrail-cli templates deploy wakapi --name my-wakapi