Adopt the proven notify-bridge pipeline pattern and fix deployment bugs.
Workflows:
- build.yml: split into parallel frontend / backend / build-image jobs.
Run svelte-check + vitest + `go vet ./...` + `go test ./internal/...`
(tests were never executed in CI). Use buildx with GHA layer cache and
pin Go to 1.25. Quote the `if:` skip-guard so it is valid YAML.
- release.yml: gate the release on a passing test job, then build & push
the image, then create the Gitea release LAST so a failed image build
can no longer leave an orphan release. Use buildx + registry buildcache,
a hard registry login (a push failure now fails the release), and
auto-generate a changelog between tags.
Docker:
- Dockerfile: pin golang to 1.25 (matches go.mod's `go 1.25.0`), add
BuildKit cache mounts for the module + build caches, an OCI source
label, VOLUME /app/data, and a HEALTHCHECK on /readyz.
- docker-compose.yml: fix the healthcheck — it targeted POST-only
/api/auth/login (405 -> always unhealthy); now /readyz. Point the image
name at the Gitea registry tag with build-from-source as the default.
- .dockerignore: exclude ~95 MB of stray binaries, logs, env, and CI/doc
files from the build context.
Rebrand the project as Tinyforge to reflect its evolution from a Docker
container watcher into a self-hosted mini CI/deployment platform.
Rename covers: Go module path, Docker labels, DB/config filenames,
JWT issuer, Dockerfile binary, docker-compose, CI workflows, frontend
i18n, README with static sites docs, and all code comments.
alexei.dolgolyov