Self-host Yamtrack with Levelrail
A self-hosted media tracker for movies, TV, anime, manga, games, and books.
- AuthorFuzzyGrim
- LicenceAGPL-3.0
- Memory512 MiB
- Archarm64
- Services2
How to self-host Yamtrack
-
Pull the images
2 images are pulled on your server.
Show images
redis:7-alpineghcr.io/fuzzygrim/yamtrack:0.26.3
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
1 secret is generated and stored encrypted, 2 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.
Yamtrack requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 8000
- 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 8000 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 Yamtrack. 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 Yamtrack docs page.
Deploy Yamtrack your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Yamtrack from the CLI
levelrail-cli templates deploy yamtrack --name my-yamtrack Deploy Yamtrack with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/yamtrack/deploy Yamtrack configuration
Yamtrack services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| redis | redis:7-alpine | none | none |
| yamtrack | ghcr.io/fuzzygrim/yamtrack:0.26.3 | 8000 | yamtrack_data -> /yamtrack/db |
Yamtrack environment variables
| Variable | Service | Value |
|---|---|---|
| REDIS_URL | yamtrack | Preset by the template |
| SECRET | yamtrack | Generated at deploy |
| URLS | yamtrack | Preset by the template |
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: yamtrack_data -> /yamtrack/db
Yamtrack FAQ
How much memory does Yamtrack need?
The catalog lists about 512 MiB of memory for Yamtrack across its 2 services.
Does Yamtrack run on arm64?
For Yamtrack, an arm64 image is published; amd64 is image published.
What licence is Yamtrack under?
Yamtrack is licensed under AGPL-3.0, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Yamtrack need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Yamtrack bundle?
The template includes Redis, running as its own service.
Which ports does Yamtrack use?
Yamtrack listens on port 8000 inside the stack.
Where does Yamtrack keep its data?
In a named volume: yamtrack_data mounted at /yamtrack/db.
Can I deploy Yamtrack 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 yamtrack for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image redis:7-alpine, ghcr.io/fuzzygrim/yamtrack:0.26.3 is what you deploy there.