Support HTTPS for docker image about docker-registry-browser HOT 5 CLOSED

Got your point. It shouldn't be difficult to add HTTPS support as the used app server has built-in support for it. It's just about providing a way to enable it and configure the cert/key pair.

I'll see if I can find some time in the next days to give it a try.

from docker-registry-browser.

Thanks! It works fine.

from docker-registry-browser.

Hi @waldner,

it's best practice to not directly expose application-servers like the one I'm using in this project (puma) to clients. That's why the application itself does not support to configure TLS.

I would recommend using for example nginx as a reverse-proxy in front which does the TLS offloading and passes the requests to the application. You can simply run it as another docker container on the same host and link it to the docker-registry-browser container.

from docker-registry-browser.

While in general I agree with you, I was asking specifically about the docker image. It's not uncommon for many self-contained dockerized applications which run a web server or expose an HTTP API to offer an HTTPS option (either via docker environment variables or the application's own configuration file), to avoid having to spin extra containers just for that. Some examples that come to mind: elasticsearch, docker registry, gogs, rabbitmq, jenkins just to name a few I've used.
I think it's not difficult to implement and allow the user to enable it via some variables. If not, then of course I'll go with the reverse proxy setup (which is what I do already, after all).

from docker-registry-browser.

@waldner I managed to implement something now.

Please check the latest image and have a look at the updated README.

from docker-registry-browser.