parabuzzle / craneoperator

Gives you a simple web interface for browsing around a Docker Registry
https://hub.docker.com/r/parabuzzle/craneoperator
MIT License
127 stars 32 forks source link

running behind reverse proxy #43

Open xelalexv opened 7 years ago

xelalexv commented 7 years ago

I'm deploying craneoperator into a Kubernetes cluster, and would like to use it through service proxy (in essence a reverse proxy), i.e. I'm accessing craneoperator via this URL:

https://{k8s API endpoint}/api/v1/namespaces/registry/services/registry-ui/proxy

That gives me the start page of craneoperator, but URL in browser changes to https://{k8s API endpoint}/containers, which of course doesn't work. Anything that can be done to make it work behind a reverse proxy?

michaelburn commented 6 years ago

I'm also interested in deploying craneoperator behind a reverse proxy. I would like to use nginx. Is this possible?

parabuzzle commented 6 years ago

The problem is URI relocation of underlying assets. I'll look into making that URI configurable.

czeigler commented 5 years ago

I would like this feature too!

xoleja01 commented 3 years ago

Hi, I would like this feature too. We need it to run under /gui location . Now it just creates empty page

danielriddell21 commented 3 years ago

@parabuzzle Any update on if this is going to be implemented

danielriddell21 commented 3 years ago

I have uploaded my own version with relative paths here: https://hub.docker.com/r/memologyserver/craneoperator I used PauloFerreira25 branch