Mike Swanson
e3e95f8fa7
Some checks failed
Build and Test / Build Server (Linux) (push) Has been cancelled
Build and Test / Build Agent (Windows) (push) Has been cancelled
Build and Test / Security Audit (push) Has been cancelled
Build and Test / Build Summary (push) Has been cancelled
Run Tests / Test Server (push) Has been cancelled
Run Tests / Test Agent (push) Has been cancelled
Run Tests / Code Coverage (push) Has been cancelled
Run Tests / Lint and Format Check (push) Has been cancelled
Brings azcomputerguru/guru-connect up to the authoritative working copy that had been maintained in the claudetools monorepo: Phase 1 security and infrastructure (middleware, metrics, utils, token blacklist, deployment scripts, security audits) plus the native-remote-control integration spec. Preserves the repo .gitignore, .cargo, and server/static/downloads. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
# GuruConnect Server Configuration
|
|
|
|
# REQUIRED: JWT Secret for authentication token signing
|
|
# Generate a new secret with: openssl rand -base64 64
|
|
# CRITICAL: Change this before deploying to production!
|
|
JWT_SECRET=KfPrjjC3J6YMx9q1yjPxZAYkHLM2JdFy1XRxHJ9oPnw0NU3xH074ufHk7fj++e8BJEqRQ5k4zlWD+1iDwlLP4w==
|
|
|
|
# JWT token expiration in hours (default: 24)
|
|
JWT_EXPIRY_HOURS=24
|
|
|
|
# Database connection URL (PostgreSQL)
|
|
# Format: postgresql://username:password@host:port/database
|
|
DATABASE_URL=postgresql://guruconnect:password@172.16.3.30:5432/guruconnect
|
|
|
|
# Maximum database connections in pool
|
|
DATABASE_MAX_CONNECTIONS=10
|
|
|
|
# Server listen address and port
|
|
LISTEN_ADDR=0.0.0.0:3002
|
|
|
|
# Optional: API key for persistent agents
|
|
# If set, persistent agents must provide this key to connect
|
|
AGENT_API_KEY=
|
|
|
|
# Debug mode (enables verbose logging)
|
|
DEBUG=false
|
|
|
|
# SECURITY NOTES:
|
|
# 1. NEVER commit the actual .env file to git
|
|
# 2. Rotate JWT_SECRET regularly (every 90 days recommended)
|
|
# 3. Use a unique AGENT_API_KEY per deployment
|
|
# 4. Keep DATABASE_URL credentials secure
|
|
# 5. Set restrictive file permissions: chmod 600 .env
|