Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ref(self-hosted): Update docs for GeoIP update and dc up -d #12210

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+8 −4
Open

ref(self-hosted): Update docs for GeoIP update and dc up -d #12210

Show file tree
Hide file tree
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
6 changes: 5 additions & 1 deletion develop-docs/self-hosted/geolocation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,11 @@ With this configuration file in place, subsequent runs of Sentry's `install.sh`

1. For the `web` service: **User Settings > Security > Session History** should display country code and region (for example, "US (CA)") underneath the IP addresses in the table.

It's normal to see the `sentry_self_hosted_geoipupdate_1` container exit soon after startup, since updating the geolocation database is a one-off batch process and not a long-running job.
If you ever need to manually refresh the IP address geolocation database, you can run the following command:

```bash
./install/geoip.sh
```

## Upgrading

Expand Down
2 changes: 1 addition & 1 deletion develop-docs/self-hosted/releases.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ We may have some updated configuration, especially for new features, so always c

If you have a `.env.custom` file, make sure to copy new environment variables from the `.env` file into the `.env.custom` file before running the install script.

Finally, to upgrade, run `./install.sh`. Upon completion, run `docker compose up -d` (or if you have `.env.custom` file, run `docker compose --env-file .env --env-file .env.custom up -d`).
Finally, to upgrade, run `./install.sh`. Upon completion, run `docker compose up --wait` (or if you have `.env.custom` file, run `docker compose --env-file .env --env-file .env.custom up --wait`).

### Hard Stops

Expand Down
4 changes: 2 additions & 2 deletions develop-docs/self-hosted/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@ The _nuclear option_ is removing all Kafka-related volumes and recreating them w
```
4. Start the instance:
```shell
docker compose up -d
docker compose up --wait
```
### Reducing disk usage

Expand Down Expand Up @@ -178,7 +178,7 @@ Occasionally, you might see an error like this
container for service "${servicename}" is unhealthy
```

This can usually be resolved by running `docker compose down` and `docker compose up -d` or rerunning the install script.
This can usually be resolved by running `docker compose down` and `docker compose up --wait` or rerunning the install script.

## Docker Network Conflicting IP Address

Expand Down
Loading