Configuration Reference¶

PROTEA loads its configuration from two sources, merged in this order (later entries win):

YAML structure¶

database:
  url: postgresql+psycopg://user:pass@host:5432/dbname

queue:
  amqp_url: amqp://guest:guest@localhost:5672/

Both keys are required. The file is loaded by protea.infrastructure.settings.load_settings(project_root) at startup.

Variable	Description
`PROTEA_DB_URL`	Overrides `database.url`. Must be a valid SQLAlchemy connection string using the `postgresql+psycopg` driver.
`PROTEA_AMQP_URL`	Overrides `queue.amqp_url`. Standard AMQP URL format.

# apps/web/.env.local
NEXT_PUBLIC_API_URL=http://127.0.0.1:8000

This is the only configuration the Next.js frontend needs. It is injected at build time by Next.js and embedded in the client bundle.

The Docker-based integration test fixture is controlled by:

Variable	Default	Description
`PROTEA_PG_IMAGE`	`pgvector/pgvector:pg16`	Docker image for the ephemeral Postgres container.
`PROTEA_PG_USER`	`protea`	Database user.
`PROTEA_PG_PASSWORD`	`protea`	Database password.
`PROTEA_PG_DB`	`protea_test`	Database name.
`PROTEA_PG_PORT`	`15432`	Host port mapped to container port 5432.
`PROTEA_PG_TIMEOUT`	`30`	Seconds to wait for Postgres readiness.

The RabbitMQ management UI is available at http://localhost:15672 (default credentials guest / guest). The two PROTEA queues are:

Queue	Durability	Operations
`protea.ping`	durable	`ping`
`protea.jobs`	durable	`insert_proteins`, `fetch_uniprot_metadata`

Queues are declared at worker startup and survive broker restarts.