Files
newsfeed/.gitea/workflows/deploy.yml
rob thijssen 62d5bc6569
Some checks failed
deploy / build-web (push) Successful in 1m27s
deploy / deploy-web (push) Successful in 4s
deploy / build-api (push) Successful in 6m16s
deploy / deploy-api (push) Failing after 30s
ci(deploy): keep deploy jobs on fedora-43 (ssh is present via git-core)
Reverts the move to `infra`. Verified on a fedora-43 runner that the ssh
reachability check ran fine (it added the host key and connected) — the
earlier deploy failure was the unprovisioned remote sudo step, not a missing
ssh client. Every runner has ssh: `git` (installed for checkout) pulls
`git-core`, which hard-requires `openssh-clients`. So fedora-43 (ssh + rsync +
curl) is the right, lighter runner for these deploy jobs.

See architecture gitea-runners.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016fKZzDpvjiJ9eYbPGgJvUP
2026-07-08 12:10:43 +03:00

158 lines
5.6 KiB
YAML

# CI-driven deploy for newsfeed (architecture deployment-gitea-actions.md).
#
# The workflow is the source of infra truth — hosts/ports/paths live here, not in a
# manifest. Build-and-rsync model: build the binaries + the SPA bundle, then rsync
# straight to the targets as the scoped `gitea_ci` user.
#
# api + worker -> slartibartfast.kosherinata.internal (share one SQLite file)
# web (SPA) -> oolon.kosherinata.internal (nginx serves + proxies /v1)
#
# Runners (see architecture gitea-runners.md): Rust build on `rust` (cargo toolchain);
# SPA build + deploy jobs on `fedora-43` (node + pnpm; ssh via git-core's openssh-clients
# dep; rsync + curl in the base). The whole fleet is Fedora, so binaries are built native —
# no glibc skew, no musl toolchain needed (deployment-gitea-actions.md §6: build on a
# runner no newer than the oldest target).
#
# One-time host prep (gitea_ci user, sudoers, service account, dirs, cert, vhost) is done
# by script/infra-setup.sh. Only secret required here: RSYNC_SSH_KEY (the runner's private
# key). newsfeed has no app secrets — SQLite has no password and tokens are hashed at rest.
name: deploy
on:
push:
branches: [main]
workflow_dispatch:
concurrency:
group: deploy
cancel-in-progress: false
env:
API_HOST: slartibartfast.kosherinata.internal
WEB_HOST: oolon.kosherinata.internal
API_PORT: "8081"
SSH_OPTS: -o StrictHostKeyChecking=accept-new
jobs:
build-api:
runs-on: rust
steps:
- uses: actions/checkout@v4
# lint/test gate: a broken commit never deploys
- run: cargo fmt --all --check
- run: cargo clippy --workspace --all-targets -- -D warnings
- run: cargo test --workspace
- name: build binaries
run: |
cargo build --release -p newsfeed-api -p newsfeed-worker
mkdir -p out
cp target/release/newsfeed-api target/release/newsfeed-worker out/
- uses: actions/upload-artifact@v3
with:
name: binaries
path: out/
build-web:
runs-on: fedora-43
steps:
- uses: actions/checkout@v4
- name: build SPA
working-directory: web
# pnpm is preinstalled globally on the fedora runners (via npm i -g pnpm);
# Fedora's nodejs doesn't bundle corepack, so call pnpm directly.
run: |
pnpm install --frozen-lockfile
pnpm build
- uses: actions/upload-artifact@v3
with:
name: web
path: web/dist/
deploy-api:
needs: build-api
runs-on: fedora-43
steps:
- uses: actions/checkout@v4
- uses: actions/download-artifact@v3
with:
name: binaries
path: bin
- name: write ssh key
run: |
install -d -m 0700 ~/.ssh
echo "${{ secrets.RSYNC_SSH_KEY }}" > ~/.ssh/id_deploy
chmod 0600 ~/.ssh/id_deploy
- name: reachability check
run: ssh $SSH_OPTS -i ~/.ssh/id_deploy gitea_ci@"$API_HOST" hostname -f
- name: rsync binaries
run: |
chmod +x bin/*
for b in newsfeed-api newsfeed-worker; do
rsync -az -e "ssh $SSH_OPTS -i ~/.ssh/id_deploy" \
--rsync-path='sudo rsync' --chown=root:root --chmod=0755 --mkpath \
"bin/$b" gitea_ci@"$API_HOST":/usr/local/bin/"$b"
done
- name: rsync config
run: |
rsync -az -e "ssh $SSH_OPTS -i ~/.ssh/id_deploy" \
--rsync-path='sudo rsync' --chown=root:newsfeed --chmod=0640 --mkpath \
asset/config/config.toml.tmpl gitea_ci@"$API_HOST":/etc/newsfeed/config.toml
rsync -az -e "ssh $SSH_OPTS -i ~/.ssh/id_deploy" \
--rsync-path='sudo rsync' --chown=root:newsfeed --chmod=0640 --mkpath \
asset/config/worker.toml.tmpl gitea_ci@"$API_HOST":/etc/newsfeed/worker.toml
- name: apply system state
run: |
ssh $SSH_OPTS -i ~/.ssh/id_deploy gitea_ci@"$API_HOST" '
sudo restorecon -R /usr/local/bin/newsfeed-api /usr/local/bin/newsfeed-worker /etc/newsfeed /var/lib/newsfeed
sudo systemctl daemon-reload
sudo systemctl restart newsfeed-api.service
sudo systemctl restart newsfeed-worker.service
'
- name: health probe
run: |
for i in $(seq 1 10); do
code=$(curl -fsS -o /dev/null -w '%{http_code}' "http://$API_HOST:$API_PORT/health") && [ "$code" = 200 ] && exit 0
sleep 2
done
echo "api did not become healthy" >&2; exit 1
- name: capture journal
if: always()
run: |
ssh $SSH_OPTS -i ~/.ssh/id_deploy gitea_ci@"$API_HOST" \
'journalctl -u newsfeed-api.service -u newsfeed-worker.service -n 80 --no-pager' || true
deploy-web:
needs: build-web
runs-on: fedora-43
steps:
- uses: actions/download-artifact@v3
with:
name: web
path: dist
- name: write ssh key
run: |
install -d -m 0700 ~/.ssh
echo "${{ secrets.RSYNC_SSH_KEY }}" > ~/.ssh/id_deploy
chmod 0600 ~/.ssh/id_deploy
- name: reachability check
run: ssh $SSH_OPTS -i ~/.ssh/id_deploy gitea_ci@"$WEB_HOST" hostname -f
- name: rsync SPA
run: |
rsync -az --delete -e "ssh $SSH_OPTS -i ~/.ssh/id_deploy" \
--rsync-path='sudo rsync' --chown=nginx:nginx --mkpath \
dist/ gitea_ci@"$WEB_HOST":/var/www/newsfeed/
- name: relabel + reload nginx
run: |
ssh $SSH_OPTS -i ~/.ssh/id_deploy gitea_ci@"$WEB_HOST" '
sudo restorecon -R /var/www/newsfeed
sudo nginx -t
sudo systemctl reload nginx.service
'