@girish Perfect thanks!
AppDev
Cloudron App Packagers
Private
Posts
-
Feature request: rsync -
Bridges - impossible to edit? -
Only able to select "Backups of automatic updates: Yes" when setting up a new site. Aha - it's in the Content menu@jdaviescoates yeah, it's not good. The UI will change in the coming releases. We will be moving away from dialogs into views (i.e full pages). The dialogs were primarily because of our old dashboard design. When we move to views, we will avoid this whole set up where we have 3 dialogs and we have to remember where to find which settings.
-
Tymeslot - Better Meeting Scheduling than cal.com@ekevu123 congratulations and thank you for doing this.
Will look further into it when back to a desk(top). -
Custom Haraka Plugin Support for the Mail Addon@CaeruleusAqua are you asking about custom bcc feature or custom haraka plugin? Custom haraka plugins won't be supported, this is not on the roadmap. Bcc feature might be. For 9.2, it will be primarily a mail feature release.
-
Update on community packagesStubborn dog-with-a-bone that I am, I did more research, and hopefully this can put to bed my diversion of the thread (sorry), and maybe help others with a similar use case / workflow objective to mine :
- Forgejo (official Cloudron AppStore) provides standard git source code functionality AND it has a built-in container registry functionality
- so no need to consider changes to the official docker registry app for public pulls
- forgejo supports private and public repos (which git.cloudron.io does not)
- forgejo supports public image pulls (like hub.docker.com) but also multiple private containers (hub.docker.com only allows 1)
- I can uninstall docker registry app and gitea/gitlab apps, multiple used for segregating cloudron community work from closed app dev, using Forgejo organization instead.
So the answer for my bandwidth-limited brain of 1 app for (almost) everything seems to be Forgejo (available today, no dev work).
However, @girish made valuable comment that hosting container images is a disk/network usage risk. Even for a small dev footprint like mine, this could be critical (let alone Cloudron scale).
I need to think & test out, but maybe Forgejo actions can automate container push to hub.docker.com, and do automated cleanup in the instance. So from dev point of view it's a single answer (Forgejo) with CI/CD offloading disk/network risks to hub.docker.com (or whatever).
-
Update on community packages@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 :- A: community apps : git A plus Dockerhub
- B: other dev : git B plus private image registry
Apologies if my ambitions for combing have confused the picture/discussion.
-
Update on community packages@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.
-
-
Update on community packages@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.ioBut plan seems to break down without easy public docker image (2 registries is good for segregating but cumbersome in practice)
