Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Allow hiding the history feature to reduce complexity of the user interface #358

Closed
lukengda opened this issue Feb 24, 2024 · 0 comments · Fixed by #362
Closed

Comments

@lukengda
Copy link
Contributor

lukengda commented Feb 24, 2024

Is your feature request related to a problem? Please describe.
I would like to use docker-registry-ui to inform users about the available tags for our images. The users of this interface are not interested in the technical backgrounds how it works and I worry that it would confuse or overwhelm them.

Just from the eyes of a non-maintainer or a less container-familiar admin, I think it has too much in-depth info having the non-descriptive layers and thinking it is required to get the Dockerfile or something else.

Describe the solution you'd like
Therefore, I propose to add a new optional feature toggle "HIDE_TAG_HISTORY" to hide the tag history, similar to "SHOW_CONTENT_DIGEST".

Describe alternatives you've considered
I thought about reducing the information in the tag history view itself. But it would be more fitting to have a details view to see the information like Env, Volumes, Entrypoint, etc. just for the topmost, latest layer in a different view then history.

Additional context
I have prepared a commit that introduces this feature. Shall i just open the PR to discuss the diff?

I would also like to add the option to customize the title for the browser tab and in the toolbar. Would you be open for another PR that adds this?

Thanks anyway for the project. It is very simple to work with!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant