Configuration

Everything is set through environment variables, normally in the .env file next to compose.yml. There is no configuration file and no admin UI.

Variables

Variable	Required	Description
POSTGRES_USER / POSTGRES_PASSWORD / POSTGRES_DB	yes	Database credentials, shared by both containers
ConnectionStrings__ArgonFetchDatabase	yes	The app's connection string. Set in compose.yml from the values above
CORS_ALLOWED_ORIGINS	in production	Comma-separated origins allowed to call the API. Defaults to http://localhost:4200, and the app warns at startup if that default is still in use in production
ASPNETCORE_ENVIRONMENT	no	Production by default. Development also enables the Swagger UI
PROXY_LIST_PATH	no	File with one proxy per line, rotated across yt-dlp fetches so they do not all leave from the same IP. See below

A complete .env for a public deployment:

POSTGRES_USER=argonfetch
POSTGRES_PASSWORD=changeme123
POSTGRES_DB=argonfetch

ASPNETCORE_ENVIRONMENT=Production
CORS_ALLOWED_ORIGINS=https://argonfetch.example.com

CORS

CORS_ALLOWED_ORIGINS is the one variable you must not forget in production. It lists the origins the browser is allowed to call the API from - normally just the origin ArgonFetch itself is served on. Several are accepted, comma-separated:

CORS_ALLOWED_ORIGINS=https://app.argonfetch.dev,https://argonfetch.dev,http://localhost:4200

Leave it at the default and the app logs a warning at startup, because a production deployment that still only trusts http://localhost:4200 is almost certainly a mistake.

Proxy rotation

If the host's IP gets rate limited, point PROXY_LIST_PATH at a file listing one proxy per line. Each fetch takes the next proxy in the list, and a failed fetch is retried through the following one.

PROXY_LIST_PATH=/config/proxies.txt

    volumes:
      - ./proxies.txt:/config/proxies.txt:ro

Both http://user:pass@host:port and the host:port:user:pass export format used by providers such as Webshare are accepted; blank lines and # comments are ignored. Without the variable, fetches go out from the server's own IP as before.

Media tooling

yt-dlp and FFmpeg are fetched into /tools when the container starts rather than baked into the image, and yt-dlp updates itself every 12 hours. Two consequences worth knowing:

• Mount a volume at /tools. Otherwise roughly 100MB is downloaded again on every start.
• A restart fixes a broken yt-dlp. Extractor fixes land without rebuilding the image.

While the binaries are being fetched the app reports itself as under maintenance: the web UI shows a maintenance screen and fetch requests answer 503. GET /api/App reports the same state in its maintenance field.