chore: consolidate platform split checks

dev/postgres/.env.example

@@ -0,0 +1,5 @@
+GOVOPLAN_POSTGRES_DB=govoplan
+GOVOPLAN_POSTGRES_USER=govoplan
+GOVOPLAN_POSTGRES_PASSWORD=govoplan-dev
+GOVOPLAN_POSTGRES_PORT=55432
+GOVOPLAN_POSTGRES_DATABASE_URL=postgresql+psycopg://govoplan:govoplan-dev@127.0.0.1:55432/govoplan

dev/postgres/README.md

@@ -0,0 +1,126 @@
+# PostgreSQL Development Profile
+
+GovOPlaN development now defaults to PostgreSQL:
+
+```text
+postgresql+psycopg://govoplan_dev@127.0.0.1:5432/govoplan_dev
+```
+
+The matching pg-tools URL for `psql`, `pg_dump`, and `pg_restore` is:
+
+```text
+postgresql://govoplan_dev@127.0.0.1:5432/govoplan_dev
+```
+
+Store the password in `~/.pgpass` instead of committing it to a `.env` file.
+The devserver and `scripts/launch-dev.sh` honor an explicit `DATABASE_URL` if
+you need a different database.
+
+## Host PostgreSQL Setup
+
+Create the default local role and database from a host shell:
+
+```bash
+export GOVOPLAN_PG_DB=govoplan_dev
+export GOVOPLAN_PG_USER=govoplan_dev
+read -rsp "Password for ${GOVOPLAN_PG_USER}: " GOVOPLAN_PG_PASSWORD
+echo
+
+if ! sudo -u postgres psql -tAc "SELECT 1 FROM pg_roles WHERE rolname='${GOVOPLAN_PG_USER}'" | grep -q 1; then
+  sudo -u postgres createuser --pwprompt "${GOVOPLAN_PG_USER}"
+else
+  sudo -u postgres psql -c "\\password ${GOVOPLAN_PG_USER}"
+fi
+
+if ! sudo -u postgres psql -tAc "SELECT 1 FROM pg_database WHERE datname='${GOVOPLAN_PG_DB}'" | grep -q 1; then
+  sudo -u postgres createdb -O "${GOVOPLAN_PG_USER}" "${GOVOPLAN_PG_DB}"
+fi
+
+sudo -u postgres psql -d "${GOVOPLAN_PG_DB}" -c "ALTER SCHEMA public OWNER TO ${GOVOPLAN_PG_USER};"
+
+touch ~/.pgpass
+chmod 600 ~/.pgpass
+grep -v "^127.0.0.1:5432:${GOVOPLAN_PG_DB}:${GOVOPLAN_PG_USER}:" ~/.pgpass > ~/.pgpass.tmp || true
+printf '127.0.0.1:5432:%s:%s:%s\n' "$GOVOPLAN_PG_DB" "$GOVOPLAN_PG_USER" "$GOVOPLAN_PG_PASSWORD" >> ~/.pgpass.tmp
+mv ~/.pgpass.tmp ~/.pgpass
+chmod 600 ~/.pgpass
+```
+
+Check access:
+
+```bash
+psql "postgresql://${GOVOPLAN_PG_USER}@127.0.0.1:5432/${GOVOPLAN_PG_DB}" \
+  -c 'select current_user, current_database();'
+```
+
+When running through the VS Codium Flatpak sandbox, host PostgreSQL tools are
+available through:
+
+```bash
+flatpak-spawn --host /usr/bin/psql --version
+flatpak-spawn --host /usr/bin/pg_dump --version
+flatpak-spawn --host /usr/bin/pg_restore --version
+```
+
+## Run GovOPlaN Against Host PostgreSQL
+
+```bash
+cd /mnt/DATA/git/govoplan-core
+./.venv/bin/python -m govoplan_core.commands.init_db \
+  --database-url postgresql+psycopg://govoplan_dev@127.0.0.1:5432/govoplan_dev \
+  --with-dev-data
+
+./.venv/bin/python -m govoplan_core.devserver --smoke --no-reload
+```
+
+For the full backend and WebUI launcher:
+
+```bash
+cd /mnt/DATA/git/govoplan-core
+scripts/launch-dev.sh
+```
+
+To force the old SQLite fallback for a disposable local run:
+
+```bash
+GOVOPLAN_DEV_DATABASE_BACKEND=sqlite scripts/launch-dev.sh
+```
+
+## Disposable Docker Testbed
+
+This testbed is for migration and module-permutation checks. It is not a
+production deployment profile.
+
+```bash
+cd /mnt/DATA/git/govoplan-core/dev/postgres
+cp .env.example .env
+docker compose --env-file .env up -d
+```
+
+Run the integration check from the core checkout:
+
+```bash
+cd /mnt/DATA/git/govoplan-core
+set -a
+. dev/postgres/.env
+set +a
+./.venv/bin/python scripts/postgres-integration-check.py \
+  --database-url "$GOVOPLAN_POSTGRES_DATABASE_URL" \
+  --reset-schema
+```
+
+`--reset-schema` drops and recreates the `public` schema before every module
+set. Use it only against this disposable database.
+
+Stop the testbed:
+
+```bash
+cd /mnt/DATA/git/govoplan-core/dev/postgres
+docker compose --env-file .env down
+```
+
+Remove all test data:
+
+```bash
+docker compose --env-file .env down -v
+```

dev/postgres/docker-compose.yml

@@ -0,0 +1,22 @@
+services:
+  postgres:
+    image: postgres:16-alpine
+    container_name: govoplan-core-postgres-dev
+    environment:
+      POSTGRES_DB: ${GOVOPLAN_POSTGRES_DB:-govoplan}
+      POSTGRES_USER: ${GOVOPLAN_POSTGRES_USER:-govoplan}
+      POSTGRES_PASSWORD: ${GOVOPLAN_POSTGRES_PASSWORD:-govoplan-dev}
+    ports:
+      - "127.0.0.1:${GOVOPLAN_POSTGRES_PORT:-55432}:5432"
+    healthcheck:
+      test:
+        - CMD-SHELL
+        - pg_isready -U "$${POSTGRES_USER}" -d "$${POSTGRES_DB}"
+      interval: 5s
+      timeout: 3s
+      retries: 20
+    volumes:
+      - postgres-data:/var/lib/postgresql/data
+
+volumes:
+  postgres-data:

dev/production-like/.env.example

@@ -0,0 +1,9 @@
+GOVOPLAN_PRODUCTION_LIKE_POSTGRES_DB=govoplan
+GOVOPLAN_PRODUCTION_LIKE_POSTGRES_USER=govoplan
+GOVOPLAN_PRODUCTION_LIKE_POSTGRES_PASSWORD=govoplan-dev
+GOVOPLAN_PRODUCTION_LIKE_POSTGRES_PORT=55433
+GOVOPLAN_PRODUCTION_LIKE_REDIS_PORT=56379
+
+GOVOPLAN_PRODUCTION_LIKE_DATABASE_URL=postgresql+psycopg://govoplan:govoplan-dev@127.0.0.1:55433/govoplan
+GOVOPLAN_PRODUCTION_LIKE_DATABASE_URL_PGTOOLS=postgresql://govoplan:govoplan-dev@127.0.0.1:55433/govoplan
+GOVOPLAN_PRODUCTION_LIKE_REDIS_URL=redis://127.0.0.1:56379/0

dev/production-like/README.md

@@ -0,0 +1,49 @@
+# Production-Like Development Profile
+
+This profile runs the shared services that production depends on while keeping
+API, worker, and WebUI code in the editable local repositories.
+
+It provides:
+
+- PostgreSQL with a persistent Docker volume
+- Redis with append-only persistence
+- explicit `ENABLED_MODULES`
+- local durable file storage under `runtime/production-like/files`
+- a Celery worker process using the same queues as the API
+
+Start it from the core repository:
+
+```bash
+cd /mnt/DATA/git/govoplan-core
+scripts/launch-production-like-dev.sh
+```
+
+The launcher uses `dev/production-like/.env` when present, otherwise
+`dev/production-like/.env.example`. Copy the example when you want local port or
+password changes:
+
+```bash
+cp dev/production-like/.env.example dev/production-like/.env
+```
+
+The API and worker use:
+
+```text
+DATABASE_URL=postgresql+psycopg://govoplan:govoplan-dev@127.0.0.1:55433/govoplan
+REDIS_URL=redis://127.0.0.1:56379/0
+CELERY_ENABLED=true
+```
+
+Stop the launched API/WebUI/worker with `Ctrl+C`. The PostgreSQL and Redis
+containers keep running by default so the next launch is fast. To stop them too:
+
+```bash
+GOVOPLAN_STOP_PROFILE_DEPENDENCIES_ON_EXIT=1 scripts/launch-production-like-dev.sh
+```
+
+To remove all profile data:
+
+```bash
+cd /mnt/DATA/git/govoplan-core/dev/production-like
+docker compose --env-file .env.example down -v
+```

dev/production-like/docker-compose.yml

@@ -0,0 +1,37 @@
+services:
+  postgres:
+    image: postgres:16-alpine
+    container_name: govoplan-production-like-postgres
+    environment:
+      POSTGRES_DB: ${GOVOPLAN_PRODUCTION_LIKE_POSTGRES_DB:-govoplan}
+      POSTGRES_USER: ${GOVOPLAN_PRODUCTION_LIKE_POSTGRES_USER:-govoplan}
+      POSTGRES_PASSWORD: ${GOVOPLAN_PRODUCTION_LIKE_POSTGRES_PASSWORD:-govoplan-dev}
+    ports:
+      - "127.0.0.1:${GOVOPLAN_PRODUCTION_LIKE_POSTGRES_PORT:-55433}:5432"
+    healthcheck:
+      test:
+        - CMD-SHELL
+        - pg_isready -U "$${POSTGRES_USER}" -d "$${POSTGRES_DB}"
+      interval: 5s
+      timeout: 3s
+      retries: 20
+    volumes:
+      - postgres-data:/var/lib/postgresql/data
+
+  redis:
+    image: redis:7-alpine
+    container_name: govoplan-production-like-redis
+    command: ["redis-server", "--appendonly", "yes"]
+    ports:
+      - "127.0.0.1:${GOVOPLAN_PRODUCTION_LIKE_REDIS_PORT:-56379}:6379"
+    healthcheck:
+      test: ["CMD", "redis-cli", "ping"]
+      interval: 5s
+      timeout: 3s
+      retries: 20
+    volumes:
+      - redis-data:/data
+
+volumes:
+  postgres-data:
+  redis-data: