mit einem Klick
configuration-env
Configure mjr.wtf safely via environment variables and .env files.
Menü
Configure mjr.wtf safely via environment variables and .env files.
| name | configuration-env |
| description | Configure mjr.wtf safely via environment variables and .env files. |
| license | MIT |
| compatibility | Requires bash, git, and Go tooling. |
| metadata | {"repo":"mjrwtf","runner":"github-copilot-cli","version":1.1} |
| allowed-tools | Bash(git:*) Bash(make:*) Bash(go:*) Read |
.env.example (template)DATABASE_URL (required): SQLite database file path (e.g. ./database.db)AUTH_TOKENS (recommended): comma-separated bearer tokensAUTH_TOKEN (legacy): single bearer tokenBASE_URL (recommended): base URL used when constructing short linksSECURE_COOKIES=true in production behind HTTPS.ALLOWED_ORIGINS: set explicit origins in production.METRICS_AUTH_ENABLED=true if /metrics should not be public.Run mjr.wtf locally using Docker Compose (SQLite), including migrations, logs, and teardown.
Operate and validate mjr.wtf observability endpoints (/health, /metrics) and logging-related behavior. Use when adding metrics, changing auth around metrics, or debugging production-like issues.
Apply project-specific security and privacy guardrails (auth, headers, rate limiting, logging). Use when touching authentication, request handling, metrics exposure, or anything that could leak sensitive data.
Run, debug, and structure tests for this Go project (unit + integration), including generation prerequisites. Use when changing domain logic, repositories, HTTP handlers, or migrations.
Run and extend the end-to-end HTTP integration tests (SQLite in-memory) for mjr.wtf, covering auth, create/list/delete, redirects, and analytics. Use when changing handlers, middleware, or API contracts.
Run and troubleshoot project code generation (sqlc + templ).