fix(docker): standardize Docker Compose and environment configurations

[starbops]

Summary

This PR resolves inconsistencies between Docker Compose files and creates comprehensive environment configuration templates for all deployment scenarios.

🔧 Docker Compose Fixes

Consistency Issues Resolved:

• ✅ Fixed PostgreSQL image consistency (all environments now use postgres:17-alpine)
• ✅ Added network configuration to test environment with voidrunner-test network
• ✅ Resolved port conflicts by using different ports for test services (PostgreSQL: 5433, Redis: 6380)
• ✅ Converted hardcoded values in development file to environment variables with defaults
• ✅ Added resource limits to test services for consistency with other environments
• ✅ Fixed health check credentials to match environment configurations
• ✅ Standardized Redis configuration with environment variables across environments
• ✅ Added missing environment variables (EMBEDDED_WORKERS, SERVER_HOST, SERVER_PORT) to development
• ✅ Added POSTGRES_INITDB_ARGS to development and test environments for consistency
• ✅ Added explicit volume drivers to test environment

📝 Environment Template Updates

New Template Files:

• ✅ .env.example: Comprehensive template with all 100+ variables and detailed documentation
• ✅ .env.test.example: Test-specific configuration with test ports and optimized settings
• ✅ .env.production.example: Production template with security guidelines and checklist
• ✅ .gitignore: Updated to include new environment files (.env.test, .env.production)

Template Features:

• 📖 Comprehensive comments explaining each variable and environment usage
• 🔒 Security warnings and best practices for production deployments
• 🎯 Environment-specific examples and recommended values
• 📋 Production security checklist with 25+ verification points

🧪 Testing Results

All tests pass successfully with the new configuration:

• ✅ Code Quality: make fmt, make vet, make lint - All passed
• ✅ Unit Tests: make test-fast, make test - All 13 packages passed with good coverage
• ✅ Integration Tests: make test-integration - Comprehensive auth tests passed using updated test services
• ✅ Docker Compose Validation: All three compose files validated successfully
• ✅ Port Isolation: Test services (5433, 6380) run without conflicts with dev/prod (5432, 6379)

💡 Key Improvements

For Developers:

• All environments can run simultaneously without port conflicts
• Clear, comprehensive templates for setting up any environment
• Consistent patterns across all configuration files
• Better documentation and setup instructions

For Operations:

• Environment-specific optimizations (dev=debug, test=fast, prod=secure)
• Production security best practices documented
• Proper volume separation between environments
• Resource limits defined for all services

For CI/CD:

• Test environment uses separate ports and networks
• Integration tests validated with new Docker Compose configuration
• Environment variables properly templated for different deployment scenarios

📋 Files Changed

• docker-compose.dev.yml - Standardized environment variables and added missing configs
• docker-compose.test.yml - Fixed ports, added network, resource limits, and standardized config
• .env.example - Complete rewrite with comprehensive documentation
• .env.test.example - New test environment template
• .env.production.example - New production environment template with security guidelines
• .gitignore - Added new environment files

🔍 Breaking Changes

None. All changes are backward compatible and maintain existing functionality while fixing inconsistencies.

📖 Usage

For Development:

cp .env.example .env.dev
# Edit .env.dev with your preferences
docker-compose -f docker-compose.yml -f docker-compose.dev.yml up

For Testing:

cp .env.test.example .env.test
make services-start  # Uses ports 5433, 6380
make test-integration

For Production:

cp .env.production.example .env.production
# Review security checklist and configure properly
docker-compose up

🤖 Generated with Claude Code

[Copilot]

Pull Request Overview

This PR standardizes Docker Compose configurations and creates comprehensive environment templates to resolve inconsistencies across development, test, and production environments. The changes focus on configuration management, environment isolation, and deployment standardization.

• Standardized Docker Compose files with consistent PostgreSQL images, environment variables, and resource configurations
• Created comprehensive environment templates (.env.example, .env.test.example, .env.production.example) with detailed documentation and security guidelines
• Fixed port conflicts between environments by using separate ports for test services (5433 for PostgreSQL, 6380 for Redis)

Reviewed Changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docker-compose.test.yml	Added network configuration, resource limits, and updated ports to prevent conflicts with dev/prod environments
docker-compose.dev.yml	Converted hardcoded values to environment variables with defaults and added missing health checks
.env.test.example	New test environment template with optimized settings and separate ports
.env.production.example	New production template with comprehensive security guidelines and checklist
.env.example	Complete rewrite with detailed documentation, environment-specific examples, and comprehensive variable coverage

[Copilot]

The Alpine Linux version 3.22 may not exist or be stable. Consider using a more conservative version like alpine:3.19 or alpine:latest with a comment about version pinning strategy.

Suggested change

	EXECUTOR_BASH_IMAGE=alpine:3.22
	EXECUTOR_BASH_IMAGE=alpine:3.19 # Pin to a stable version; update as needed after testing