4 Commits

Include renames

Author	SHA1	Message	Date
stroblmeandClaude Opus 5	c33fa404a4	Keep the dev bind mounts out of CI, where they land nowhere ... compose.dev.yml mounts the source over the image's own copy so `--reload` means something in a detached local stack, and mounts the Playwright report out to the host. Under act_runner the daemon is a sibling of the job rather than its host: it resolves those paths against its own filesystem, finds nothing, and mounts empty directories. So the backend reported "Path does not exist fluksio/main.py" for a file the image plainly ships, and every shard uploaded nothing — "No files were found with the provided path: frontend/blob-report". compose.ci.yml now puts backend's volumes back to what compose.yml declares and drops Playwright's entirely; the shard copies its report out of the container before the teardown instead. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-24 21:42:04 +02:00
stroblmeandClaude Opus 5	961a8f881d	Keep the engine's state in SQLite, not Postgres ... One process owns this database — the image has run a single uvicorn worker for that reason since the four-engines bug — so a file beside the flows is the honest shape for it, and it is what lets `fluksio serve` need no infrastructure at all. Live values, node execution and the work queue never came here anyway; what does is a rollup a minute at a time, a row per cascade and the run history, and WAL keeps the readers going while that one writer works. DATA_DIR is now the one setting that moves everything an installation keeps; the rest derive from it and the images still spell theirs out. The schema is prepared in-process at startup, so the prestart service is gone, and the ten Postgres-only revisions collapse into one portable baseline. Three things only worked because psycopg was casting for us: a token's subject arriving as a string where the column is a UUID, `greatest`, and `date_bin`. The timestamps needed a column type of their own — SQLite stores no offset, and a naive datetime read back either raises against an aware `now` or serialises as local time. Postgres stays in the stack only for Umami, behind the analytics profile. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-21 22:19:45 +02:00
stroblmeandClaude Fable 5	b4d5aa6186	Let two backend CI runs share a runner host ... The job kept the fixed container names and the fixed 5432 that compose.ci.yml resets for every other job, so a second run could not start. Layering that file leaves the db on a port Docker assigns, which the suite is told about, and the project name is now per run so one teardown cannot take another run's database with it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01H7LwYgJfpkbLCTeiAf8U4A	2026-08-16 16:46:25 +02:00
Melvin StroblandClaude Opus 5	8a221bfe50	Add the Gitea Actions workflows ... Ports n3xd's four: pre-commit, backend tests, sharded Playwright and a compose smoke test. Everything comes from the committed .env.example, so no repository secrets are needed; Actions still has to be enabled per repository and a runner registered with the ubuntu-latest label. container_name, published ports and image tags are all daemon-global, so two shards on one runner would fight over them. compose.ci.yml resets them and tags per project. test-backend keeps the fixed names because it reaches Postgres from the runner host. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KkmeRiyeYmVZqJVwuyHq9o	2026-08-15 21:20:05 +02:00