--- title: "Deploy GlitchTip Self-Hosted (Docker)" description: "Step-by-step guide to self-hosting GlitchTip with Docker Compose. " --- # Deploy GlitchTip Open source error tracking that's compatible with Sentry SDKs.
⭐ 3.0k stars 📜 MIT 🔴 Advanced ⏱ ~20 minutes
🚀 Deploy on DigitalOcean ($200 Free Credit)
## What You'll Get A fully working GlitchTip instance running on your server. Your data stays on your hardware — no third-party access, no usage limits, no surprise invoices. ## Prerequisites - A server with Docker and Docker Compose installed ([setup guide](/quick-start/choosing-a-server)) - A domain name pointed to your server (optional but recommended) - Basic terminal access (SSH) ## The Config Create a directory for GlitchTip and add this `docker-compose.yml`: ```yaml # ------------------------------------------------------------------------- # 🚀 Created and distributed by The AltStack # 🌍 https://thealtstack.com # ------------------------------------------------------------------------- version: '3.8' services: glitchtip: image: glitchtip/glitchtip:latest container_name: glitchtip restart: unless-stopped depends_on: - db - redis ports: - "8000:8000" environment: - DATABASE_URL=postgres://glitchtip:glitchtip@db:5432/glitchtip - REDIS_URL=redis://redis:6379 - SECRET_KEY=change_me_to_something_random - PORT=8000 db: image: postgres:14 container_name: glitchtip-db restart: unless-stopped environment: - POSTGRES_USER=glitchtip - POSTGRES_PASSWORD=glitchtip - POSTGRES_DB=glitchtip volumes: - glitchtip_db_data:/var/lib/postgresql/data redis: image: redis:alpine container_name: glitchtip-redis restart: unless-stopped volumes: glitchtip_db_data: ``` ## Let's Ship It ```bash # Create a directory mkdir -p /opt/glitchtip && cd /opt/glitchtip # Create the docker-compose.yml (paste the config above) nano docker-compose.yml # Pull images and start docker compose up -d # Watch the logs docker compose logs -f ``` ## Environment Variables | Variable | Default | Required | |---|---|---| | `DATABASE_URL` | `postgres://glitchtip:glitchtip@db:5432/glitchtip` | No | | `REDIS_URL` | `redis://redis:6379` | No | | `SECRET_KEY` | `change_me_to_something_random` | No | | `PORT` | `8000` | No | | `POSTGRES_USER` | `glitchtip` | No | | `POSTGRES_PASSWORD` | `glitchtip` | No | | `POSTGRES_DB` | `glitchtip` | No | ## Post-Deployment Checklist - [ ] Service is accessible on the configured port - [ ] Admin account created (if applicable) - [ ] Reverse proxy configured ([Caddy guide](/concepts/reverse-proxies)) - [ ] SSL/HTTPS working - [ ] Backup script set up ([backup guide](/concepts/backups)) - [ ] Uptime monitor added ([Uptime Kuma](/deploy/uptime-kuma)) ## The "I Broke It" Section **Container won't start?** ```bash docker compose logs glitchtip | tail -50 ``` **Port already in use?** ```bash # Find what's using the port lsof -i :PORT_NUMBER ``` **Need to start fresh?** ```bash docker compose down -v # ⚠️ This deletes volumes/data! docker compose up -d ``` ## Going Further - [GlitchTip on AltStack Directory](https://thealtstack.com/alternative-to/glitchtip) - [GlitchTip Self-Hosted Guide](https://thealtstack.com/self-hosted/glitchtip) - [Official Documentation](https://glitchtip.com) - [GitHub Repository](https://github.com/glitchtip/glitchtip)