# ----------------------------------------------------------------------------- # cameleer-website — Gitea Actions build + deploy # # Runner: self-hosted arm64 (Gitea Runner / act_runner). # Deploy target: Hetzner Webhosting L (amd64). # # Architecture mismatch does NOT matter: Astro's output is static HTML/CSS/JS # plus hashed assets. Nothing arch-specific ships in the bundle. Everything in # this workflow — Node 20, rsync, ssh, curl, chromium — has native arm64. # # The only non-trivial arm64 gotcha is Lighthouse CI: Google Chrome has no # stable Linux/arm64 build, so we install the distro-packaged Chromium and # hand its path to LHCI via CHROME_PATH. On amd64 runners this still works; # the step is idempotent if Chromium is already present. # # `runs-on` labels: # This file uses `ubuntu-latest`, which the default act_runner config maps # to `catthehacker/ubuntu:act-latest` (multi-arch, has apt + sudo). If your # runner is registered with different labels (e.g. `[self-hosted, arm64]`), # update `runs-on` below accordingly. # ----------------------------------------------------------------------------- name: build-test-deploy on: push: branches: [main] pull_request: branches: [main] jobs: build: runs-on: ubuntu-latest timeout-minutes: 20 env: PUBLIC_AUTH_SIGNIN_URL: ${{ vars.PUBLIC_AUTH_SIGNIN_URL }} PUBLIC_AUTH_SIGNUP_URL: ${{ vars.PUBLIC_AUTH_SIGNUP_URL }} PUBLIC_SALES_EMAIL: ${{ vars.PUBLIC_SALES_EMAIL }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' cache: 'npm' # Lighthouse CI needs a Chrome/Chromium binary at runtime. Google Chrome # has no Linux/arm64 build, so install distro Chromium and export its # path. Handles both `chromium` (Debian) and `chromium-browser` (older # Ubuntu) package names, and works whether sudo is present or absent # (e.g. runner running as root). - name: Install Chromium for Lighthouse CI shell: bash run: | set -e if command -v sudo >/dev/null 2>&1; then SUDO=sudo; else SUDO=; fi resolve_chromium() { command -v chromium 2>/dev/null \ || command -v chromium-browser 2>/dev/null \ || true } CHROME_BIN="$(resolve_chromium)" if [ -z "$CHROME_BIN" ]; then $SUDO apt-get update -qq $SUDO apt-get install -y --no-install-recommends \ chromium chromium-driver \ || $SUDO apt-get install -y --no-install-recommends \ chromium-browser chromium-chromedriver CHROME_BIN="$(resolve_chromium)" fi if [ -z "$CHROME_BIN" ]; then echo "Failed to install a Chromium binary — Lighthouse CI cannot run." exit 1 fi echo "CHROME_PATH=$CHROME_BIN" >> "$GITHUB_ENV" "$CHROME_BIN" --version || true - name: Install dependencies run: npm ci - name: Run unit tests run: npm test - name: Build site run: npm run build - name: Guard — no TBD markers may ship in built HTML run: | if grep -rl 'TBD:' dist 2>/dev/null | grep -E '\.(html|svg)$'; then echo "Built output contains unfilled markers." echo "Fill in imprint.astro and privacy.astro operator fields before merging to main." exit 1 fi - name: Validate HTML run: npm run lint:html - name: Check internal links run: npm run lint:links - name: Lighthouse CI env: CHROME_PATH: ${{ env.CHROME_PATH }} run: npx lhci autorun - name: Upload dist artifact if: github.ref == 'refs/heads/main' uses: actions/upload-artifact@v4 with: name: dist path: dist/ retention-days: 7 deploy: if: github.ref == 'refs/heads/main' needs: build runs-on: ubuntu-latest timeout-minutes: 10 concurrency: group: deploy-production cancel-in-progress: false steps: - name: Download dist artifact uses: actions/download-artifact@v4 with: name: dist path: dist/ - name: Configure SSH env: SFTP_KEY: ${{ secrets.SFTP_KEY }} SFTP_KNOWN_HOSTS: ${{ secrets.SFTP_KNOWN_HOSTS }} run: | set -e : "${SFTP_KEY:?SFTP_KEY secret must be set}" : "${SFTP_KNOWN_HOSTS:?SFTP_KNOWN_HOSTS secret must be set}" mkdir -p ~/.ssh printf '%s\n' "$SFTP_KEY" > ~/.ssh/id_ed25519 chmod 600 ~/.ssh/id_ed25519 printf '%s\n' "$SFTP_KNOWN_HOSTS" > ~/.ssh/known_hosts chmod 644 ~/.ssh/known_hosts # Ensure rsync + openssh are present even on a minimal runner image. if ! command -v rsync >/dev/null 2>&1 || ! command -v ssh >/dev/null 2>&1; then if command -v sudo >/dev/null 2>&1; then SUDO=sudo; else SUDO=; fi $SUDO apt-get update -qq $SUDO apt-get install -y --no-install-recommends rsync openssh-client fi - name: Deploy via rsync env: SFTP_USER: ${{ secrets.SFTP_USER }} SFTP_HOST: ${{ secrets.SFTP_HOST }} SFTP_PATH: ${{ secrets.SFTP_PATH }} run: | # Fail loudly if any secret is missing — otherwise rsync --delete # could be directed at the SSH user's home root. : "${SFTP_USER:?SFTP_USER secret must be set}" : "${SFTP_HOST:?SFTP_HOST secret must be set}" : "${SFTP_PATH:?SFTP_PATH secret must be set}" rsync -avz --delete \ -e "ssh -i ~/.ssh/id_ed25519 -o StrictHostKeyChecking=yes -o UserKnownHostsFile=~/.ssh/known_hosts" \ dist/ "$SFTP_USER@$SFTP_HOST:$SFTP_PATH/" - name: Post-deploy smoke test run: | set -e echo "Checking security headers on www.cameleer.io..." HEADERS=$(curl -sI https://www.cameleer.io/ || echo "") echo "$HEADERS" | grep -i '^strict-transport-security:' || { echo "HSTS missing"; exit 1; } echo "$HEADERS" | grep -i '^content-security-policy:' || { echo "CSP missing"; exit 1; } echo "$HEADERS" | grep -i '^x-frame-options:' || { echo "XFO missing"; exit 1; } echo "All required headers present on the live origin."