Refresh HiveGrid Cloud reference snapshot
This commit is contained in:
1 parent
5e99e14772
commit
7f88026f79
5955 files changed
+1177325
-188362
No files matched your search
@@ -12,7 +12,7 @@ For the lightweight alternative (GlitchTip, no Performance/Replay/OTLP), see
|
||||
|
||||
| Item | Value |
|
||||
| --- | --- |
|
||||
| Upstream | `getsentry/self-hosted` tag **`25.12.1`** |
|
||||
| Upstream | `getsentry/self-hosted` tag **`25.12.1`**, commit **`5c9794c9b1fda551f38515f85d56ec298371d060`** |
|
||||
| Public hostname | `https://sentry.boiler.saas-ctrl.com` |
|
||||
| Host | `boilerplate-staging` (`46.225.5.93`, Hetzner Nürnberg) |
|
||||
| Orchestrator | Coolify-managed Docker Compose, Traefik v3.6 in front |
|
||||
@@ -262,17 +262,18 @@ a one-time operator pass plus a quarterly review.
|
||||
host-port bindings inherited from upstream. Verify:
|
||||
`ss -tlnp | grep -E '5432|9000|9092|6379'` on the host shows
|
||||
**no** matches.
|
||||
- [ ] **Backups encrypted.** `backup.sh` uses GPG (recipient-key if
|
||||
`SENTRY_BACKUP_GPG_RECIPIENT` is set, AES256 symmetric with
|
||||
`SENTRY_SECRET_KEY` otherwise). Verify: `aws s3 cp` of a recent
|
||||
- [ ] **Backups encrypted with a separate key.** `backup.sh` requires the
|
||||
dedicated `SENTRY_BACKUP_GPG_RECIPIENT` and fails closed when it is
|
||||
absent. Runtime `SENTRY_SECRET_KEY` is never backup key material. Verify:
|
||||
`aws s3 cp` of a recent
|
||||
dump returns a file with header bytes `8c 0d` (GPG-armored) or
|
||||
`85 02` (binary GPG).
|
||||
- [ ] **Symbolicator: no external sym sources.** `sentry.conf.py` sets
|
||||
`SYMBOLICATOR_SYMSOURCES = []`. Verify: `docker compose exec
|
||||
symbolicator cat /etc/symbolicator/config.yml | grep sources`
|
||||
shows no Microsoft / Mozilla / Apple entries.
|
||||
- [ ] **SENTRY_SECRET_KEY stored offline.** Lost key = unreadable
|
||||
backups. Copy from Coolify vault to a hardware-backed password
|
||||
- [ ] **Backup recipient private key stored offline.** Lost key = unreadable
|
||||
backups. Store it separately from the Sentry runtime secrets in a hardware-backed password
|
||||
manager (1Password, BitWarden Premium with TOTP, YubiKey-backed
|
||||
pass).
|
||||
- [ ] **Traefik dashboard port 8080 firewalled.** Close at Hetzner Cloud
|
||||
@@ -286,8 +287,7 @@ per quarter, (c) before opening Sentry to additional users.
|
||||
|
||||
## CI Secrets
|
||||
|
||||
The CI pipelines in `.github/workflows/_sentry-release.yml` and
|
||||
`.gitea/workflows/_sentry-release.yml` need three Sentry secrets to tag
|
||||
The CI pipeline in `.gitea/workflows/_sentry-release.yml` needs three Sentry secrets to tag
|
||||
releases, upload source-maps, correlate commits, and mark deploys. The
|
||||
main CI build uploads `apps/web/build/client` as the
|
||||
`web-client-sourcemaps` workflow artifact; the reusable web release job
|
||||
@@ -312,30 +312,12 @@ and passes source-maps through the workflow artifact instead.
|
||||
`member:admin`.
|
||||
4. Copy the token immediately — Sentry only shows it once.
|
||||
|
||||
### 2. Store secrets in GitHub Actions
|
||||
|
||||
Navigate to **Settings → Secrets and variables → Actions** in the
|
||||
GitHub mirror (`github.com/<org>/boilerplate`) and add three repository
|
||||
secrets:
|
||||
|
||||
| Name | Value |
|
||||
| --- | --- |
|
||||
| `SENTRY_AUTH_TOKEN` | The token minted in step 1 |
|
||||
| `SENTRY_ORG` | `sentry` (the auto-generated slug from single-org install) |
|
||||
| `SENTRY_URL` | `https://sentry.boiler.saas-ctrl.com` |
|
||||
|
||||
Once configured, `_sentry-release.yml` is invoked once per project
|
||||
(api/worker/web) at the end of every CI run via `workflow_call`.
|
||||
Only the web invocation passes `sourcemaps-artifact:
|
||||
web-client-sourcemaps`; api and worker releases pass `sourcemaps-path:
|
||||
none`.
|
||||
|
||||
### 3. Store secrets in Gitea Actions
|
||||
### 2. Store secrets in Gitea Actions
|
||||
|
||||
In Gitea (`git.tool-ctrl.de/toolctrl-labs/HiveGrid-Cloud`) open
|
||||
**Repository Settings → Actions → Secrets** and create the same three
|
||||
secrets (`SENTRY_AUTH_TOKEN`, `SENTRY_ORG`, `SENTRY_URL`) with
|
||||
identical values. Gitea's secret scoping rules mirror GitHub's, so the
|
||||
identical values. Gitea's repository secret scoping makes them available to the
|
||||
reusable workflow at `.gitea/workflows/_sentry-release.yml` (and the
|
||||
composite-action fallback at `.gitea/actions/sentry-release/action.yml`
|
||||
for runner versions < 1.21) will pick them up automatically.
|
||||
@@ -345,22 +327,21 @@ secrets in its **Mark Sentry deploy** step; if the secrets are absent
|
||||
the step skips silently so existing deploy paths continue to function
|
||||
during the rollout window.
|
||||
|
||||
### 4. Rotation
|
||||
### 3. Rotation
|
||||
|
||||
- **Rotate every 6 months.** Add a recurring calendar entry for the
|
||||
operator on-call.
|
||||
- Rotation procedure:
|
||||
1. Mint a new token (step 1) with the same `project:releases` scope.
|
||||
2. Update `SENTRY_AUTH_TOKEN` in **both** GitHub and Gitea secret
|
||||
stores within the same maintenance window.
|
||||
3. Wait for one CI run on each system to confirm the new token works
|
||||
2. Update `SENTRY_AUTH_TOKEN` in the Gitea repository secret store.
|
||||
3. Wait for one CI run to confirm the new token works
|
||||
(look for a fresh release in the Sentry UI).
|
||||
4. Revoke the old token via the Sentry UI (Settings → Account →
|
||||
API → Auth Tokens → trash icon).
|
||||
- **Next scheduled rotation: 2026-11-17.** Update this date after each
|
||||
rotation.
|
||||
|
||||
### 5. Local development
|
||||
### 4. Local development
|
||||
|
||||
Releases are a CI-only concern. Local developers do **not** need
|
||||
`SENTRY_AUTH_TOKEN`; the web Vite build only uploads source-maps when
|
||||
|
||||
Reference in new issue
Block a user