@Lonkle How'd you do this? I'm running into issues as I have multiple Cloudron servers with custom apps and only the ability to configure a single docker registry

@girish said in Add a"Staff Choice" badge/filter to App Store apps: I don't want to be part of the decision-making of our end user. First off: im new here. Just discovered Cloudron a few weeks ago. Super impressed! And quite a nice community. And here goes my point: You are already part of the decision making. Or at least together with the community that votes for packages to get included. The App Store is already a curated selection But I can see the direction you are coming from. I mean in the end a feature like GH Stars would safe me 2 clicks, so I would say its definitely a nice-to-have and nothing more. Thanks for the good work!

and even object storage has options for a checksum based restore..

@joseph Good point. There is no exclude option in the filter settings. And because of new topics without tags, this idea is not helpful. Sorry.

@girish could you maybe give an update if you are considering adding this feature? We would really, really appriciate it!

@msbt got you, thanks! I don't believe Cloudron's auth is easily replaceable for the build-in apps and it's unlikely that it will be replaced one day - that means a lot of testing on top of the existing infrastructure.

A standalone, fully customizable PostgreSQL would be nice indeed, I have a use-case where the timescaledb extension is required, has anyone tried that before?

Vanity nameservers are now supported in https://git.cloudron.io/platform/box/-/commit/6aca198428bde8c189d0098270ffc05d5a352bab (expected in Cloudron 9.0)

@necrevistonnezr I was looking in the forum Thank you!

(From https://forum.cloudron.io/topic/13362/restoring-app-backup-improvements)

For the first one, I guess you are suggesting a real rsync between the existing files and the remote. I think the issue is that rsync itself relies on a remote rsync service. Cloudron's rsync is strictly speaking not rsync, more like "individual files are synced as opposed to tarball". Even with sshfs, one cannot know for sure if there is a remote rsync service running. The second one looks like it can be fixed . I will should split this post though

I could not find directly-accessible relevant specification or documentation for the token entry name other than what @joseph provided. The logo/icon seems also to be a case of different approach depending on which app you use - Some allow for manual upload/lookup of a logo, some offer to "submit" a logo suggestion to their list. There does not seem to have a standard / uniform specification for this - So tricky to solve.

Thanks for the initiative @humptydumpty Not sure @staff is the the right callout. They're busy making Cloudron great. There are many ways to do this, via WP, ESPO, or even from scratch via (lovable, v0, cursor, etc) AI building a bounty site from scratch in a few minutes deployable in the LAMP app. [If you have the expertise or time to learn, please do. Could be fun.] Similarly, the packaging can be quick started by AI systems to help get things started, as I've shown in another forum thread. Some instructions (templates, options, hints, tips) on the bounty site could tie all this together and await participants to drive sponsored apps to the app store for @staff to test and approve. Needs someone to host Needs someone to dev site Needs someone to manage listings from forum, (fun)ding & happiness Needs someone to create pkg templates Needs AppDev to package Who's in?

Great idea. Since we are rewriting those views currently, we will add such deeplinking support for tags and maybe just search in general.

check the forum on how folks did it with Google drive and the rclone config

That would be a very cool feature!

Yes, unless we actively track user activity in the dashboard, this is quite useless when that browser session had a still valid accessToken or OpenID session. Same goes for apps, only here the platform has even less control and no way to track unless we would inject some javascript, which we really shouldn't