Deploy workflows still call server-infra/scripts/deploy.sh --app client_site (client-site template leftover). server-infra catalogs this app as college_craft (server-infra#24, PR #25). Until --app matches the catalog name, CI deploy is a no-op / loud fail and never hits the new host_apps rows.
Default branch is master, not main. Beta deploy currently triggers on main, so pushes to master never run it.
Also rename the deploy step (Deploy client_site … → Deploy college_craft …).
2. Beta trigger on master
In deploy-beta.yml:
on:
push:
branches:
- - main
+ - master
Without this, CI never deploys beta on the default branch.
Optional (same PR)
Docker CI still uses template names (PROJECT=client-ci-…, DATABASE_URL=postgres://client_site:client_site@db:5432/client_site). That only affects the workflow-local compose tests, not Ansible catalog matching — rename if convenient.
Depends on
Merge server-infra#25 first (catalog + ports). Secrets + Postgres DBs still need to exist before the first real deploy.
## Summary
Deploy workflows still call `server-infra/scripts/deploy.sh --app client_site` (client-site template leftover). `server-infra` catalogs this app as **`college_craft`** ([server-infra#24](https://git.aimloperations.com/ai_ml_operations/server-infra/issues/24), [PR #25](https://git.aimloperations.com/ai_ml_operations/server-infra/pulls/25)). Until `--app` matches the catalog name, CI deploy is a no-op / loud fail and never hits the new host_apps rows.
Default branch is **`master`**, not `main`. Beta deploy currently triggers on `main`, so pushes to `master` never run it.
## Files
- [`.gitea/workflows/deploy-beta.yml`](https://git.aimloperations.com/ai_ml_operations/college_craft/src/branch/master/.gitea/workflows/deploy-beta.yml)
- [`.gitea/workflows/deploy-prod.yml`](https://git.aimloperations.com/ai_ml_operations/college_craft/src/branch/master/.gitea/workflows/deploy-prod.yml)
## Required
### 1. `--app college_craft`
In both workflows:
```diff
- --app client_site
+ --app college_craft
```
Also rename the deploy step (`Deploy client_site …` → `Deploy college_craft …`).
### 2. Beta trigger on `master`
In `deploy-beta.yml`:
```diff
on:
push:
branches:
- - main
+ - master
```
Without this, CI never deploys beta on the default branch.
## Optional (same PR)
Docker CI still uses template names (`PROJECT=client-ci-…`, `DATABASE_URL=postgres://client_site:client_site@db:5432/client_site`). That only affects the workflow-local compose tests, not Ansible catalog matching — rename if convenient.
## Depends on
Merge [server-infra#25](https://git.aimloperations.com/ai_ml_operations/server-infra/pulls/25) first (catalog + ports). Secrets + Postgres DBs still need to exist before the first real deploy.
westfarn
self-assigned this 2026-09-02 06:57:45 -07:00
westfarn
changed title from Point deploy workflows at --app college_craft (not client_site) to Point deploy workflows at --app college_craft and trigger beta on master2026-09-02 06:58:29 -07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Deploy workflows still call
server-infra/scripts/deploy.sh --app client_site(client-site template leftover).server-infracatalogs this app ascollege_craft(server-infra#24, PR #25). Until--appmatches the catalog name, CI deploy is a no-op / loud fail and never hits the new host_apps rows.Default branch is
master, notmain. Beta deploy currently triggers onmain, so pushes tomasternever run it.Files
.gitea/workflows/deploy-beta.yml.gitea/workflows/deploy-prod.ymlRequired
1.
--app college_craftIn both workflows:
Also rename the deploy step (
Deploy client_site …→Deploy college_craft …).2. Beta trigger on
masterIn
deploy-beta.yml:Without this, CI never deploys beta on the default branch.
Optional (same PR)
Docker CI still uses template names (
PROJECT=client-ci-…,DATABASE_URL=postgres://client_site:client_site@db:5432/client_site). That only affects the workflow-local compose tests, not Ansible catalog matching — rename if convenient.Depends on
Merge server-infra#25 first (catalog + ports). Secrets + Postgres DBs still need to exist before the first real deploy.
Point deploy workflows at --app college_craft (not client_site)to Point deploy workflows at --app college_craft and trigger beta on master