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

@@ -1,10 +1,13 @@
# Cap Standalone env for staging/prod. Copy to `.env` next to the compose file,
# chmod 600, and replace every CHANGE_ME value.
CAP_IMAGE=tiago2/cap:3.1.5
CAP_IMAGE=tiago2/cap:3.1.5@sha256:97455d85b5517172397c7053837d377c72ded6250777928d5435c3eab2f58779
ADMIN_KEY=CHANGE_ME_RANDOM_MIN_32_CHARS
REDIS_URL=redis://valkey:6379
REDIS_PREFIX=hivegrid:cap:
# Both supplied compose stacks use a dedicated Valkey instance. Keep this empty:
# Cap 3.1.5 does not prefix HMSET during site-key creation, so a non-empty
# prefix creates dashboard entries that the challenge endpoint cannot read.
REDIS_PREFIX=
# Serve widget.js and WASM from the self-hosted Cap instance instead of jsDelivr.
ENABLE_ASSETS_SERVER=true
@@ -13,7 +16,7 @@ WASM_VERSION=0.0.7
# Comma-separated browser origins allowed to generate/redeem challenges.
# Staging example:
# CORS_ORIGIN=https://staging-app.hivegrid.de,https://staging-api.hivegrid.de
# CORS_ORIGIN=https://staging-app.hivegrid.de,https://staging-api.hivegrid.de,https://staging.hivegrid.de,https://staging-portal.hivegrid.de
# Production example:
# CORS_ORIGIN=https://app.hivegrid.de,https://admin.hivegrid.de,https://api.hivegrid.de
CORS_ORIGIN=
@@ -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:
@@ -10,7 +10,7 @@ volumes:
services:
cap:
image: ${CAP_IMAGE:-tiago2/cap:3.1.5}
image: ${CAP_IMAGE:-tiago2/cap:3.1.5@sha256:97455d85b5517172397c7053837d377c72ded6250777928d5435c3eab2f58779}
restart: unless-stopped
env_file: [.env]
expose:
@@ -23,7 +23,7 @@ services:
condition: service_healthy
valkey:
image: valkey/valkey:9-alpine
image: valkey/valkey:9-alpine@sha256:ee91f7a174ac4d6a6b0685b3a60e321f0a9dbbb691f9b0e285be2ba1d1be8328
restart: unless-stopped
volumes:
- cap-valkey-data:/data
@@ -18,7 +18,7 @@ volumes:
services:
cap:
image: ${CAP_IMAGE:-tiago2/cap:3.1.5}
image: ${CAP_IMAGE:-tiago2/cap:3.1.5@sha256:97455d85b5517172397c7053837d377c72ded6250777928d5435c3eab2f58779}
restart: unless-stopped
networks:
cap-net:
@@ -33,7 +33,7 @@ services:
condition: service_healthy
valkey:
image: valkey/valkey:9-alpine
image: valkey/valkey:9-alpine@sha256:ee91f7a174ac4d6a6b0685b3a60e321f0a9dbbb691f9b0e285be2ba1d1be8328
restart: unless-stopped
networks: [cap-net]
volumes: