[FEATURE] ENV variables

[cook1emr]

Feature Summary

It would be great if Radarr URL and Radarr API Key could be set as environment variables, this would allow for rotation via secrets managers etc.

[iongpt]

@cook1emr Good news — Boxarr already supports environment variables for Radarr configuration, so you don’t need a new feature to do this.

What’s supported today

• RADARR_URL: sets the Radarr base URL (e.g., http://radarr:7878).
• RADARR_API_KEY: sets the Radarr API key.
• BOXARR_URL_BASE: sets a URL base when running behind a reverse proxy (e.g., /boxarr).
• BOXARR_DATA_DIRECTORY: sets the config/data directory (defaults to ./config).

Ways to set them

• Docker Compose:
  services:
  boxarr:
  image: ghcr.io/iongpt/boxarr:latest
  ports:
  • 8888:8888
    volumes:
  • ./config:/config
    environment:
  • RADARR_URL=http://radarr:7878
  • RADARR_API_KEY=${RADARR_API_KEY} # pull from your compose env or secrets manager
  • BOXARR_URL_BASE=boxarr # optional
• Docker run:
  docker run -d
  -p 8888:8888
  -v $(pwd)/config:/config
  -e RADARR_URL=http://radarr:7878
  -e RADARR_API_KEY=your_key
  ghcr.io/iongpt/boxarr:latest
• Local .env file (auto‑loaded):
  RADARR_URL=http://radarr:7878
  RADARR_API_KEY=your_key
• Direct YAML (local.yaml):
  radarr:
  url: http://radarr:7878
  api_key: your_key

Notes on precedence and rotation

• Precedence: values in config/local.yaml override environment variables. If you want the env var to be the source of truth (e.g., for secret rotation),
  leave these fields blank or removed in local.yaml.
• Setup UI: it will prefill from the current settings (including env vars). If you save from the UI, it will persist URL and API key into local.yaml. If
  you prefer env‑only, avoid saving those fields or remove them again from local.yaml after saving other options.
• Secrets managers: use your orchestrator to inject RADARR_API_KEY (and RADARR_URL if desired) at container start. As long as local.yaml doesn’t override
  them, updates take effect on restart.

Given the above, I believe this request is already covered by existing options so I am closing this. Please re-open if you think something is missing.

[stavros-k]

@iongpt On a fresh install I've tried setting BOXARR_PORT to 1234, But I still see in the logs

2025-10-06 13:11:01,227 - __main__ - INFO - Starting Boxarr application
2025-10-06 13:11:01,234 - __main__ - INFO - No configuration found - starting in setup mode
2025-10-06 13:11:01,234 - __main__ - INFO - Please visit http://localhost:8888 to configure Boxarr
2025-10-06 13:11:01,234 - __main__ - INFO - Boxarr startup complete
INFO:     Started server process [1]
INFO:     Waiting for application startup.
2025-10-06 13:11:01,298 - src.api.app - INFO - Boxarr API starting up...
2025-10-06 13:11:01,298 - apscheduler.scheduler - INFO - Adding job tentatively -- it will be properly scheduled when the scheduler starts
2025-10-06 13:11:01,300 - apscheduler.scheduler - INFO - Added job "Box Office Update" to job store "default"
2025-10-06 13:11:01,301 - apscheduler.scheduler - INFO - Scheduler started
2025-10-06 13:11:01,301 - src.core.scheduler - INFO - Scheduler started successfully with cron: 0 23 * * 2
2025-10-06 13:11:01,301 - src.core.scheduler - INFO - Timezone: America/New_York
2025-10-06 13:11:01,302 - src.core.scheduler - INFO - Next scheduled run: 2025-10-08 23:00:00+00:00
2025-10-06 13:11:01,302 - src.core.scheduler - INFO - Time until next run: 57.8 hours
2025-10-06 13:11:01,302 - src.api.app - INFO - Scheduler started
INFO:     Application startup complete.
INFO:     Uvicorn running on http://0.0.0.0:8888 (Press CTRL+C to quit)

Also can you clarify if envs override the yaml file values?