Developing with HTTPS in Containers
HTTPS is the new black. In production, you'll likely terminate HTTPS at the load balancer. But how do you develop HTTPS content inside Docker containers? Do you just drop back to HTTP and assume it'll work out? Do you drop the Docker part until you commit? How do you we get the browser to trust the self-signed certificates inside Docker containers? Let's dive deep into certificate trust, how Linux stores certificates, and how web servers use certificates. With that knowledge in place, let's build up Docker containers for both development (self-signed) work, and containers that have real, trusted certificates should you choose a Layer-4 load balancer in production.
You may also be interested in
Containers have become integral to every phase in the lifecycle of application development. Production grade orchestration tools such as Kubernetes...