sim/Justfile

default:
    @just --list

run:
    docker compose down --remove-orphans && docker compose up --build -d --remove-orphans

stop:
    docker compose down --remove-orphans

dev:
    SHARD_DATABASE_URL="sqlite://sim-shard-{shard}.db?mode=rwc" cargo run
feat: add database persistence and Docker setup 2026-10-08 06:44:30 +00:00			`default:`
			`@just --list`

			`run:`
feat(compose): run sqlite shards in separate containers Co-Authored-By: GitHub Copilot <noreply@github.com> 2026-10-13 15:18:15 +00:00			`docker compose down --remove-orphans && docker compose up --build -d --remove-orphans`
feat: add database persistence and Docker setup 2026-10-08 06:44:30 +00:00
build: update Just workflows for Compose and SQLite development 2026-10-08 07:24:14 +00:00			`stop:`
feat(compose): run sqlite shards in separate containers Co-Authored-By: GitHub Copilot <noreply@github.com> 2026-10-13 15:18:15 +00:00			`docker compose down --remove-orphans`
feat: add database persistence and Docker setup 2026-10-08 06:44:30 +00:00
build: update Just workflows for Compose and SQLite development 2026-10-08 07:24:14 +00:00			`dev:`
docs: document the shard cluster, economy and per-shard databases Describe the gateway and shard processes, transparent transfers, the economy and console peers in the README. Compose creates one Postgres database per shard and passes `SHARD_DATABASE_URL` and `SIM_SHARDS`; the Justfile and Dockerfile use per-shard SQLite files. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> 2026-10-12 18:43:11 +00:00			`SHARD_DATABASE_URL="sqlite://sim-shard-{shard}.db?mode=rwc" cargo run`