Point CI and deploy at app_catalog.print_forge on master.

Gitea was still targeting main and a leftover client-ci compose name, so PRs and server-infra --app print_forge would miss each other.
2026-09-06 20:31:42 -05:00
parent 9f2d349974
commit 5ea7cce56b
5 changed files with 9 additions and 5 deletions
@@ -43,7 +43,7 @@ jobs:
            COMPOSE_DATABASE_URL DJANGO_ENV DJANGO_SECRET_KEY DJANGO_DEBUG \
            DJANGO_ALLOWED_HOSTS || true

-          PROJECT="client-ci-${{ gitea.sha }}"
+          PROJECT="print-forge-ci-${{ gitea.sha }}"
          cleanup() { docker compose -p "$PROJECT" down -v --remove-orphans || true; }
          trap cleanup EXIT

@@ -64,6 +64,7 @@ jobs:
      SERVER_INFRA_ROOT: /home/westfarn/Documents/repos/server-infra
      ANSIBLE_PRIVATE_KEY_FILE: /home/westfarn/.ssh/ansible_deploy
    steps:
+      # --app must match server-infra app_catalog (print_forge).
      - name: Deploy print_forge prod to all webservers
        run: |
          "$SERVER_INFRA_ROOT/scripts/deploy.sh" \