Configuration

lyrid is configured entirely through the environment. There is no configuration file, and secrets never live in one.

Variable	Required	Default	Purpose
DATABASE_URL	yes	—	PostgreSQL connection string, e.g. postgres://lyrid:lyrid@localhost:5432/lyrid
LYRID_ADDR	no	0.0.0.0:8080	Socket address the HTTP server binds to
RUST_LOG	no	lyrid=info,tower_http=info	Log filter, in tracing-subscriber EnvFilter syntax

How it is read

The server reads the environment once at startup and fails immediately if it cannot build a valid configuration:

• DATABASE_URL missing — startup aborts with a message naming the variable and showing the expected shape.
• LYRID_ADDR malformed — startup aborts naming the variable and echoing the value it could not parse.

Failing at startup is deliberate. A server that boots with a broken configuration and only discovers it on the first request has turned a deployment error into an outage.

Note that a database that is unreachable is a different case from one that is not configured: the first is reported by /health as degraded while the server keeps running, the second stops it from starting at all.

Local development

Copy .env.example to .env and edit it. .env is in .gitignore and must stay there — credentials, tokens, and connection strings never enter the repository, the docs, the tests, or an example.

cp .env.example .env