haemka
575a5bf1e3
Latest diagnostic run showed aquaria's OpenSSH responding fine on the first of several near-simultaneous connections ssh-keyscan opens (one per default-probed key type), then hanging on the rest with no response — a rate-limiting signature, not an outright ban. Both hosts confirmed to offer an RSA host key, so scan just that type: one connection per host instead of ~4 at once. Left the diagnostic step in to confirm before removing it. Dropped -v now that the cause is known.
81 lines
3.2 KiB
YAML
81 lines
3.2 KiB
YAML
name: Build and deploy
|
|
|
|
on:
|
|
push:
|
|
branches: [master]
|
|
workflow_dispatch: {}
|
|
|
|
jobs:
|
|
build-and-deploy:
|
|
runs-on: self-hosted
|
|
container: python:3.12-slim
|
|
steps:
|
|
- name: Install system dependencies
|
|
run: |
|
|
apt-get update
|
|
apt-get install -y --no-install-recommends git rsync openssh-client nodejs netcat-openbsd dnsutils
|
|
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
with:
|
|
submodules: false
|
|
|
|
# Temporary diagnostic step — remove once the aquaria connectivity
|
|
# issue is root-caused. ssh-keyscan swallows pre-handshake failures
|
|
# even with -v, so this checks DNS + raw TCP connect independently.
|
|
- name: Diagnose connectivity to deploy host
|
|
env:
|
|
DEPLOY_HOST: ${{ vars.DEPLOY_HOST }}
|
|
DEPLOY_PORT: ${{ vars.DEPLOY_PORT }}
|
|
run: |
|
|
echo "--- DNS resolution ---"
|
|
getent hosts "$DEPLOY_HOST" || echo "getent: no result"
|
|
dig +short A "$DEPLOY_HOST" || true
|
|
dig +short AAAA "$DEPLOY_HOST" || true
|
|
echo "--- TCP connect (IPv4) ---"
|
|
nc -4 -zv -w 8 "$DEPLOY_HOST" "${DEPLOY_PORT:-22}" || echo "nc exit code: $?"
|
|
|
|
- name: Set up SSH key
|
|
# Same key used both as the theme repo's deploy key (Gitea) and for
|
|
# the webserver login (below) — one secret, two authorized_keys entries.
|
|
env:
|
|
DEPLOY_SSH_KEY: ${{ secrets.DEPLOY_SSH_KEY }}
|
|
DEPLOY_HOST: ${{ vars.DEPLOY_HOST }}
|
|
DEPLOY_PORT: ${{ vars.DEPLOY_PORT }}
|
|
run: |
|
|
mkdir -p ~/.ssh
|
|
printf '%s\n' "$DEPLOY_SSH_KEY" > ~/.ssh/deploy_key
|
|
chmod 600 ~/.ssh/deploy_key
|
|
# -t rsa: both hosts confirmed to offer an RSA host key. Restricting
|
|
# to one type means one connection per host instead of ~4 fired at
|
|
# once (one per probed key type), which aquaria's connection-rate
|
|
# limiting was intermittently dropping past the first.
|
|
ssh-keyscan -4 -t rsa -H git.haemka.in >> ~/.ssh/known_hosts
|
|
ssh-keyscan -4 -t rsa -H -p "${DEPLOY_PORT:-22}" "$DEPLOY_HOST" >> ~/.ssh/known_hosts
|
|
|
|
- name: Fetch theme submodule
|
|
run: |
|
|
# Override the submodule's tracked HTTPS URL for this checkout only,
|
|
# so it's fetched over SSH with the deploy key instead of needing a
|
|
# token with access to both repos.
|
|
git config submodule.themes/latex.url git@git.haemka.in:hmk/pelican-latex.git
|
|
GIT_SSH_COMMAND="ssh -4 -i ~/.ssh/deploy_key -o StrictHostKeyChecking=yes" \
|
|
git submodule update --init --recursive
|
|
|
|
- name: Install Python dependencies
|
|
run: pip install --no-cache-dir -r requirements.txt
|
|
|
|
- name: Build site
|
|
run: pelican -s publishconf.py
|
|
|
|
- name: Deploy via rsync
|
|
env:
|
|
DEPLOY_HOST: ${{ vars.DEPLOY_HOST }}
|
|
DEPLOY_PORT: ${{ vars.DEPLOY_PORT }}
|
|
DEPLOY_USER: ${{ secrets.DEPLOY_USER }}
|
|
DEPLOY_PATH: ${{ vars.DEPLOY_PATH }}
|
|
run: |
|
|
rsync -avz --delete \
|
|
-e "ssh -4 -i ~/.ssh/deploy_key -p ${DEPLOY_PORT:-22} -o StrictHostKeyChecking=yes" \
|
|
output/ "${DEPLOY_USER}@${DEPLOY_HOST}:${DEPLOY_PATH}"
|