Configuration

Environment Variables

All configuration is via environment variables. Copy .env.example to .env and customize.

Variable	Default	Description
TRAPFALL_DATABASE_URL	sqlite:trapfall.db	Database URL (sqlite:path.db or postgres://...)
TRAPFALL_LISTEN	0.0.0.0:9090	HTTP listen address
TRAPFALL_SECURE_COOKIE	true	Set false for HTTP local dev
TRAPFALL_CORS_ORIGINS	(empty = allow all)	Comma-separated origins
RUST_LOG	info	Log level: trace, debug, info, warn, error

Database URL

TrapFall supports selecting a database backend via URL scheme:

# SQLite (default) — bare paths auto-prefixed with sqlite:
TRAPFALL_DATABASE_URL=trapfall.db               # → sqlite:trapfall.db
TRAPFALL_DATABASE_URL=sqlite:/data/trapfall.db   # explicit

# Postgres (built-in, no extra build flags needed)
TRAPFALL_DATABASE_URL=postgres://user:pass@host:5432/trapfall

The --db CLI flag takes precedence over the env var:

trapfall --db /custom/path.db serve
trapfall --db sqlite:/data/trapfall.db serve

Local Development

For local HTTP development, you must set:

TRAPFALL_SECURE_COOKIE=false

Otherwise browsers will reject the session cookie over HTTP.

Production

For production with HTTPS:

TRAPFALL_SECURE_COOKIE=true
TRAPFALL_CORS_ORIGINS=https://trapfall.yourcompany.com
RUST_LOG=trapfall=info

Docker Compose

The included docker-compose.yml is pre-configured:

services:
  trapfall:
    image: ghcr.io/codecoradev/trapfall:0.0.5
    ports:
      - "3000:3000"
    volumes:
      - trapfall-data:/data
    environment:
      - RUST_LOG=trapfall=debug
      - TRAPFALL_SECURE_COOKIE=false
      - TRAPFALL_DATABASE_URL=sqlite:/data/trapfall.db
    command: serve --listen 0.0.0.0:3000

Database

TrapFall uses SQLite in WAL mode with synchronous=NORMAL. The database is a single file — back it up by copying the file.

No migration commands needed — the schema is auto-created on first run.