3 Commits

Include renames

Author	SHA1	Message	Date
tfaour	8ae09f238b	Push server image to local registry instead of git.thumeit.com ... Cloudflare (fronting git.thumeit.com) started rejecting image pushes with 413 Payload Too Large once whiteboard mode's Node runtime + native resvg bindings made the image significantly bigger than before. Switched the build/push target to a LAN-local registry (10.0.0.246:3000) that has nothing in front of it to hit that limit, and updated docker-compose.yml.example to match.	2026-07-23 17:10:21 -04:00
tfaour	2cd7283ce9	Fix Gitea Actions registry auth: use a PAT instead of the auto token ... The automatic GITHUB_TOKEN doesn't reliably authenticate against Gitea's Container Registry -- confirmed as a known, still-open limitation across several Gitea versions (multiple upstream issues, consistent with the 401/unauthorized error hit here). Gitea's own community guidance is to use a real Personal Access Token instead. Switches docker/login-action to a REGISTRY_TOKEN repo secret (a PAT with package write scope, created in Gitea's user settings) with an explicit username rather than the gitea.actor context, and drops the now-unused permissions: packages: write block that only applied to the auto token.	2026-07-18 15:50:11 -04:00
tfaour	1c1d9c6767	Add Gitea Actions workflow to build/push the server image ... Builds server/Dockerfile and pushes to this repo's Gitea Container Registry (git.thumeit.com/tfaour/espresso-frame-server) on every push to main that touches server/, tagged both latest and the commit SHA. docker-compose.yml now sets both image: and build: -- deploy hosts can docker compose pull to grab the CI-built image without needing this repo's build context, while local dev can still docker compose build against Dockerfile changes directly.	2026-07-18 14:38:55 -04:00