Update Docs explaining keyring usage

[Vad1mo]

We are using a keyring and secret storage strategy: it woul de greate if we could document and explain that to the user in the documentation

Reference:

          @qcserestipy the examples are great, do you think we can get them out of the PR into general docs? e.g. manpages, so that users can find them later too..

Related to #387

[qcserestipy]

What do you think about a static site generator such as hugo? Or are there better choices?

[Vad1mo]

Generally Hugo is good.

I think in that case we would be better off, if the cli docs would be embedded in the goharbor.io main site.

Less maintenance, and one place for all.Just like we did with the man-docs, maybe we can extend or reuse that PR. goharbor/website#580

[qcserestipy]

@Vad1mo @Althaf66
Is the doc-harborcli branch still being actively worked on? If not, I’d be happy to take over and finalize the changes. Alternatively, I can wait for it to be merged before adding my documentation updates. Let me know what works best for you!

[Vad1mo]

@Vad1mo @Althaf66
Is the doc-harborcli branch still being actively worked on? If not, I’d be happy to take over and finalize the changes. Alternatively, I can wait for it to be merged before adding my documentation updates. Let me know what works best for you!

Not actively worked on. Branch will be merged when cli becomes GA.

So go ahead.

[qcserestipy]

I opened this PR: goharbor/website#645

[qcserestipy]

#415 and #418 have shown confusion happened, because the docs were not up to date. I will create a PR that will add necessary info to the README until the docs on the website is merged @Vad1mo