Cloud README: GET /admin/status is for anyone signed in; only POST /admin/build is admin-only
The route table put both under OIDC_ADMIN_GROUPS. admin.mjs checks the admin group on the build only; status answers any signed-in team member (commit SHAs and build state, nothing more). Measured: a designer reads /admin/status (200) and is refused the build (403, "builds are for team admins").
This commit is contained in:
parent
ffebd14377
commit
8c72b8a309
1 changed files with 2 additions and 1 deletions
|
|
@ -70,7 +70,8 @@ With the sign-in on, the container also runs PocketBase and can publish a produc
|
|||
| `/pb/` | signed-in (its `/_/` dashboard: `OIDC_ADMIN_GROUPS` only). With `PB_OIDC_CLIENT_SECRET`, its `/api/` is public and PocketBase signs people in itself (see below); `_superusers` and system collections stay admin-only | PocketBase **dev**, the team's shared backend |
|
||||
| `/api-prod/api/` | **public** | PocketBase **prod**'s API; its dashboard is never exposed |
|
||||
| `/cdn/dx-maps/` | **public** | the last published build: `manifest.json` at a stable URL, CORS open for embeds |
|
||||
| `POST /admin/build` · `GET /admin/status` | `OIDC_ADMIN_GROUPS` only | build and publish the pulled commit |
|
||||
| `POST /admin/build` | `OIDC_ADMIN_GROUPS` only | build and publish the pulled commit |
|
||||
| `GET /admin/status` | signed-in | the published and pulled commits, and whether a build is running |
|
||||
|
||||
A build runs one at a time (a second gets `409`), on a snapshot of the pulled commit, with Node's heap
|
||||
capped. It removes everything in [`public-exclusions.txt`](./public-exclusions.txt) **before**
|
||||
|
|
|
|||
Loading…
Reference in a new issue