Skip to content
This repository has been archived by the owner on Aug 14, 2024. It is now read-only.

fix(docs): Move alert next to options it references #1067

Merged
merged 1 commit into from
Oct 31, 2023
Merged

fix(docs): Move alert next to options it references #1067

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/docs/self-hosted/backup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,10 +15,6 @@ This script creates a `backup.json` file in the `sentry` directory in your main
./scripts/backup.sh
```

<Alert title="Note" level="info"><markdown>
If you omit the `-T` or `-e SENTRY_LOG_LEVEL=CRITICAL` parts, your backup file will have logging lines mixed in and you'll have to remove them somehow.
</markdown></Alert>

### Restore

Once you have a backup by using the backup script, the easiest way to restore it is to place it under the `sentry` directory in your main `self-hosted` repo, next to the config files. This directory automatically gets mounted to `/etc/sentry` so you can run the following to restore your backup:
Expand All @@ -42,6 +38,10 @@ If you're running on a version of self-hosted Sentry that is below 23.3.1, you'l
docker-compose run -v $(pwd)/sentry:/sentry-data/backup --rm -T -e SENTRY_LOG_LEVEL=CRITICAL web export /sentry-data/backup/backup.json
```

<Alert title="Note" level="info"><markdown>
If you omit the `-T` or `-e SENTRY_LOG_LEVEL=CRITICAL` parts, your backup file will have logging lines mixed in and you'll have to remove them somehow.
</markdown></Alert>

#### Restore
```shell
docker-compose run --rm -T web import /etc/sentry/backup.json
Expand Down
Loading