Moves the image build off GitHub Actions and onto the homelab runner, pushing to this Gitea's container registry as an immutable short-SHA tag plus :latest.
Build-only: the GitHub workflow also SSHed into the Hostinger VPS and redeployed it on every push to main. Deploys now happen the way the rest of the homelab ships — a PR bumping the tag in ffaerber/homelab.
.github/workflows is removed from this copy so Gitea does not also try to run it (it would log in to ghcr with a Gitea token and SSH to a host whose secrets are not here). The GitHub repository is untouched.
Moves the image build off GitHub Actions and onto the homelab runner, pushing to this Gitea's container registry as an immutable short-SHA tag plus `:latest`.
Build-only: the GitHub workflow also SSHed into the Hostinger VPS and redeployed it on every push to `main`. Deploys now happen the way the rest of the homelab ships — a PR bumping the tag in `ffaerber/homelab`.
`.github/workflows` is removed from this copy so Gitea does not also try to run it (it would log in to ghcr with a Gitea token and SSH to a host whose secrets are not here). The GitHub repository is untouched.
This repo now lives on git.ffaerber.duckdns.org and its image is consumed by the
homelab swarm, so the build moves with it: .gitea/workflows/docker.yml builds on
the homelab runner and pushes to this Gitea's registry as an immutable short-SHA
tag plus :latest.
Build-only, on purpose. The GitHub workflow it replaces also SSHed into the
Hostinger VPS and ran `docker stack deploy` on every push to main, which
deploys the machine being retired and makes a deploy a side effect of a push.
The homelab pattern is a PR bumping the tag in ffaerber/homelab, so shipping is
a reviewed commit.
Plain `docker build` rather than buildx: the runner shares the host daemon
through a mounted socket, and buildx's gha cache backend does not exist outside
GitHub.
.github/workflows is removed from this copy so Gitea does not also try to run
it -- it would log in to ghcr with a Gitea token and SSH to a host whose secrets
are not here. The GitHub repository keeps its own copy untouched.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Moves the image build off GitHub Actions and onto the homelab runner, pushing to this Gitea's container registry as an immutable short-SHA tag plus
:latest.Build-only: the GitHub workflow also SSHed into the Hostinger VPS and redeployed it on every push to
main. Deploys now happen the way the rest of the homelab ships — a PR bumping the tag inffaerber/homelab..github/workflowsis removed from this copy so Gitea does not also try to run it (it would log in to ghcr with a Gitea token and SSH to a host whose secrets are not here). The GitHub repository is untouched.