Jones Magloire

Hello, thank you for your issue. Use `URL` instead of `REGISTRY_URL`. I'm sorry, it's a bit complicate to know when we should use `REGISTRY_URL` and when we should use `URL`......

Hi, thank you for your issue. I'm glad that you are using this project :smile: I don't know if I can remove dangling tags because this will break the pagination......

Hi, Thank you for your feature request :+1: I think this feature will not be available on `DELETE` queries :thinking:.

Hi, A quick fix for your issue is to force the use of the trailing slash (with a 301 redirect for example). I also use the project behind a reverse...

For nginx, the correct configuration is : ```nginx location /registry/ { proxy_pass http://docker-registry-ui/; } ``` I used relative path to bypass these kinds of issues.

Hi, thank you for your comment. I'm glad that you are using my project in a corporate environment :smile:. I chose neutral colors so that the interface could satisfy everyone....

> Do you have an idea of the way you could propose this feature? I think I will add some environment variables (again). > Maybe it can be crystal clear...

@pedrohdz I did some tests and `terminationGracePeriodSeconds` is not enough. As you can see in this image, the grace period starts after the SIGTERM signal, at this moment it's already...

That's cool, a timeout is definitively a good idea. I'm a bit worried on the impact on phrase queries, in the benchmark, it seems that they are a bit slower...

Travis is using `npm install` and not `npm update`, some packages should be outdated and are failing in the CI. You can push your updated package.json or force a package...