Change Details

Ideally, we should serve static files from nginx, but the container doesn't contain a nginx instance and we don't have access to those files. Proxy configuration is fairly standard, but tweaked to ensure compatibility with Jenkins CLI in HTTP connection mode. **References** - https://jenkins.io/doc/book/managing/cli/ - https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx

Provision vhost and Let's encrypt include snippet to Proxy configuration is fairly standard, but tweaked to ensure compatibility with Jenkins CLI in HTTP connection mode. The docker_containers pillar entry format is switched from a list to a dictionary, to allow to store metadata like domain or port. **Area for improvement** Ideally, we should serve static files from nginx, but the container doesn't contain a nginx instance and we don't have access to those files. **References** - https://jenkins.io/doc/book/managing/cli/ - https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx

Provision vhost and Let's encrypt include snippet to Proxy configuration is fairly standard, but tweaked to ensure compatibility with Jenkins CLI in HTTP connection mode. The docker_containers pillar entry format is switched from a list to a dictionary, to allow to store metadata like domain or port. **Area for improvement** Ideally, we should serve static files from nginx, but the container doesn't contain a nginx instance and we don't have access to those files. Proxy configuration is fairly standard, but tweaked to ensure compatibility with Jenkins CLI in HTTP connection mode. **References** - https://jenkins.io/doc/book/managing/cli/ - https://wiki.jenkins.io/display/JENKINS/Running+Jenkins+behind+Nginx