docs: update plan for migration of backend
This commit is contained in:
@@ -13,7 +13,7 @@
|
||||
## Lifecycle Phases
|
||||
|
||||
1. **Local Dev** — `yarn dev` + `npx supabase start` (Podman)
|
||||
2. **Dev server** — `bab1.mgmt.toal.ca` — static site via nginx; backend = supabase.com
|
||||
2. **Dev server** — `https://bab.toal.ca` (nginx on `bab1.mgmt.toal.ca`, webroot `/usr/share/nginx/html/`); backend = supabase.com
|
||||
3. **Production** — static site on AWS S3; backend = supabase.com
|
||||
|
||||
## Backend Hosting
|
||||
@@ -77,6 +77,8 @@ Format: `kv/oys/(dev|prod|shared)/(supabase|app|infra)/<secretname>`
|
||||
**Local dev:** Secrets in `.env` (git-ignored). Do not put real values in `.env.example`.
|
||||
**AAP:** Vault lookup plugin as a credential type.
|
||||
**Gitea Actions:** Variable `ENV_FILE` (per branch) populated by AAP sync playbook (see below).
|
||||
**Gitea URL:** `https://gitea.toal.ca/`
|
||||
**Gitea artifact download token:** `kv/oys/bab_gitea` (pre-existing secret; deviates from naming convention — use as-is).
|
||||
|
||||
### Gitea Actions Secret Injection
|
||||
|
||||
|
||||
Reference in New Issue
Block a user