Commit Graph
5 Commits
Author SHA1 Message Date
RyanandClaude Sonnet 5.5 9564880783 Don't fail the publish job when the package is already linked
CI/CD / test (push) Successful in 21s
CI/CD / publish (push) Successful in 15s
CI/CD / deploy (push) Successful in 4s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-26 11:39:34 +03:30
RyanandClaude Sonnet 5.5 c1141ad3af Deploy through the runner's Docker socket instead of SSH
CI/CD / test (push) Successful in 22s
CI/CD / publish (push) Failing after 18s
CI/CD / deploy (push) Skipped
The runner lives on the deployment server, so the deploy job runs
docker compose locally with a temporary registry login.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-26 11:37:45 +03:30
RyanandClaude Sonnet 5.5 894e3e25c6 Deploy from a Gitea registry image instead of building on the server
CI/CD / test (push) Failing after 7m19s
CI/CD / publish (push) Skipped
CI/CD / deploy (push) Skipped
CI now builds and pushes the image to the Gitea container registry, links
the package, and the deploy job ships only deploy/docker-compose.yml and an
.env naming the image to /opt/vending-machine-game.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-10-26 10:46:57 +03:30
HamedandClaude Opus 5.5 9832f303e8 Make CI and Docker builds survive an unreachable npm registry
CI/CD / test (push) Failing after 7m58s
CI/CD / deploy (push) Skipped
The Gitea runner hung for over 30 minutes on `npm ci` because it cannot
reach registry.npmjs.org. The registry is now configurable through the
NPM_REGISTRY repository variable, passed on to the server's Docker
build, and npm gives up after bounded retries. Jobs also have time
limits (test 15 min, deploy 30 min) so the runner is never held forever.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:15:49 +03:30
HamedandClaude Opus 5.5 22aa11bf32 Add Gitea Actions CI/CD
CI/CD / test (push) Canceled after 0s
CI/CD / deploy (push) Canceled after 0s
Every push and pull request installs, tests and builds the game. Pushes
to main then ship the sources to the server over SSH and restart the
site with docker compose; the deploy step is skipped until the
DEPLOY_HOST / DEPLOY_SSH_KEY secrets exist. An optional HEALTH_URL is
polled after deploying.

The Gitea server is now the `origin` remote; GitHub remains as `github`.
Gitea ignores .github/workflows while .gitea/workflows exists, so the
GitHub Pages workflow keeps running only on GitHub.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 10:07:54 +03:30