Deploy ABC beta from Development instead of master (#37)
Sync runner checkout / sync (push) Successful in 7s

## Summary
- A no-ref beta deploy of `abc_be`, `abc_worker`, and `abc_fe` checks out `Development` instead of `master`.
- `livekit` and every other app still use their current default branch.
- CI that passes `--ref` is unchanged; this only affects the catalog fallback.

## Test plan
- [ ] `scripts/deploy.sh --app abc_be --env beta` resolves ref `Development`
- [ ] Same for `abc_worker` and `abc_fe`
- [ ] `livekit` still resolves `master`

Reviewed-on: #37
This commit was merged in pull request #37.
This commit is contained in:
westfarn committed 2026-09-23 17:31:06 -07:00
1 parent 658152088e
commit d9621a984b
1 file changed
+3 -3
+3 -3
View File
@@ -160,14 +160,14 @@ app_catalog:
abc_be:
type: django
repo: "{{ git_base_url }}/GIS/abc_be.git"
default_branch: master
default_branch: Development
compose_file: docker-compose.prod.yml
web_service: web
migrate_cmd: "uv run python manage.py migrate --noinput"
abc_worker:
type: django
repo: "{{ git_base_url }}/GIS/abc_worker.git"
default_branch: master
default_branch: Development
compose_file: docker-compose.prod.yml
web_service: web
# FastAPI — no Django migrations. `true` keeps the django deploy path happy.
@@ -175,7 +175,7 @@ app_catalog:
abc_fe:
type: node-static
repo: "{{ git_base_url }}/GIS/abc_fe.git"
default_branch: master
default_branch: Development
webroot_pattern: "/var/www/{env}.abc.aimloperations/html"
livekit:
type: django