- Setup Repository
- Update Packages
- Install Packages
- Create Sentry User
- Setting up an Environment
- Install Sentry
- Database Setup
- Initializing the Configuration
- Running Migrations
- Starting the Web Service
- Setup a Reverse Proxy
- More Information
Create Sentry User
Setting up an Environment
- Once that’s done, choose a location for the environment, and create it with the virtualenv command. For our guide, we’re going to choose
Initializing the Configuration
- Now you’ll need to create the default configuration.
- To do this, you’ll use the
initcommand You can specify an alternative configuration path as the argument to init, otherwise it will use the default of
- The configuration for the server is based on
sentry.conf.server, which contains a basic Django project configuration, as well as the default Sentry configuration values.
- Sentry provides an easy way to run migrations on the database on version upgrades.
Before running it for the first time you’ll need to make sure you’ve created the database.
- Once done, you can create the initial schema using the
- Next up you’ll need to create the first user, which will act as a superuser
- All schema changes and database upgrades are handled via the upgrade command, and this is the first thing you’ll want to run when upgrading to future versions of Sentry.
Starting the Web Service
- Sentry provides a built-in webserver (powered by uWSGI) to get you off the ground quickly, also you can setup Sentry as WSGI application, in that case skip to section Running Sentry as WSGI application.
Start Builtin Webserver
- A large amount of Sentry’s work is managed via background workers.
- These need run in addition to the web service workers
- See Asynchronous Workers for more details on configuring workers.
Start Cron Process
- Sentry also needs a cron process which is called
- You should now be able to test the web service by visiting http://localhost:9000.
Setup a Reverse Proxy
- By default, Sentry runs on port 9000. Even if you change this, under normal conditions you won’t be able to bind to port 80.
To get around this (and to avoid running Sentry as a privileged user, which you shouldn’t), we recommend you setup a simple web proxy.
- You’ll use the builtin HttpProxyModule within Nginx to handle proxying:
To know more Information refer official documents.