Cloudron App Packagers
@girish you're right.
I'll have to rethink strategy.
I was focussed on simplicity, single git platform and single image registry.
But I guess it's gonna have to be separate streams :
@girish does sharing creds / creating users gives full registry access ?
yes, this is why it works only for friends and trusted people.
Maybe I miss something, but cloudron docker registry app and community packages are completely different things/use cases.
community app is for sharing built images. You generally want to use a public registry like gcs, DO, dockerhub etc. If you want to use a private registry, this is possible if the end user adds the private registry on their server. The public cloud providers have registries which give tokens with read/write and all sorts of access control which can be used for this.
cloudron docker registry is just an app to store private docker images. sure, we can add a feature to make it support public images, but this is not on the roadmap. In general, selfhosting public docker registry is very expensive network wise and backup wise. GIven the size of docker images, you will quickly run out of network limits. This is why cloudron's own appstore images use dockerhub and is not selfhosted.
@girish does sharing creds / creating users gives full registry access ? Or a user (virtual or real) can be limited to certain repos?
—-
EDIT : the support for Community Apps is awesome.
Thank you again for doing this “non-priority” enhancement.
Totally ok with CloudronVersions.json living in source repo such as git.cloudron.io
But plan seems to break down without easy public docker image (2 registries is good for segregating but cumbersome in practice)
You already got it, but often proxyAuth is the simplest.
Through my CCAI --> CCAI-P --> CAG journey, I've used Docker Hub for public pulls, and my private registry for dev and non-community projects.
Maybe my bad, but I desperately hoped that Community apps would allow me one registry for minimum workflow / publish discrepancies. But seems not possible.
Not without dev work.
[made with cloudron custom mermaid app]
@jdaviescoates Pretty much, yes.
But it can be used for sharing with friends / sharing with people you trust though. Just give them a docker registry app password and they can put it in their cloudrons and then install via the versions file.
Right, the cloudron registry app can only host private packages. We can possibly look into adding support to make it a public registry as well, but afaik this is complicated. We need private push and public pulls - this is not implemented out of the box by the opensource registry project.
Thanks for reporting. Fixed - https://git.cloudron.io/platform/box/-/commit/8ef56c6d91684bf34b25071aca0b8d6658aadcc9
There's a conundrum rattling in my head.
cloudron build prompts for a registry.cloudron versions add does its workSo test of installing community app fails.
cloudron versions does not support cloudron-hosted registries ?Docs should also be clear that community app repo link should be open (publicly accessible), if it does not already do so.
