Church Garden

Church management: rota, attendance, service order, worship songs, sermon files. Rust (axum) + Postgres + Datastar. No ORM. Docker is the only tool you need installed.

Develop

docker compose up            # Postgres + app with live reload on http://localhost:3000
# emails the app sends (sign-up verification, password resets) show up in Mailpit: http://localhost:8025
# port 3000 busy? CHURCHGARDEN_PORT=8080 docker compose up

docker compose run --rm test                       # all unit + route tests (each test gets its own throwaway database)
docker compose run --rm tools cargo clippy --all-targets -- -D warnings
docker compose run --rm tools cargo fmt
docker compose run --rm tools cargo add <crate>    # any other cargo command
docker compose down -v                             # stop and wipe the database

First run builds the toolchain image (a few minutes); later runs reuse it.

Open http://localhost:3000 and create an account. Rota page: /services/<id>/rota. Migrations in migrations/ run on startup.

Layout

• src/lib.rs routes + SQL, src/rota.rs assignment algorithm, src/geo.rs geofence
• tests/api.rs route tests; unit tests sit beside the code
• docs/PLAN.md roadmap and decisions

CI

scripts/ci.sh is the whole check (format, clippy, tests, all through docker compose); run it locally before pushing. .gitea/workflows/ci.yml runs it on every push and pull request using Gitea Actions. That needs Actions enabled on the Gitea server and a runner (act_runner) whose host has Docker with the compose plugin and mounts the Docker socket into jobs. The workflow uses no third-party actions, so nothing is pulled from GitHub.