Skip to content

Sentry: Install, Backup and Re-Install

Requirements

According to the official documentation, the minimum requirements for Sentry 24.x are 4 CPU cores / 16 GB RAM (Nov 2024), and RAM is more important.

My tests show that Sentry 24.x runs on the following VPS configurations:

ProviderServerCPU coresRAM
HetznerCPX41416 GB
ContaboVPS 2616 GB

cpu

ram

Additional requirements are Docker Engine and optionally reverse proxy.

Before re-install

Backup config files

  • sentry/config.yml
  • sentry/sentry.conf.py
  • sentry/enhance-image.sh
  • geoip/GeoIP.conf
  • .env.custom

Backup settings

e.g. to file sentry/backup.json by following command:

shell
./sentry-admin.sh export global /etc/sentry/backup.json

You may not have permission to create this file, then you can create it yourself and grant write permissions.

Docs: Backup & Restore

Before install

Follow the official installation documentation, but before running install.sh make sure you have the following files in the correct places:

Important config files

  • sentry/config.yml configured from sentry/config.example.yml.
  • sentry/sentry.conf.py configured from sentry/sentry.conf.example.py.

When restoring settings

  • sentry/backup.json if you want to restore the Sentry Configuration from backup.

Additional config files

  • sentry/enhance-image.sh configured from sentry/enhance-image.example.sh.
  • geoip/GeoIP.conf configured from documentation.

After install

If you want to restore the Sentry Configuration, answer the following question with n and follow the steps below:

Would you like to create a user account now? [Y/n]: n
shell
./sentry-admin.sh import global /etc/sentry/backup.json
Proceeding with this operation will irrecoverably delete all existing
low-volume data - are you sure want to continue? [y/n]: y

Starting up

shell
docker compose up -d

Side Notes

--no-report-self-hosted-issues

Set env variable in file /etc/environment:

txt
REPORT_SELF_HOSTED_ISSUES=0

To avoid reporting error and performance data for your Sentry instance.