From 7d1d7a3c08195706e89f7e00fbfc9181a08425b7 Mon Sep 17 00:00:00 2001 From: Burak Yigit Kaya Date: Mon, 23 Dec 2024 15:46:30 +0300 Subject: [PATCH] ref(self-hosted): Update docs for GeoIP update and `dc up -d` Companion PR for getsentry/self-hosted#3490 --- develop-docs/self-hosted/geolocation.mdx | 6 +++++- develop-docs/self-hosted/releases.mdx | 2 +- develop-docs/self-hosted/troubleshooting.mdx | 4 ++-- 3 files changed, 8 insertions(+), 4 deletions(-) diff --git a/develop-docs/self-hosted/geolocation.mdx b/develop-docs/self-hosted/geolocation.mdx index 9c7f2aaba6846..ea976c1a5777a 100644 --- a/develop-docs/self-hosted/geolocation.mdx +++ b/develop-docs/self-hosted/geolocation.mdx @@ -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 diff --git a/develop-docs/self-hosted/releases.mdx b/develop-docs/self-hosted/releases.mdx index dc0b3366dbb91..01a8b8487afc4 100644 --- a/develop-docs/self-hosted/releases.mdx +++ b/develop-docs/self-hosted/releases.mdx @@ -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 diff --git a/develop-docs/self-hosted/troubleshooting.mdx b/develop-docs/self-hosted/troubleshooting.mdx index a383577c961d9..b2fb6443a325b 100644 --- a/develop-docs/self-hosted/troubleshooting.mdx +++ b/develop-docs/self-hosted/troubleshooting.mdx @@ -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 @@ -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