Document Sentry self-hosted deployment

This commit is contained in:
2026-07-08 15:31:21 +03:30
parent 3f94ced9ea
commit ea638c0eae
11 changed files with 491 additions and 128 deletions
+44
View File
@@ -241,6 +241,47 @@ The 2026-07-08 runtime snapshot verified `nextcloud_nextcloud_data` and `nextclo
---
#### Sentry
Deployment model:
```text
Upstream Sentry self-hosted install.sh
```
Contains:
* `/srv/docker/sentry`
* Generated Sentry configuration
* PostgreSQL metadata
* ClickHouse event data
* Redis cache and coordination data
* Kafka data if persistence is enabled
* SeaweedFS attachments and object storage
Required:
* Backup of `/srv/docker/sentry`
* Backup of Sentry generated config and secret files
* Backup of persistent Sentry Docker volumes
* Nginx Proxy Manager route and certificate state for `sentry.silveressence.net`
Importance:
Critical
Sentry is not a normal SilverLinux `slcompose` service. Preserve its upstream self-hosted installer layout and restore it as one deployment unit.
Verified configuration files:
```text
/srv/docker/sentry/.env
/srv/docker/sentry/docker-compose.yml
/srv/docker/sentry/sentry/sentry.conf.py
```
---
#### Nginx Proxy Manager
Locations:
@@ -526,6 +567,7 @@ Restore order:
11. DbGate
12. Xray
13. Nextcloud
14. Sentry
---
@@ -550,6 +592,8 @@ Verified:
Nextcloud restore validation is pending after its 2026-07-08 operational documentation update.
Sentry restore validation is pending after its upstream `install.sh` deployment documentation update.
Validation results:
* MSSQL backup integrity verified