From 08cfe7ef6ab973c38640a17890d689633372e672 Mon Sep 17 00:00:00 2001 From: Reinaldy Rafli Date: Sat, 13 Sep 2025 15:26:55 +0700 Subject: [PATCH] docs(self-hosted): recommend SENTRY_AIR_GAP flag for air-gapped installation --- develop-docs/self-hosted/index.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/develop-docs/self-hosted/index.mdx b/develop-docs/self-hosted/index.mdx index 2d1f299686202..9af4c63f452b6 100644 --- a/develop-docs/self-hosted/index.mdx +++ b/develop-docs/self-hosted/index.mdx @@ -85,6 +85,8 @@ Starting with the 22.10.0 release, we will require those running the Sentry inst Sentry can run in air-gapped environments, where there are no internet access. Depending on how air-tight your environment is, the best way to do so is to do installation and upgrades behind a proxy, see [Installing Behind a Proxy](#installing-behind-a-proxy) below. If it's not possible, you may build the entire Docker Compose stack on another machine, use `docker commit` to "freeze" the images, then use combination of `docker save` and `docker load` which convert the image as a `.tar` file and transfer it into the air-gapped machine. Then, you can use `docker-compose up` to start the services. Although this may seem possible, we don't provide any further help for this use case, as it's not a common scenario. +It is recommended to set `SENTRY_AIR_GAP` to `True` on your `sentry/sentry.conf.py` file to make sure there are no network calls from your Sentry installation. + ### Self-hosted Beacon If you opt-in to it, self-hosted Sentry will periodically communicate with a remote beacon server. This is utilized for a couple of things, primarily: