Skip to content

add instructons to enable geolocation #12

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

Merged
Angel-Padilla merged 1 commit into from
Nov 19, 2025
Merged

add instructons to enable geolocation #12

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
16 changes: 12 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,14 @@ Documentation [here](https://develop.sentry.dev/self-hosted/).

## Meticulous Espresso instance

### Geo location

In order to use the geolocation capabilites of sentry, You need to provide a geolocation database from MaxMind, for which You will require an valid Account in MaxMind, it is free

The Sentry Project makes use of the GeoIPUpdate product from MaxMind to download/update its database, so the only requirement is to provide the `GeoIP.conf` to the `geoip` directory, running `install.sh` will call an update process to the database alongside. If You dont provide a `GeoIP.conf` file, the database will be empty

For more information visit [Sentry: Geolocation](https://develop.sentry.dev/self-hosted/geolocation/) and [MaxMind: Updating GeoIP and GeoLite Databases ](https://dev.maxmind.com/geoip/updating-databases/#directly-downloading-databases)

### Custom files

#### configure-swap.sh
Expand All @@ -31,10 +39,10 @@ Documentation [here](https://develop.sentry.dev/self-hosted/).
### External requirements

#### Docker
The Self-Hosted Sentry deploymentent is completely containarized
The Self-Hosted Sentry deploymentent is mostly containarized

#### Nginx
We run an Nginx instance in the VPS that handles SSL termination and redirects the request to `http://localhost:8081` where its listen and responded to by the sentry deployment
#### NGINX
The VPS should run an NGINX instance that handles SSL termination and redirects the request to `http://localhost:8081` where its listen and responded to by the sentry deployment

#### Certbot
To get the SSL certificates for `sentry.meticulousespresso.com` used by Nginx
To get the SSL certificates for `sentry.meticulousespresso.com` used by NGINX