flakeguard/.env.test.example at main · thc1006/flakeguard · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
# Test Environment Variables
# Used by docker-compose.test.yml for E2E testing
# DO NOT use these values in production!

# Database (Test)
DATABASE_URL=postgresql://test_user:test_password@postgres-test:5432/flakeguard_test

# Redis (Test)
REDIS_URL=redis://redis-test:6379

# GitHub App (Test)
GITHUB_APP_ID=test-app-id
GITHUB_PRIVATE_KEY_GENERATE=true  # Will generate at runtime
GITHUB_WEBHOOK_SECRET=test-webhook-secret-12345

# Slack (Test)
SLACK_BOT_TOKEN=xoxb-test-slack-token
SLACK_SIGNING_SECRET=test-slack-signing-secret

# NextAuth (Test)
NEXTAUTH_URL=http://localhost:3000
NEXTAUTH_SECRET_GENERATE=true  # Will generate at runtime
GITHUB_CLIENT_ID=test-github-client-id
GITHUB_CLIENT_SECRET=test-github-client-secret

# API Configuration (Test)
API_URL=http://api-test:3001
INTERNAL_API_URL=http://api-test:3001

# Application (Test)
NODE_ENV=test
LOG_LEVEL=debug
ENABLE_METRICS=true
ENABLE_SWAGGER=true

# Worker Configuration (Test)
MAX_CONCURRENCY=2

# Network Ports (Test)
API_PORT=3001
WEB_PORT=3000
POSTGRES_PORT=5433
REDIS_PORT=6380
NGINX_PORT=8080
MOCKSERVER_PORT=1080

# Security Note:
# - Cryptographic keys are generated at runtime using docker/scripts/generate-test-keys.js
# - This prevents hardcoded secrets from being committed to version control
# - Test tokens and secrets use obvious fake values that won't trigger security scanners