Installation

Profilarr is a self-hosted web app that runs continuously, like Radarr and Sonarr. It keeps everything in one folder: its SQLite database, logs, backups, and the databases you link. Testing custom formats and quality profiles requires the Profilarr parser, a small companion service that runs as its own container.

Requirements

• A Docker host running Linux kernel 3.17 or newer, on linux/amd64 or linux/arm64.
• Sonarr v4.0.9.2386 or newer.
• Radarr v5.10.4 or newer.

Installation Methods

Profilarr is currently distributed as a Docker image. Standalone binaries for Windows, macOS, and Linux are a work in progress.

The Parser

The parser is a small companion service that reads release titles the way Radarr and Sonarr do. It’s written in C#, like Radarr and Sonarr, so it uses the same parsing logic and the same .NET regex engine they do. That means test results match what your Arrs will actually decide.

Profilarr uses it for:

• Custom format testing
• Quality profile testing, including Quick Parse
• Checking that a regular expression is valid
• Running Regex101 unit tests

The parser was built mostly for the development side of Profilarr: building and testing configurations. If you’re only linking a database and syncing it to your Arrs, without changing its configs, you can skip the parser entirely and lose nothing you’d use (and save about 50 MB of RAM). Without it, Profilarr hides custom format and quality profile testing, and regex checks and Regex101 tests show no results.

Release Channels

Profilarr is published under a few tags, so you can choose how it updates. New features land on develop first for beta testers, and a batch becomes a stable release once it’s verified. How you keep Profilarr up to date depends on how you installed it. For Docker, see Updating.

Use latest unless you specifically want to test upcoming changes. The parser publishes the same tags. Keep both containers on the same one.

Environment Variables

Profilarr is configured with environment variables. Most are read by Profilarr itself and work the same way with any installation method. The ones marked Docker only are handled by the container’s startup script, so they won’t apply to the standalone binaries.

General

Authentication

Set all three OIDC_ variables to turn on SSO.

Parser

See The Parser for what it does and whether you need it.

Outbound Proxy

Profilarr has no proxy setting of its own. It follows these standard variables for everything it fetches: database updates from GitHub, notifications, TMDB, and announcements.

• Proxy URLs take the form scheme://user:pass@host:port, where the scheme is http, socks5, or socks5h. Use socks5h to send DNS lookups through the proxy too.
• Special characters in the username or password need to be URL-encoded, such as @ as %40 and : as %3A.

For example, this routes Profilarr through a proxy container named gluetun, while your Arrs and the parser stay direct:

environment:
  - HTTPS_PROXY=http://user:pass@gluetun:8888
  - NO_PROXY=localhost,127.0.0.1,parser,radarr,sonarr

Announcements

Secrets from Files

Docker only. Any variable can be read from a file instead by adding _FILE to its name and setting it to the file’s path. This works with Docker secrets, so values like the OIDC client secret don’t have to sit in your compose file:

environment:
  - OIDC_CLIENT_SECRET_FILE=/run/secrets/oidc_client_secret

The startup script reads the file, strips any newlines, and sets the variable without _FILE from it. If the file doesn’t exist, it logs a warning and leaves the variable unset.