lizardbyte/themerr repository overview

⁠Docker

⁠lizardbyte/themerr

Before connecting a media server, create a persistent key file outside the /config volume. Keep this file private and ensure the container's PUID can read it. Keep the same key when recreating the container; losing it requires signing in again.

THEMERR_TOKEN_KEY_FILE encrypts credentials for all media servers. The older THEMERR_PLEX_TOKEN_KEY_FILE name is still accepted; use the same key when renaming it. The generic variable takes precedence if both are set. Port 9495 serves only the Jellyfin connector repository over HTTP when the admin UI uses a self-signed certificate. Use a host address reachable from Jellyfin; localhost inside another container refers to that container itself.

python3 -c 'import base64, os; print(base64.urlsafe_b64encode(os.urandom(32)).decode())' > themerr-tokens.key
chmod 600 themerr-tokens.key

⁠Using docker run

Create and run the container (substitute your <values>):

docker run -d \
  --name=themerr \
  --restart=unless-stopped \
  -v <path to data>:/config \
  -v <absolute path to themerr-tokens.key>:/run/secrets/themerr_token_key:ro \
  -e THEMERR_TOKEN_KEY_FILE=/run/secrets/themerr_token_key \
  -e PUID=<uid> \
  -e PGID=<gid> \
  -e TZ=<timezone> \
  -p 9494:9494 \
  -p 9495:9495 \
  lizardbyte/themerr

To update the container it must be removed and recreated:

# Stop the container
docker stop themerr
# Remove the container
docker rm themerr
# Pull the latest update
docker pull lizardbyte/themerr
# Run the container with the same parameters as before
docker run -d ...

⁠Using docker-compose

Create a docker-compose.yml file with the following contents (substitute your <values>):

version: '3'
services:
  themerr:
    image: lizardbyte/themerr
    container_name: themerr
    restart: unless-stopped
    volumes:
      - <path to data>:/config
      - <absolute path to themerr-tokens.key>:/run/secrets/themerr_token_key:ro
    environment:
      - THEMERR_TOKEN_KEY_FILE=/run/secrets/themerr_token_key
      - PUID=<uid>
      - PGID=<gid>
      - TZ=<timezone>
    ports:
      - 9494:9494
      - 9495:9495

Create and start the container (run the command from the same folder as your docker-compose.yml file):

docker-compose up -d

To update the container:

# Pull the latest update
docker-compose pull
# Update and restart the container
docker-compose up -d

⁠Parameters

You must substitute the <values> with your own settings.

Parameters are split into two halves separated by a colon. The left side represents the host and the right side the container.

Example: -p external:internal - This shows the port mapping from internal to external of the container. Therefore -p 9494:9494 exposes port 9494 from inside the container on the host's port 9494. The internal port is 9494; the host port may be changed (e.g. -p 8080:9494).

⁠User / Group Identifiers:

When using data volumes (-v flags) permissions issues can arise between the host OS and the container. To avoid this issue you can specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify.

In this instance PUID=1001 and PGID=1001. To find yours use id user as below:

$ id dockeruser
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)