BlogDocumentationDocsLog In

GlitchTip Installation Guide

GlitchTip can be run with Docker. We recommend Docker Compose or Heroku for smaller installations.

Docker Compose

Docker Compose is a simple way to run GlitchTip on a single server.

  1. Install Docker and Docker Compose. On Debian/Ubuntu this is sudo apt install docker-compose
  2. Copy docker-compose.sample.yml to your server as docker-compose.yml.
  3. Edit the environment section of docker-compose.yml. See Configuration.
  4. Start docker service docker-compose up -d now the service should be running on port 8000.

It's highly recommended to configure SSL next. Use nginx or preferred solution.

  • Install nginx. Ex: sudo apt install nginx.
  • (on Debian/Ubuntu) edit /etc/nginx/sites-enabled/default for example:
server {
    access_log  /var/log/nginx/access.log;

    location / {
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

This configuration will direct to port 8000 (the default GlitchTip docker compose port).


  1. Pull latest docker image docker-compose pull
  2. Restart docker-compose stop and docker-compose up -d

Database migrations will automatically happen.


Heroku is a simple environment suitable for deployments small to large.

  1. Create Heroku app: heroku apps:create <heroku-app-name>
  2. Create Postgres database heroku addons:create heroku-postgresql --app <heroku-app-name>
  3. Set SECRET_KEY and other environment variables heroku config:set SECRET_KEY=random_string -a glitchtip. See Configuration.
  4. Deploy Docker image
  • docker pull glitchtip/glitchtip
  • docker tag glitchtip/glitchtip<heroku-app-name>/web
  • heroku container:login
  • docker push<heroku-app-name>/web
  • heroku container:release web

For production environments, you will likely wish to deploy a worker dyno. This requires at least hobby tier dynos. This is necessary for notifications and more.

  1. Create Redis instance: heroku addons:create heroku-redis:hobby-dev
  2. docker tag glitchtip/glitchtip<heroku-app-name>/worker
  3. docker push<heroku-app-name>/worker
  4. heroku container:release worker

GlitchTip will detect being run as a worker dyno and automatically start a celery worker with integrated beat scheduler.

For very high traffic sites, you may wish to run multiple workers. Limit the beat servers to just 1. Create another Heroku role and set the environment variable SERVER_ROLE=worker.


  1. docker pull glitchtip/glitchtip
  2. docker tag glitchtip/glitchtip<heroku-app-name>/web
  3. docker push<heroku-app-name>/web
  4. heroku container:release web

If using a worker, run the same commands with worker instead of web.


Helm is a complex package manager for Kubernetes. It's suitable for high capacity servers. You should have an expert level of knowledge with Kubernetes before using Helm. Currently we do not publish them but you can find the chart itself here


Required environment variables:

  • SECRET_KEY set to any random string
  • EMAIL_URL SMTP string. See format examples here.
    • Alternatively you can use the Mailgun API by setting MAILGUN_API_KEY and MAILGUN_SENDER_DOMAIN. Set EMAIL_BACKEND to anymail.backends.mailgun.EmailBackend
  • DEFAULT_FROM_EMAIL Default from email address. Example
  • GLITCHTIP_DOMAIN Set to your doamin. Example:

Optional environment variables:

  • GLITCHTIP_MAX_EVENT_LIFE_DAYS (Default 90) Events and associated data older than this will be deleted from the database
  • REDIS_HOST Set redis host explicitely.
  • DATABASE_URL Set postgres connect string.