configuration-env
Configure mjr.wtf safely via environment variables and .env files.
When & Why to Use This Skill
This Claude skill streamlines the setup and management of the mjr.wtf project by automating the configuration of environment variables and .env files. It ensures that critical parameters for databases, authentication, and security are correctly implemented, reducing manual errors and enhancing deployment security.
Use Cases
- Initial Environment Setup: Automatically generate and populate .env files from .env.example templates to jumpstart local or production development for mjr.wtf.
- Security Hardening: Configure production-specific security settings such as SECURE_COOKIES, ALLOWED_ORIGINS, and METRICS_AUTH_ENABLED to protect the application from unauthorized access.
- Database & Auth Integration: Efficiently manage DATABASE_URL paths and bearer tokens (AUTH_TOKENS) to ensure seamless connectivity and secure API authentication.
- CI/CD Pipeline Integration: Use the skill within automated workflows to validate or update environment configurations during deployment phases.
| name | configuration-env |
|---|---|
| description | Configure mjr.wtf safely via environment variables and .env files. |
| license | MIT |
| compatibility | Requires bash, git, and Go tooling. |
| repo | mjrwtf |
| runner | github-copilot-cli |
| version | 1.1 |
| allowed-tools | Bash(git:*) Bash(make:*) Bash(go:*) Read |
Primary references
.env.example(template)- README “Configuration” + “Authentication”
Core variables
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 links
Security-sensitive settings
SECURE_COOKIES=truein production behind HTTPS.ALLOWED_ORIGINS: set explicit origins in production.METRICS_AUTH_ENABLED=trueif/metricsshould not be public.