4e: Dual-env TrapFall projects + DSN routing for Rungu/CIRA

[ajianaz]

Parent: #234 · Blocked by: #248

Scope

Set up 4 separate TrapFall projects for dual-environment tracking, with DSN routing configuration in both Rungu and CIRA.

TrapFall Projects

Project	Slug	DSN Path	Purpose
rungu-prod	rungu-production	/api/rungu-prod/envelope/	Production errors
rungu-dev	rungu-development	/api/rungu-dev/envelope/	Dev/staging errors
cira-prod	cira-production	/api/cira-prod/envelope/	Production errors
cira-dev	cira-development	/api/cira-dev/envelope/	Dev/staging errors

DSN Format

https://<trapfall-key>@trapfall.ajianaz.dev:9090/<project-slug>

Config (both Rungu and CIRA)

// In config, derive DSN from environment + app name:
impl SentryConfig {
    pub fn build_dsn(host: &str, app: &str, env: &str) -> String {
        format!("https://key@{}/{}-{}", host, app, env)
    }
}

Environment variable:

Env Var	Example Value
TRAPFALL_HOST	trapfall.ajianaz.dev:9090
APP_ENVIRONMENT	production or development
APP_NAME	rungu or cira

Dashboard Routing

• TrapFall dashboard already supports project filtering
• Tag events with environment=production|development for easy filtering
• Release tag: rungu@0.2.0 or cira@0.1.0

Tasks

• Create 4 projects in TrapFall instance (manual or seed migration)
• Add DSN builder function in Rungu config
• Add DSN builder function in CIRA config
• Document DSN setup in Rungu README
• Document DSN setup in CIRA README
• Verify: events from Rungu prod go to rungu-production project
• Verify: events from Rungu dev go to rungu-development project

Effort: ~1 hour

[ajianaz]

✅ Approach changed per user direction: DSN via raw ENV var (SENTRY_DSN) instead of programmatic builder. Each deployment sets its own DSN pointing to the correct TrapFall project. No code changes needed — just env config. See rungu#90, cira#94.