Self-host Ryot with Levelrail
A self-hosted tracker for media, fitness, and other parts of life.
- AuthorIgnisDa
- LicenceGPL-3.0
- Memory512 MiB
- Archarm64
- Services2
How to self-host Ryot
-
Pull the images
2 images are pulled on your server.
Show images
postgres:16-alpineignisda/ryot:v10.3.0
-
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
3 secrets are generated and stored encrypted, 3 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.
Ryot 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
- GPL-3.0, copyleft 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 Ryot. 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 Ryot docs page.
Deploy Ryot your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Ryot from the CLI
levelrail-cli templates deploy ryot --name my-ryot Deploy Ryot with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/ryot/deploy Ryot configuration
Ryot services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| postgres | postgres:16-alpine | none | postgres_data -> /var/lib/postgresql/data |
| ryot | ignisda/ryot:v10.3.0 | 8000 | none |
Ryot environment variables
| Variable | Service | Value |
|---|---|---|
| POSTGRES_DB | postgres | Preset by the template |
| POSTGRES_PASSWORD | postgres | Generated at deploy |
| POSTGRES_USER | postgres | Preset by the template |
| DATABASE_URL | ryot | Generated at deploy |
| SERVER_ADMIN_ACCESS_TOKEN | ryot | Generated at deploy |
| TZ | ryot | Preset by the template |
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: postgres_data -> /var/lib/postgresql/data
Ryot FAQ
How much memory does Ryot need?
The catalog lists about 512 MiB of memory for Ryot across its 2 services.
Does Ryot run on arm64?
For Ryot, an arm64 image is published; amd64 is image published.
What licence is Ryot under?
Ryot is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.
Does Ryot need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Ryot bundle?
The template includes Postgres, running as its own service.
Which ports does Ryot use?
Ryot listens on port 8000 inside the stack.
Where does Ryot keep its data?
In a named volume: postgres_data mounted at /var/lib/postgresql/data.
Can I deploy Ryot 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 ryot for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image postgres:16-alpine, ignisda/ryot:v10.3.0 is what you deploy there.