food-market/deploy/forgejo/food-market-forgejo-mirror.timer at 9891280bfdb4d5c5528b04545f4dd7443441c680 - nns/food-market - food-market git

nns/food-market

nurdotnet afbf01304a

CI / Backend (.NET 8) (push) Waiting to run

Details

CI / Web (React + Vite) (push) Waiting to run

Details

CI / POS (WPF, Windows) (push) Waiting to run

Details

Docker Images / API image (push) Failing after 15s

Details

Docker Images / Web image (push) Failing after 2s

Details

ops: Forgejo on git.zat.kz as primary, GitHub as mirror

Pushing straight to GitHub from KZ is a lottery — TCP to github.com
times out often enough that git push becomes a flake. Fix: Forgejo runs
on the stage server (sqlite, single container), all pushes go there
first (local network, always reliable), a systemd timer mirrors the
whole repo into GitHub every 10 minutes so GitHub stays up-to-date as
a backup + CI source.

What's committed here is the infra-as-code side:
- deploy/forgejo/docker-compose.yml — Forgejo 7 on :3000 (HTTP) and :2222 (SSH)
- deploy/forgejo/food-market-forgejo.service — systemd unit that drives compose
- deploy/forgejo/mirror-to-github.sh + mirror timer/service — push to GH every 10 min
- deploy/forgejo/nginx.conf — vhost for git.zat.kz (certbot to be run once DNS is set)
- docs/forgejo.md — how to clone/push, operations, what's left for the user (DNS + certbot)

GitHub Actions CI is untouched: commits land on GitHub via the mirror
and the self-hosted runner picks them up as before.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-23 12:27:45 +05:00

11 lines

177 B

SYSTEMD

Raw Blame History

 [Unit]
 Description=Mirror Forgejo -> GitHub every 10 min
 [Timer]
 OnBootSec=3min
 OnUnitActiveSec=10min
 Unit=food-market-forgejo-mirror.service
 [Install]
 WantedBy=timers.target