# Deploying Finalarr > **Keep Finalarr inside your home network.** Do not forward port 5790 to the internet. > For access from outside use a VPN, or a reverse proxy with HTTPS (see *Remote access* > below). With `FINALARR_AUTH=local`, anyone on your network can use Finalarr without > logging in. ## Requirements - Docker, amd64 or arm64 (release candidates are amd64 only). Image: `ghcr.io/abrechen2/finalarr` (`latest`, a version such as `0.3.0`, or `rc-latest`). - Sonarr v4 reachable from the container. - Two secrets in the environment (Finalarr refuses to start without them): - `FINALARR_API_KEY` — at least 20 characters, e.g. `openssl rand -hex 32`. It is also the UI login. - `FINALARR_SECRET_KEY` — a Fernet key: `openssl rand -base64 32 | tr '+/' '-_'`. It encrypts stored Sonarr keys and channel URLs; changing it makes them unreadable. Optional: `FINALARR_AUTH=local` (no login from home networks, like Sonarr's "disabled for local addresses"; behind a reverse proxy also set `FINALARR_TRUSTED_PROXIES`, or every request looks local), `FINALARR_PUBLIC_URL` (adds "Finalarr" links to messages), `FINALARR_TRUSTED_PROXIES` (number of reverse proxies in front), `FINALARR_WEBHOOK_ALLOW` (IPs/CIDRs allowed to call the webhook), `PUID`/`PGID`, `TZ`. See `.env.example`. ## Docker Compose The README has a ready-to-use compose file with the published image. To build from a checkout instead: ```sh cp .env.example .env # fill in the two keys docker compose up -d --build ``` Data lives in `/config` (SQLite database, log, scheduler lock). ## Updates and backups Pull the new image and recreate the container (`docker compose pull && docker compose up -d`); database migrations run on start and are not reversible, so take a backup first. Backup while Finalarr runs (a plain `cp` of `finalarr.db` can catch it mid-write): ```sh docker exec finalarr python -m finalarr.backup # → /config/backups/finalarr-