You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 10, 2025. It is now read-only.
feat: [#21] implement complete HTTPS automation with self-signed certificates
- Enable HTTPS by default in deployment (ENABLE_HTTPS=true)
- Fix Docker Compose SSL certificate volume mappings:
- Mount /var/lib/torrust/proxy/certs to /etc/ssl/certs (was incorrectly mapped to dhparam)
- Mount /var/lib/torrust/proxy/private to /etc/ssl/private
- Move dhparam to /etc/ssl/dhparam to avoid conflicts
- Fix nginx HTTPS template variable escaping for envsubst:
- Replace all nginx variables () with ${DOLLAR}var to prevent envsubst processing
- Ensures proper nginx variable substitution in generated config
- Update deployment script for streamlined SSL certificate generation:
- Generate 10-year self-signed certificates directly on VM using openssl
- Switch domain from tracker-demo.local to test.local for consistency
- Remove complex container-based certificate generation (chicken-egg problem)
- Add comprehensive HTTPS connection info with /etc/hosts instructions
- Implement complete twelve-factor deployment workflow:
- Infrastructure provisioning (make infra-apply)
- Application deployment with HTTPS (make app-deploy)
- Health validation and connection info display
Deployment now provides both HTTP and HTTPS endpoints:
- HTTP: tracker.test.local, grafana.test.local (via nginx proxy)
- HTTPS: Same domains with 10-year self-signed certificates
- Direct access: VM IP for debugging/monitoring
Resolves certificate chicken-egg problem by generating certificates on host
before container startup, enabling automated HTTPS deployment without manual steps.
0 commit comments