Self-host Wallos with Levelrail

Verified

A personal subscription tracker that shows what you pay each month, with reminders and multi-currency support.

  • AuthorelliteVerified by Levelrail
  • LicenceGPL-3.0
  • Memory128 MiB
  • Archarm64
  • Services1

How to self-host Wallos

  1. Pull the images

    One image is pulled on your server.

    Show images
    • bellamy/wallos:5.8.1
  2. Create the app

    One service starts in a single Compose app, with 2 named volume mounts for your data, on port 80.

  3. Fill in the secrets

    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.

Wallos requirements

Memory
About 128 MiB
Architectures
amd64 image published, arm64 tested
Ports
80
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0, copyleft license
  • Verified. Verified on arm64 with image tag 5.8.1. Our CI ran this exact image version and it answered on its health path. Evidence
  • Host ports. It publishes port 80 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 Wallos. 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 Wallos docs page.

Deploy Wallos your way

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

Deploy Wallos from the CLI

levelrail-cli templates deploy wallos --name my-wallos

Deploy Wallos 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/wallos/deploy

Wallos configuration

Wallos services

ServiceImagePortsVolumes
wallos bellamy/wallos:5.8.1 80 wallos_db -> /var/www/html/dbwallos_logos -> /var/www/html/images/uploads/logos

Wallos environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
80
Volumes
2 named mounts: wallos_db -> /var/www/html/db, wallos_logos -> /var/www/html/images/uploads/logos

Wallos FAQ

How much memory does Wallos need?

The catalog lists about 128 MiB of memory for Wallos.

Does Wallos run on arm64?

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

What licence is Wallos under?

Wallos is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does Wallos need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Wallos use?

Wallos listens on port 80 inside the stack.

Where does Wallos keep its data?

In named volumes: wallos_db mounted at /var/www/html/db and wallos_logos mounted at /var/www/html/images/uploads/logos.

Can I deploy Wallos 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 wallos for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image bellamy/wallos:5.8.1 is what you deploy there.

levelrail-cli templates deploy wallos --name my-wallos