Provision PostgreSQL for dev and test and configure the database URL #2

New issue

Open

opened 2026-09-26 13:58:28 +00:00 by belvedere · 0 comments

belvedere commented

2026-09-26 13:58:28 +00:00

Collaborator

Objective: A reachable Postgres instance for dev and test environments.

config/dev.exs and config/test.exs will need credentials; AshPostgres and Ecto both use the
same repo config.

Files:

Create: docker-compose.yml (or document a native install)
Modify: config/dev.exs, config/test.exs (read from DATABASE_URL where sensible)

Steps:

Add a docker-compose.yml running postgres:17 with a named volume and a healthcheck, or
document the native-install route.
Point config/dev.exs and config/test.exs at it.
Verify connectivity: mix ecto.create succeeds.

Verify:

docker compose up -d
mix ecto.create && mix ecto.migrate   # both succeed

Notes: test must use a distinct database (e.g. first_thousand_words_test) so the
mix test alias cannot truncate dev data.

**Objective:** A reachable Postgres instance for `dev` and `test` environments. `config/dev.exs` and `config/test.exs` will need credentials; AshPostgres and Ecto both use the same repo config. **Files:** - Create: `docker-compose.yml` (or document a native install) - Modify: `config/dev.exs`, `config/test.exs` (read from `DATABASE_URL` where sensible) **Steps:** 1. Add a `docker-compose.yml` running `postgres:17` with a named volume and a healthcheck, or document the native-install route. 2. Point `config/dev.exs` and `config/test.exs` at it. 3. Verify connectivity: `mix ecto.create` succeeds. **Verify:** ```bash docker compose up -d mix ecto.create && mix ecto.migrate # both succeed ``` **Notes:** `test` must use a distinct database (e.g. `first_thousand_words_test`) so the `mix test` alias cannot truncate dev data.

belvedere added this to the M0 — Toolchain & scaffold verification milestone

2026-09-26 13:58:28 +00:00

belvedere added the

labels

2026-09-26 13:58:28 +00:00

belvedere referenced this issue