spotiarr-docker

To configure a docker-compose deployment for SpotiArr with persistent storage, you bind a Docker volume to the `/spotiarr/config` directory. This ensures your SQLite database and app data persist across container restarts.

Redis health-based service startup ordering ensures the Spotiarr container waits for a healthy Redis status before launching. This guarantees the Redis-backed job queue is ready to accept tasks for reliable media automation.

Yes, you must use an absolute path for the mandatory `DOWNLOADS_DIR` environment variable when self-hosting Spotify downloaders. This ensures Docker correctly maps the host directory for managing downloaded media files.

Yes, you can use Traefik as a reverse proxy for a self-hosted SpotiArr Docker setup. The deployment blueprint includes optional Traefik configuration for production routing and external connectivity.

Spotiarr local access and OAuth require mandatory Spotify client credential environment variables. You must validate these settings to ensure the application can authenticate and connect to Spotify's API.

You should gitignore the `./config/` directory and `docker-compose.override.yml` to implement safe operational guardrails. This prevents committing sensitive local configuration data and OAuth credentials to version control.