Refresh HiveGrid Cloud reference snapshot

This commit is contained in:
david committed 2026-08-03 15:31:14 +02:00
1 parent 5e99e14772
commit 7f88026f79
5955 files changed
+1177325 -188362

No files matched your search

@@ -30,9 +30,16 @@ Traefik can reach it without publishing Cap directly to the public interface.
3. Create `/opt/cap/.env` from `.env.example`, set `ADMIN_KEY`, and set:
```env
CORS_ORIGIN=https://staging-app.hivegrid.de,https://staging-api.hivegrid.de,https://staging.hivegrid.de
CORS_ORIGIN=https://staging-app.hivegrid.de,https://staging-api.hivegrid.de,https://staging.hivegrid.de,https://staging-portal.hivegrid.de
REDIS_PREFIX=
```
The supplied stack owns its Valkey instance exclusively. Keep
`REDIS_PREFIX` empty with Cap 3.1.5: its site-key creation path does not
prefix `HMSET`, while the challenge path prefixes reads. A non-empty value
therefore creates keys that are visible in the dashboard but always return
`404` from `/<sitekey>/challenge`.
4. Start Cap:
```sh
@@ -48,7 +55,9 @@ Traefik can reach it without publishing Cap directly to the public interface.
6. Open `https://captcha-staging.hivegrid.de`, log in with `ADMIN_KEY`, and
create site keys for `login`, `forms`, and `booking`. Keep each public
sitekey and its matching site secret.
sitekey and its matching site secret. Before rolling them out, prove that
`POST /<sitekey>/challenge` returns `200` for every key and includes the
requesting staging origin in `Access-Control-Allow-Origin`.
7. Set the staging web app env: