Does not work behind proxy after last couple of commit

[utestinc]

Looks like inclusion of base href "/" broke it, so it can't be mounted as /fe/ on docker registry node
thanks!

[kwk]

Hi @utestinc. Thank you for reporting the issue and sorry for the inconvenience.

The <base href="/"> in app/index.html can be changed to your liking if you decide to build your own container (simply run docker build --tag="your-registry/yourname/yourfrontend:mybase" . from the root directory). All paths in the frontend are relative and refer to the base. You can basically change it to anything you wish including /fe/.

If it works for you we can maybe think of a way to configure the base at container runtime (e.g. by introducing a new env variable ENV_BASE_HREF). Please, give it a try, would you?

The W3C says:

The base element specifies a document-wide base URL for the purposes of resolving relative URLs, and a document-wide default browsing context name for the purposes of following hyperlinks.

I hope this helps.

[utestinc]

Hi @kwk,
I am using a workaround for now: Here is a snippet from the nginx config:
location /fe/ {
sub_filter 'base href="/"' 'base href="/fe/"';
sub_filter_once off;
proxy_set_header Accept-Encoding "";
proxy_pass http://docker-registry-frontend/;

If I get time I may look into adding runtime config as you mentioned, something like docker-registry-ui project.

[bpholt]

I tried the alternate base (<base href="/ui/">, in my case) and it seems to be working. It’s a little hard to tell for sure because of #53.

I also had to modify app-mode-services.js:8 because the request to app-mode.json had a leading /.

It isn’t clear to me how to introduce ENV_BASE_HREF or I’d send a pull request. Any suggestions?

[bpholt]

Since #53 has been fixed, everything seems to be working in my fork. @kwk, if you can suggest how to introduce ENV_BASE_HREF, I’ll try to implement it. In the meantime, if anyone wants to run the front-end on /ui/ feel free to use this branch in my fork or the image I published to the Hub.

[kwk]

@bpholt Please check to see how all the other ENV_... variables work and do it accordingly.

[calh]

I still couldn't get a /ui/ prefix to work behind my haproxy load balancer, even using @bpholt's image. Every endpoint call would return the index file for some reason.

I ended up just virtual hosting it on a separate domain from my registry, and it seems to work fine. Then to reduce my hops, I linked it directly to my registry like this:

docker run -d --restart=always --name registry_ui \
  --link registry:registry \
  -e ENV_DOCKER_REGISTRY_HOST=registry \
  -e ENV_DOCKER_REGISTRY_PORT=5000 \
  -p 8080:80 \
  konradkleine/docker-registry-frontend

But, I'd still like to find a more elegant solution than a separate subdomain if possible.

[Morriz]

I strongly favor your ENV_BASE_HREF solution, if that would fix our woes. Vhosting the app is silly, as it it should never be needed, only wanted