Add glitchtip app (Sentry-compatible error tracking)

GlitchTip replaces the broken self-hosted Sentry setup: it runs with
only PostgreSQL (shared) and Redis, with no ClickHouse/Kafka/Snuba
dependency.  Includes web, worker+beat, and a one-shot migrate service.

Made-with: Cursor

Author: romkey

apps/glitchtip/.env.example

@@ -0,0 +1,30 @@
+# Public URL where GlitchTip is served — used in outbound links and emails
+GLITCHTIP_DOMAIN=https://glitchtip.example.com
+
+# Django secret key — generate with:
+#   python3 -c "import secrets; print(secrets.token_hex(50))"
+SECRET_KEY=
+
+# PostgreSQL connection (uses the shared postgresql service)
+DATABASE_URL=postgresql://glitchtip_user:password@postgresql:5432/glitchtip_db
+
+# Redis connection (uses the internal glitchtip-redis service)
+REDIS_URL=redis://glitchtip-redis:6379/0
+
+# Email
+DEFAULT_FROM_EMAIL=glitchtip@example.com
+EMAIL_URL=smtp://postfix:25
+
+# Port the web service listens on (default 8000)
+PORT=8000
+
+# Celery worker scaling: min,max concurrent workers
+CELERY_WORKER_AUTOSCALE=1,3
+CELERY_WORKER_MAX_TASKS_PER_CHILD=10000
+
+# Set to True to allow new user registrations; disable once initial accounts exist
+ENABLE_USER_REGISTRATION=False
+
+# Image versions
+#IMAGE_VERSION=latest
+#REDIS_IMAGE_VERSION=7-alpine

apps/glitchtip/.rsync-exclude

@@ -0,0 +1,89 @@
+# glitchtip
+
+[GlitchTip](https://glitchtip.com) is a Sentry-compatible self-hosted error
+tracking and uptime monitoring platform.  Unlike Sentry, it runs with only
+PostgreSQL and Redis — no ClickHouse, Kafka, or Snuba required.
+
+## Services
+
+| Service | Image | Role |
+|---|---|---|
+| `glitchtip` | `glitchtip/glitchtip` | Django web app + API |
+| `glitchtip-worker` | `glitchtip/glitchtip` | Celery worker + beat scheduler |
+| `glitchtip-redis` | `redis` | Celery broker and cache |
+| `glitchtip-migrate` | `glitchtip/glitchtip` | One-shot database migration runner |
+
+## Networks
+
+| Network alias | Actual network | Purpose |
+|---|---|---|
+| `db` | `postgres-net` | Shared PostgreSQL |
+| `proxy` | `nginx-proxy-net` | Reverse proxy (nginx-proxy-manager) |
+| `mail` | `postfix-net` | Outbound email via shared postfix |
+| `redis` | `glitchtip-redis-net` | Internal Redis (glitchtip-redis only) |
+
+## First-time setup
+
+### 1. Create the database
+
+Connect to the shared PostgreSQL instance:
+
+```sql
+CREATE USER glitchtip_user WITH PASSWORD 'your-password';
+CREATE DATABASE glitchtip_db OWNER glitchtip_user;
+```
+
+### 2. Configure environment
+
+```sh
+cp .env.example .env
+```
+
+Edit `.env` and fill in at minimum:
+
+- `SECRET_KEY` — generate with:
+  ```sh
+  python3 -c "import secrets; print(secrets.token_hex(50))"
+  ```
+- `DATABASE_URL` — update the password to match what you set above
+- `GLITCHTIP_DOMAIN` — the public URL (e.g. `https://glitchtip.example.com`)
+- `DEFAULT_FROM_EMAIL` — sender address for alerts and invites
+
+### 3. Run migrations
+
+```sh
+docker compose run --rm glitchtip-migrate
+```
+
+### 4. Start
+
+```sh
+docker compose up -d
+```
+
+The `glitchtip-migrate` container will also run automatically on every
+`docker compose up`; Django migrations are idempotent so this is safe.
+
+### 5. Create the first superuser
+
+```sh
+docker compose exec glitchtip ./manage.py createsuperuser
+```
+
+Then log in at your `GLITCHTIP_DOMAIN` and create an organization and project.
+
+## SDK configuration
+
+Point your Sentry SDK at GlitchTip by replacing the DSN host.  GlitchTip
+issues DSNs in the same format as Sentry — copy the DSN from the project
+settings page.
+
+## Reverse proxy
+
+Configure nginx-proxy-manager to proxy `glitchtip.example.com` → `glitchtip:8000`.
+
+## Stopping safely
+
+```sh
+docker compose down
+```

apps/glitchtip/README.md

@@ -0,0 +1,85 @@
+services:
+  glitchtip-redis:
+    image: redis:${REDIS_IMAGE_VERSION:-7-alpine}
+    container_name: glitchtip-redis
+    hostname: glitchtip-redis
+    restart: unless-stopped
+    volumes:
+      - ../../lib/glitchtip/redis:/data
+    networks:
+      - redis
+    healthcheck:
+      test: ["CMD", "redis-cli", "ping"]
+      interval: 10s
+      timeout: 5s
+      retries: 5
+
+  glitchtip:
+    image: glitchtip/glitchtip:${IMAGE_VERSION:-latest}
+    container_name: glitchtip
+    hostname: glitchtip
+    restart: unless-stopped
+    volumes:
+      - ../../lib/glitchtip/uploads:/code/uploads
+    env_file:
+      - .env
+    networks:
+      - db
+      - proxy
+      - redis
+      - mail
+    depends_on:
+      glitchtip-redis:
+        condition: service_healthy
+    healthcheck:
+      test: ["CMD-SHELL", "curl -fSs http://localhost:8000/ || exit 1"]
+      interval: 30s
+      timeout: 10s
+      retries: 3
+      start_period: 40s
+
+  glitchtip-worker:
+    image: glitchtip/glitchtip:${IMAGE_VERSION:-latest}
+    container_name: glitchtip-worker
+    hostname: glitchtip-worker
+    restart: unless-stopped
+    command: ./bin/run-celery-with-beat.sh
+    volumes:
+      - ../../lib/glitchtip/uploads:/code/uploads
+    env_file:
+      - .env
+    networks:
+      - db
+      - redis
+      - mail
+    depends_on:
+      glitchtip-redis:
+        condition: service_healthy
+
+  glitchtip-migrate:
+    image: glitchtip/glitchtip:${IMAGE_VERSION:-latest}
+    container_name: glitchtip-migrate
+    hostname: glitchtip-migrate
+    restart: "no"
+    command: ./manage.py migrate
+    env_file:
+      - .env
+    networks:
+      - db
+      - redis
+    depends_on:
+      glitchtip-redis:
+        condition: service_healthy
+
+networks:
+  proxy:
+    external: true
+    name: nginx-proxy-net
+  db:
+    external: true
+    name: postgres-net
+  mail:
+    external: true
+    name: postfix-net
+  redis:
+    name: glitchtip-redis-net