Some Improvement on the UI and backend : verson, links, relative path... etc

[abd3-13]

Hey @eznix86

Nice work, liked it, span it up immediately, Nice , so here comes my itch, what is the image made of, de-imaged it...
Then i started to work on adopting it to my own ngnix container, i have to serve multiple site with folder (/SPFT/, /CyberChef/ etc) with one port only or non subpath using different ports.

i came to issues and had to do some changes, like absolute path to relative path ("/..." to "./....") .

Improvements:

It would be nice if there is a version and GitHub link on the UI (maybe on the bottom footer, or the sidebar bottom footer).
For the version also add it on the index.html meta tag or response from url request (like ip:port/version),

Changes i made:
href="/container-hub.svg" >> href="./container-hub.svg"
src="/assets/index-nrVgH3xk.js" >> src="./assets/index-nrVgH3xk.js"
href="/assets/index-tn0RQdqM.css" >> href="./assets/index-tn0RQdqM.css"
fetch("/sources.json") >> fetch("./sources.json")
and nginx location block changes for the proxy to the registry link

[eznix86]

Thanks for opening this, issue.

Let me break it down for future self

• add a version of the project to the UI and Github link
• Include the version of the app on the html meta tag (not sure what you mean by url request)
• Add a documentation on how to de-image or have a convenient script in cases where it is behind another nginx

Is it like you described ?

I think for the 3rd item, you can contribute a documentation or make a script out of it. Let me know if you have one already there.

Also note that v1.x will not support pure html, it will be just a pure go binary later. The reason are here: #28

TLDR;

The project works great when you have low count of repositories and image, when you have a medium size to big registry. This is where it is taking all the resources of your browser. It is reliant on your browser and connection speed. The go implementation will do proper caching and and synchronization, since it is not in the browser anymore, the data is fetched once, and mostly cached on the backend side.