3 Commits

Include renames

Author	SHA1	Message	Date
Latte	288c696f28	fix(ci): give the smoke-test container a per-commit name ... The Docker smoke-test ran the server container under the fixed name familiar-smoke. On the self-hosted runner the job shares the host Docker daemon, so a container left behind by a killed or re-run job (or a concurrent dev push + PR) collides on that name and 'docker run' fails with exit 125. Derive the name from the commit SHA, remove any stale container of that name before starting, and thread the name through the smoke-test and cleanup steps.	2026-07-05 13:55:29 +02:00
Latte	945e40b5d8	fix(ci): smoke-test the image from inside its own container via docker exec ... The smoke test probed the server over the network, which fails on the self-hosted runner: the job step runs in a container that shares the host Docker socket but sits on a different network, so it can reach neither a published host port (-p lands on the runner host) nor the server container's bridge IP (different network → curl connect hangs, so the job looked stuck rather than failing). Probe from inside the server container with `docker exec` instead: it goes through the Docker socket and runs in the server's own netns, where 127.0.0.1:8080 always works regardless of runner topology. The image ships python + httpx, so no curl or extra image pull is needed. Drop the now unnecessary -p publish.	2026-07-05 13:42:40 +02:00
Latte	eb2922f63c	ci(docker): build, smoke-test, and publish the remote-HTTP image ... New .gitea/workflows/docker.yml (alongside the untouched ci.yml wheel publish). Runs lint + test, then builds the image and smoke-tests it — non-root uid, /healthz 200, MCP 401 without a token and 200 with a valid bearer. On a merge to main/dev it pushes to git.hiddenden.cafe/hiddenden/familiar (main -> :latest + :main, dev -> :dev, plus :sha-<12>) via the existing REGISTRY_TOKEN, then does a scoped cleanup. The two workflows are independent and don't interfere.	2026-07-04 19:26:17 +02:00