viewflow/seedkit / skills/django-seedkit
django-seedkit
FlaggedBootstrap a new Django project, or add components — auth (allauth, magic-link, axes, 2FA), payments (Stripe, dj-stripe), REST (django-modern-rest, django-bolt), Celery / Django Tasks, async views & WebSockets (ASGI, uvicorn worker, django-channels, channels-redis), Tailwind+DaisyUI, favicon, SEO meta tags + sitemap, HTML email templates, S3 storage, structlog, healthchecks, Docker, CI, deploy (VPS / Fly / GitHub-SSH), dbbackup, Sentry/Bugsink — to an existing Django codebase. Use whenever the user wants to scaffold Django, integrate a Django package, set up async / WebSockets, set up production deploys, wire CI/CD, or extend an existing Django project.
references/error-reporting.md
View on GitHub# Error reporting
Docs: <https://docs.sentry.io/platforms/python/integrations/django/> · <https://www.bugsink.com/docs/> · <https://glitchtip.com/documentation>
Sentry-protocol error tracker. Three backends share one SDK setup — only `SENTRY_DSN` differs.
## Install
```sh
uv add sentry-sdk
```
## Settings
Wire in `config/settings/production.py` (or single-file: gate on `not DEBUG`). Not `base.py` — a local/test run with `SENTRY_DSN` set would otherwise ship telemetry.
```python
SENTRY_DSN = env("SENTRY_DSN", default="")
if SENTRY_DSN:
import sentry_sdk
from sentry_sdk.integrations.django import DjangoIntegration
sentry_sdk.init(
dsn=SENTRY_DSN,
integrations=[DjangoIntegration()],
release=env("SENTRY_RELEASE", default=None),
# traces_sample_rate=0.1, # tracing — Sentry SaaS / GlitchTip only
)
```
PII / scrubbing — see `references/gdpr.md`.
## Background workers
The same `sentry_sdk.init` covers Celery worker processes because they load the same settings module. After deploy, run a task that raises and confirm it appears in the tracker.
## .env
```sh
SENTRY_DSN=
```
## .env.prod
```sh
SENTRY_DSN=<dsn>
```
`SENTRY_RELEASE` comes from the image, not `.env.prod` — the commit is known at
build time, not at run time. In the production Dockerfile's `prod` stage:
```dockerfile
ARG GIT_SHA=unknown
ENV SENTRY_RELEASE=${GIT_SHA}
```
and pass it from CI — in `references/deploy-github-ssh.md`, add to the
`docker/build-push-action` step:
```yaml
build-args: |
GIT_SHA=${{ github.sha }}
```
---
## Backend A: Bugsink (self-hosted, recommended)
### docker-compose.prod.yml
```yaml
services:
bugsink:
image: bugsink/bugsink:latest
restart: unless-stopped
environment:
SECRET_KEY: ${BUGSINK_SECRET_KEY}
CREATE_SUPERUSER: "admin:${BUGSINK_ADMIN_PASSWORD}"
BEHIND_HTTPS_PROXY: "true"
BASE_URL: https://bugsink.example.com
volumes:
- bugsink_data:/data
volumes:
bugsink_data:
```
Reverse-proxy `bugsink.example.com` → `bugsink:8000` in the Caddyfile. Open the UI, create a project, copy the DSN into `SENTRY_DSN`.
## Backend B: Sentry SaaS
Create a Django project at sentry.io (EU region available at signup), copy the DSN.
## Backend C: GlitchTip (self-hosted)
```yaml
services:
glitchtip-web:
image: glitchtip/glitchtip:latest
restart: unless-stopped
environment:
DATABASE_URL: postgres://glitchtip:${GLITCHTIP_DB_PASSWORD}@glitchtip-db:5432/glitchtip
SECRET_KEY: ${GLITCHTIP_SECRET_KEY}
REDIS_URL: redis://glitchtip-redis:6379/0
depends_on: [glitchtip-db, glitchtip-redis]
glitchtip-worker:
image: glitchtip/glitchtip:latest
command: ./bin/run-celery-with-beat.sh
restart: unless-stopped
environment: # GlitchTip's own config, not the app's
DATABASE_URL: postgres://glitchtip:${GLITCHTIP_DB_PASSWORD}@glitchtip-db:5432/glitchtip
SECRET_KEY: ${GLITCHTIP_SECRET_KEY}
REDIS_URL: redis://glitchtip-redis:6379/0
depends_on: [glitchtip-db, glitchtip-redis]
glitchtip-redis:
image: redis:8-alpine
restart: unless-stopped
# GlitchTip's Celery keys carry no TTL, so on the app's redis the
# `volatile-lru` maxmemory policy evicts the app's cache to hold them.
glitchtip-db:
image: postgres:16-alpine
environment:
POSTGRES_DB: glitchtip
POSTGRES_USER: glitchtip
POSTGRES_PASSWORD: ${GLITCHTIP_DB_PASSWORD}
volumes:
- glitchtip_pgdata:/var/lib/postgresql/data
volumes:
glitchtip_pgdata:
```
Reverse-proxy → `glitchtip-web:8000`.
---
## Release tracking
```dockerfile
ARG GIT_SHA=unknown
ENV GIT_SHA=${GIT_SHA}
```
```sh
docker build --build-arg GIT_SHA=$(git rev-parse --short HEAD) -t app .
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |