Self-host Ryot on a managed VPS: your media and fitness tracker

To self-host Ryot on a managed VPS is to keep the history of what you watch, read, play and lift on a server of your own, which our teams keep up to date and monitor day and night. Ryot is a free, open source tracker under the GPL-3.0 license, for movies, shows, books, games, podcasts, music and workouts. This guide follows its official Docker image at version v10.5.8, and we ran every command on a Simafri VPS before writing it: installation with Docker Compose and PostgreSQL, HTTPS, the first account, the API keys of each media type, backups and updates.

Simon Vasconcelos Lee By Published on 19 November 202611 minute read

All guides

In short

  1. The GPL-3.0 license lets you run Ryot for yourself, your family or your club with no license to buy; Ryot Pro, a paid key, adds features on top of the same image.
  2. Install it with Docker Compose: the image ignisda/ryot and PostgreSQL 18, with port 8000 published on 127.0.0.1 behind an HTTPS reverse proxy.
  3. Put the database password and SERVER_ADMIN_ACCESS_TOKEN in a .env file, and set FRONTEND_URL to your public address.
  4. The first account you create becomes the administrator; then set USERS_ALLOW_REGISTRATION=false to close sign-ups on a private instance.
  5. Books work at once; movies and shows need a TMDB token, video games a Twitch application. Back up with pg_dump, then update by changing the image tag.

What Ryot does

Ryot, for “Roll Your Own Tracker” and pronounced “riot”, keeps in one place what you have seen, read, played and trained, with statistics, a calendar of what is coming and collections of your own. Its developer, IgnisDa, writes it in Rust, with a web interface you can install on a phone as an app.

What the GPL-3.0 license allows

Ryot is published under the GNU General Public License, version 3 (GPL-3.0). You can use it free of charge, for yourself, your family, your club or your company, copy it and modify it. If you distribute a modified version, you distribute its source code under the same license. The software is provided without warranty.

Ryot Pro is a paid key sold by its developer, which unlocks extra features such as profile sharing and personalized recommendations. It goes in a SERVER_PRO_KEY variable of the same image, and the server returns to the community version if the key expires. Nothing in this guide needs it.

The resources to plan for

The documentation sets no minimum size, and Ryot is light. Here is what we measured on our test VPS, freshly installed:

Server size therefore depends on the number of users and on the other applications you run beside Ryot. On a managed VPS, tell us about your usage and we will recommend the right size.

Installing with Docker Compose

Ryot ships as a single image, ignisda/ryot, also published as ghcr.io/ignisda/ryot, which serves both the interface and the API on port 8000. It needs PostgreSQL 15 or later, run beside it in its own container. On a server with Docker Engine and its Compose plugin, installed from Docker’s repository for Ubuntu, create a folder such as /opt/ryot and put this compose.yaml in it, based on the file of the installation page:

compose.yaml
services:
  ryot-db:
    image: postgres:18-alpine
    restart: unless-stopped
    environment:
      - TZ=Europe/Amsterdam
      - POSTGRES_DB=ryot
      - POSTGRES_USER=ryot
      - POSTGRES_PASSWORD=${POSTGRES_PASSWORD:?set POSTGRES_PASSWORD in .env}
    volumes:
      - postgres_storage:/var/lib/postgresql
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U ryot -d ryot"]
      interval: 5s
      timeout: 5s
      retries: 10

  ryot:
    image: ignisda/ryot:v10.5.8
    restart: unless-stopped
    ports:
      - "127.0.0.1:8000:8000"
    environment:
      - TZ=Europe/Amsterdam
      - FRONTEND_URL=https://ryot.example.com
      - DATABASE_URL=postgres://ryot:${POSTGRES_PASSWORD}@ryot-db:5432/ryot
      - SERVER_ADMIN_ACCESS_TOKEN=${SERVER_ADMIN_ACCESS_TOKEN:?set SERVER_ADMIN_ACCESS_TOKEN in .env}
    depends_on:
      ryot-db:
        condition: service_healthy

volumes:
  postgres_storage:

The two secrets go in a .env file next to it, which Docker Compose reads on its own. Create it readable by root only, then start the stack:

Terminal, in /opt/ryot
umask 077
printf 'POSTGRES_PASSWORD=%s\nSERVER_ADMIN_ACCESS_TOKEN=%s\n' "$(openssl rand -hex 24)" "$(openssl rand -hex 32)" > .env
umask 022
docker compose up -d
docker compose ps

The first start runs the database migrations and downloads the exercise catalog; on our test VPS, Ryot answered in a few seconds. To check that it responds:

Terminal
curl -s -o /dev/null -w "%{http_code}\n" http://127.0.0.1:8000/health
curl -s http://127.0.0.1:8000/backend/config | head -c 300

The first command answers 200. The second returns the configuration the server loaded, as JSON, with its secrets redacted: a handy way to check a variable.

HTTPS: the reverse proxy

The container serves Ryot over HTTP, on port 8000. HTTPS is handled by a reverse proxy in front of it, which must forward the public Host header and X-Forwarded-Proto. We tested Caddy, installed from its official Debian and Ubuntu repository: it obtains the Let’s Encrypt certificate itself, renews it, and forwards these headers by default.

/etc/caddy/Caddyfile
ryot.example.com {
	reverse_proxy 127.0.0.1:8000
}
Terminal
sudo systemctl reload caddy

The first account, sign-ups and invitations

Ryot has no default account, and sign-ups are open on a new instance. The first account created gets the Admin role; the following ones are normal users. Create yours right after the first start:

  1. Open your address: Ryot shows its login page.
  2. Click “Create a new account?”, then enter a username and a password twice.
  3. Register, then log in with your new credentials: you land on the dashboard, with an onboarding tour.
  4. Under “Settings”, “Users”, your account appears with the Admin role.

For a private instance, close sign-ups: add USERS_ALLOW_REGISTRATION=false to the environment of the ryot service, then run docker compose up -d. On our test VPS, the “Create a new account?” link disappeared, and a sign-up attempted from the registration address was refused by the server with “Registration is disabled”.

Inviting the other users

  1. Under “Settings”, “Users”, click the + button next to the title.
  2. Enter the person’s username: Ryot creates the account and shows a one-time link.
  3. Send the link: the person opens it, chooses a password, then logs in.

We tested it with sign-ups closed: the invited account was created as a normal user, its password was set from the link, and it reached its own dashboard.

To sign in with your company accounts instead, Ryot supports OpenID Connect: set SERVER_OIDC_CLIENT_ID, SERVER_OIDC_CLIENT_SECRET and SERVER_OIDC_ISSUER_URL, and declare https://ryot.example.com/api/auth as the redirect address at your provider.

Movies, shows and games: the API keys

Ryot finds the details and covers of each media type at a provider. Some work without a key, others need yours, since the shared keys were removed in v9:

MediaProviderWhat to set
BooksOpen LibraryNothing: it works at once. Google Books and Hardcover are optional, with their API key
Movies and showsTMDB, or TVDBMOVIES_AND_SHOWS_TMDB_ACCESS_TOKEN, the API Read Access Token of a free TMDB account, or MOVIES_AND_SHOWS_TVDB_API_KEY
Video gamesIGDB, through TwitchVIDEO_GAMES_TWITCH_CLIENT_ID and VIDEO_GAMES_TWITCH_CLIENT_SECRET, from an application in the Twitch developer console
MusicSpotify, optionalMUSIC_SPOTIFY_CLIENT_ID and MUSIC_SPOTIFY_CLIENT_SECRET
Anime importMyAnimeListANIME_AND_MANGA_MAL_CLIENT_ID, needed only to import from MyAnimeList

These keys are secrets: put them in the .env file, add a line such as - MOVIES_AND_SHOWS_TMDB_ACCESS_TOKEN=${MOVIES_AND_SHOWS_TMDB_ACCESS_TOKEN} to the environment of the ryot service, then run docker compose up -d. The configuration page of the documentation lists every other variable.

Backups

Everything lives in two places: the PostgreSQL database, in the postgres_storage volume, and your .env file. Keep the latter safe: SERVER_ADMIN_ACCESS_TOKEN is needed to read the two-factor secrets stored in the database. The PostgreSQL image includes pg_dump:

Terminal, in /opt/ryot
docker compose exec -T ryot-db pg_dump -U ryot -Fc ryot > ryot-$(date +%F).dump
cp .env env-$(date +%F).bak

Schedule this copy and send it off the server. Stored on the disk, the dumps are also included in the server’s nightly backups.

Restoring

On the same or a new installation, with the same .env, stop the application, load the dump, then start it again:

Terminal, in /opt/ryot
docker compose stop ryot
docker compose exec -T ryot-db pg_restore -U ryot -d ryot --clean --if-exists --no-owner < ryot-2026-11-18.dump
docker compose start ryot

We tested the whole cycle on our VPS: dump, the database actually deleted, restore. The two accounts, their collections and the 876 exercises came back, and the administrator signed in again at once.

Ryot also exports your own data as JSON, from the “Imports and Exports” settings page, which it can import back. That export needs S3-compatible file storage; the database dump above works without it.

Updates

Ryot is released often, on a loosely weekly basis. Read the release notes, take a backup, change the image tag in the compose.yaml, then pull the new image and recreate the container. The database migrations run on their own at startup:

Terminal, in /opt/ryot
docker compose pull
docker compose up -d
docker compose logs ryot | grep -i migration

Telemetry

Ryot collects anonymous usage data, page views and a few events, on a self-hosted Umami instance of its developer. To turn it off, add DISABLE_TELEMETRY=true to the environment of the ryot service, then run docker compose up -d.

Who does what on a managed VPS

Self-hosting means running the server on top of the application. On a managed VPS, our teams take charge of the server and proactively monitor your instance; Ryot remains your software, with your history and your settings.

TopicOur teamsYou
The serverSystem and security updates, server interventions includedThe timing that suits you
MonitoringServer monitored 24/7, with intervention without waiting for your callYour history, your collections and your integrations in Ryot
RyotProactive monitoring: errors, slowdowns, database and disk space spotted, fix recommendedIts installation, updates, API keys and settings, which you apply, yourself or through your AI assistant
UsersThe server that carries them, monitored and backed upAccounts, sign-ups and single sign-on
BackupsEvery night, encrypted and kept off the machine; restores includedRyot’s own database dumps and JSON exports, and the restore request, when you need one
MigrationYour current server migrated, free of chargeThe timing of the switch

If you would rather have our teams work inside the application itself, that service is billed by the hour or at a fixed rate, with an estimate shared before the work starts.

Ryot, on a server run for you

With a Simafri Managed VPS, our teams keep your Ryot instance’s server up to date, monitor it day and night and step in without waiting for your call; they also proactively monitor your instance and recommend useful fixes, which you apply, yourself or through your AI assistant. Backups are encrypted every night and kept off the machine, restores are included, and migrating your current server is free.

Explore Managed VPS

Frequently asked questions

Is Ryot free?

Yes. Ryot is under the GPL-3.0 license: you can run it for yourself, your family or your team with no license to buy. Ryot Pro is an optional paid key that adds features to the same image. What remains is the cost of the server that runs it.

How do I install Ryot with Docker Compose?

Use the ignisda/ryot image and PostgreSQL 18 in a compose.yaml. Put the database password and SERVER_ADMIN_ACCESS_TOKEN in a .env file, set FRONTEND_URL to your https address, publish port 8000 on 127.0.0.1, run docker compose up -d, and put an HTTPS reverse proxy in front.

What is the default Ryot login?

There is none. Click “Create a new account?” on the login page: the first account created becomes the administrator. Then set USERS_ALLOW_REGISTRATION=false to close sign-ups; the administrator invites the other users from Settings, Users, with a one-time link.

Why can Ryot not find movies or shows?

Since v9, movies and shows need your own TMDB token: create a free TMDB account, request an API key, and set its API Read Access Token in MOVIES_AND_SHOWS_TMDB_ACCESS_TOKEN. Video games need a Twitch application, while books work without any key.

How much memory does Ryot need?

Little. On our test VPS, a fresh installation used about 240 to 300 MB for Ryot and 70 MB for PostgreSQL, and the two images take about 810 MB of disk.

How do I back up Ryot?

Dump the PostgreSQL database with docker compose exec -T ryot-db pg_dump -U ryot -Fc ryot, and keep a copy of your .env file. Restore with pg_restore --clean --if-exists --no-owner, the application stopped.

How do I update Ryot?

Read the release notes and take a backup, change the image tag in compose.yaml, then run docker compose pull and docker compose up -d. The database migrations run on their own at startup. Between major versions, follow the migration page.

Does a managed VPS cover Ryot?

A managed VPS covers the server: system, security, monitoring and backups. Our teams also proactively monitor your instance and recommend useful fixes, which you apply. Work inside the application is billed by the hour or at a fixed rate.

Contact us