4 Commits

Include renames

Author	SHA1	Message	Date
patrick	412a73cedf	fix: tell the tests where the database actually is ... DOCKER_HOST only decides which daemon creates the container; the address the test dials comes from POSTGRES_HOST, which defaults to the job container's own loopback. Setting one without the other still times out.	2026-08-18 00:49:41 -04:00
patrick	5176dfcb77	fix: give the backend CI job a docker daemon it can address ... The runner has docker, so the database container started; the job just could not reach it. pytest-databases takes the address from DOCKER_HOST, and unset means 127.0.0.1 -- the job container's loopback, not the namespace the sibling published on. A dind service makes it resolve to a host that answers.	2026-08-18 00:45:43 -04:00
patrick	54043a97d2	feat: check formatting, linting and tests in CI ... Every push runs ruff, prettier, pytest and svelte-check; a tagged release runs the blocking half again before it publishes an image. eslint and svelte-check report without failing, since 87 and 30 findings predate the workflow.	2026-08-17 15:17:20 -04:00
patrick	b70ed5cb51	feat: build and publish release images from version tags ... Tagging v* builds both images on Gitea Actions and pushes them to the instance registry, then smoke-tests the published stack. The frontend read its backend URL through import.meta.env, which Vite resolves at build time, so an image could only point at whatever the build host had; it now reads it at runtime.	2026-08-17 15:05:18 -04:00