Files
Bulwark/.env.local.example
Christopher Fahlin ea814c5125 build: add release image, compose backing services, and env scaffolding
- Multi-stage Dockerfile (mix release, embedded ERTS, runs as nobody) with
  migrate/server release overlays for an initContainer migration flow
- docker-compose: standalone-friendly upstream images (postgres:17,
  valkey/valkey:8) for the local dev loop. The cluster's operator images
  (cloudnative-pg, hyperspike) don't run standalone — DSN-from-env already
  gives local<->cluster parity, so image identity is local-only
- .env(.local).example templates + .envrc (direnv) loader
- .dockerignore; .gitignore fixups for release artifacts and env files
2026-05-30 19:07:21 -07:00

20 lines
757 B
Bash

# Local development env — copy to .env.local (gitignored).
#
# Points the app at the throwaway Postgres + Valkey from docker-compose.yml.
# The DSN is the ONLY thing that differs from prod; read it from the env so the
# local -> cluster move is a deploy, not a rewrite.
# --- docker-compose backing services ---
POSTGRES_USER=postgres
POSTGRES_PASSWORD=postgres
POSTGRES_DB=bulwark_dev
# --- app connection strings ---
# Postgres: local container.
DATABASE_URL=ecto://postgres:postgres@localhost:5432/bulwark_dev
# Valkey: local container, NO password (cluster requires one — see auth-parity
# note in the developer guide). Always pass the full DSN via env so the
# credentialed prod form flows through unchanged.
VALKEY_URL=redis://localhost:6379/0