[docker] Parameterize Docker image for SSL + HTTPS

[olemis]

Adding SSL+HTTPS requires editing nginx.conf . Provide a way to do the same by providing a parameter to the image at run time.

• Image entry point
• Image CLI parameters for SSL + HTTPS
• Option to rely on Let's Encrypt during the process

[gz-c]

Is it possible to use let's encrypt for this

[olemis]

I guess so, should we offer the option in entry point or somehow . @stdevNorge can tell better.

[stdevYuniers]

Task Option to rely on Let's Encrypt during the process can't be done on image build because Let's Encrypts made checks when a certificate is generated. It must done on start up process or manual exec of an user.

[olemis]

Some resources :

• https://medium.com/@pentacent/nginx-and-lets-encrypt-with-docker-in-less-than-5-minutes-b4b8a60d3a71
• https://community.letsencrypt.org/t/tutorial-how-to-automate-lets-encrypt-using-docker-and-nginx/49917
• https://www.reddit.com/r/selfhosted/comments/9gr5xp/traefik_dockerletsencrypt_guide/
• https://medium.com/@joshuaavalon/setup-traefik-step-by-step-406792afe9b2
• https://www.humankode.com/ssl/how-to-set-up-free-ssl-certificates-from-lets-encrypt-using-docker-and-nginx

[gz-c]

@iketheadore Do you have any comment on this issue

[gz-c]

I think SSL/HTTPS is handled at a different layer than inside the docker container, and is out of scope for this project

[olemis]

sometimes it's handled by the load balance software ... but the fact is that the Docker image is derived from nginx:alpine , so the instructions in aforementioned article (section Set up Your Production Site to Run in a Nginx Docker Container) apply.

[olemis]

when a single web wallet node is launched there is no load balance proxy , and SSL certificate has to be configured directly through the nginx daemon running inside the Docker container .