Konrad Kleine
Konrad Kleine
> @kwk Cherry-picking [18f5b6a](https://github.com/nrnrnr/noweb/commit/18f5b6a3804f59aa5f0f50ab0196e262d6b8c168) would cover most of those. If you review commit-by-commit instead of looking at the total difference (as Github likes to present everything) I don't think there...
Right. The frontend currently can handle Kerberos authentication and has no notion of authorization. It is planned though. I have an out of the box registry setup with token authorization...
@guruvan thank you. Please be more specific about what your idea is. The title says "paginate" while the rest of the feature request talks about convenient views (e.g. tree views)....
We can surely talk about pagination in the list of repos or tags, but please specify exactly what you're aiming at. I see more problems with a tree view than...
@guruvan As much as I would like to implement repository pagination in the frontend, there currently is an [issue with the docker-registry itself](https://github.com/docker/docker-registry/issues/987) that needs to be clarified first.
No, this is not configurable (yet) but don't hesitate to code something and create a PR. We can discus it then. The correct suffix is `#/repositories` not `/registry`. This hashtag...
You are right, requests are made to the frontend server's `/v1/...` route (see [registry-services.js](https://github.com/kwk/docker-registry-frontend/blob/master/app/scripts/services/registry-services.js)). The frontend's Apache Server then routes this request to the registry (see [apache-site.conf](https://github.com/kwk/docker-registry-frontend/blob/master/apache-site.conf#L29)). Please see [my...
Thank you for your feedback. How would you like to see this implemented? Please elaborate a bit so we are able to break this down into smaller steps?
Hi @jainishshah17 . Thank you for reporting this issue but please be more specifc about it though. How exactly is your private repo secured with username and password? Is it...