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 Pebble SSL testing environment and decide on pre-generated cert approach
- Created comprehensive Pebble testing environment with Docker Compose
- All SSL scripts implemented and deployed: ssl-setup.sh, ssl-validate-dns.sh, ssl-generate.sh, ssl-configure-nginx.sh, ssl-activate-renewal.sh, ssl-setup-local-dns.sh
- Two-phase nginx template system: nginx-http.conf.tpl (base) + nginx-https-extension.conf.tpl (HTTPS extension)
- Pebble ACME server running and accessible at https://192.168.122.92:14000/dir
- Nginx serving ACME challenges from /var/lib/torrust/certbot/webroot
- Fixed working tree deployment via rsync --filter=':- .gitignore' for local testing
- Created comprehensive SSL testing guide with manual validation steps
Architecture Decision: Switch to pre-generated test certificates approach
- Complexity of Pebble environment makes iteration slow
- Pre-generated certificates will enable faster testing of nginx HTTPS configuration
- Focus on SSL script workflow validation rather than certificate authority integration
- Keep Pebble environment for optional comprehensive integration testing
Next: Implement ssl-generate-test-certs.sh for simplified SSL testing workflow
0 commit comments