Where Does Self-Hosted Redlib Store Config?
Redlib config file, systemd and Docker env locations for self-hosted Linux setups.
Last updated
Redlib keeps no database and no data directory. One TOML file plus environment variables control the whole instance. That makes backup trivial but surprises people hunting for a data folder.
The primary file is redlib.toml in the working directory with libreddit.toml as fallback. Systemd installs add an env file at /etc/redlib.conf. Docker setups pass a separate .env file instead.
Where Redlib stores this, by platform
./redlib.toml
Primary config in the working dir with libreddit.toml fallback. Stateless server with no data dir. Systemd uses /etc/redlib.conf env file, Docker uses its own .env. Binary installs to /usr/bin/redlib.
Frequently asked questions
Where is the Redlib database?
There is none. Redlib is stateless and proxies upstream. Back up redlib.toml and the env file instead. Logs go nowhere in production unless the process manager captures them.
Which wins, env vars or the config file?
Environment wins in order: REDLIB prefixed vars, then legacy LIBREDDIT vars, then the TOML file. Keep secrets in the env file and shared defaults in TOML to avoid duplication.
Notice an outdated path? Let us know.