Update docker-compose to use https

It is necesarry to update in dev branch docker-compose for https scenario.

Good sample is provided from @bravecobra - https://github.com/bravecobra/identityserver-ui

I would like to use http://127.0.0.1.xip.io - with https for development scenario as well - but currently it does not work properly on my machine - I need spend more time on this.

Currently this feature is blocker for next release, because I would like to provide support for docker as well and https is required. Any help/PR is really welcome. 👍 🚀

Thanks

[vpetkovic]

I think something along these lines could help and be a good start. Here’s the explanation of each container:

• nginx-proxy will route traffic to other containers by providing “VIRTUAL_HOST” environment variable.

• letsencrypt-nginx-proxy-companion will auto-generate valid SSL cert for virtual host. (Using self-signed certs might add complexity and additional config of nginx)

• nginx will run demo web server

   services:
       nginx-proxy:
           container_name: nginx-proxy
           ports:
               - "80:80"
               - "443:443"
           volumes:
               - /etc/nginx/certs
               - /etc/nginx/vhost.d
               - /usr/share/nginx/html
               - "/var/run/docker.sock:/tmp/docker.sock:ro"
           image: jwilder/nginx-proxy
       
       letsencrypt-nginx-proxy-companion:
           container_name: nginx-proxy-letsencrypt
           volumes:
               - "/var/run/docker.sock:/var/run/docker.sock:ro"
           environment:
               - DEFAULT_EMAIL=PUTYOUREMAILHERE
           image: jrcs/letsencrypt-nginx-proxy-companion
       
       nginx:
           container_name: nginx
           environment:
               - VIRTUAL_HOST=127.0.0.1.xip.io
               - LETSENCRYPT_HOST=127.0.0.1.xip.io
           image: nginx
  

This part is not directly related to https but it is related to nginx (some might’ve experienced it) as it might cause 502 bad gateway when authorizing a client. It is due the fact that nginx doesn’t allow a large header content. To fix that nginx.conf needs to be modified and inlcude

    http{
        proxy_buffer_size   128k;
        proxy_buffers   4 256k;
        proxy_busy_buffers_size   256k;
        large_client_header_buffers 4 16k;
    }

[skoruba]

Done - PR #657. Thanks for your help/suggestions.