Cloudron Forum

said in CCAI : Cloudron Custom App Installer: @timconsidine Thank you for your work on this. It really leverages Cloudron's capabilities and helps make more applications deployable using Cloudron. Feedback: Edit /app/data/config.json with your Cloudron URL and a NEW Long-Lived Token. This part is a bit confusing for me. Let me show why: We create token 1 when we first install CCAI to access our Cloudron. We create token 2 when we install our first application, Application A. After our first application installation is completed, we are asked to update its token, so we create token 3 Then we might need to install an additional app, Application B. So we launch the CCAI on our local machine and ... create token 4? Also: Should the tokens be read-only or read and write? Also: Could we please also include a pretty icon for that specific application so we have one readily available instead of the generic cloudron one in our panel? Perhaps that could be included inline with the apps list on CCAI. As that list grows, it might help people find the ones they want more quickly, too.

@o1lab it's understandable in this economy. I only have two real requests for your team: 2FA / MFA needs to be one of those enterprise features you give to the community. It is becoming trivial to use tools like Opus 4.6 to find vulnerabilities in open source code and exploit it. You need to come up with a plan for the small business self hosted users. I want to support your product development but I don't need you to host it. I hope you guys seriously consider unlocking a "Community Plus" option.

I've put up a Github for a Filestash Cloudron app incase you guys wanna check it out: https://github.com/stalecontext/filestash-cloudron-app Let me know if there are any quirks. I didn't get mine fully set up yet

Funkwhale now on CustomAppGateway, alongside Indiekit

Funkwhale and Indict on CustomAppGateway [image: 1770657210667-screenshot-2026-02-09-at-17.13.16-resized.png]

@timconsidine said in Update on community packages: So, making sure I understand it correctly, for a CustomApp, the packager really just needs to add CloudronVersions.json to their repo (in addition to CloudronManifest.json, Dockerfile etc.) ? Neat ! Yes, correct. cloudron versions add simply creates CloudronVersions.json with the current manifest and current build information. Hopefully, it's all as obvious as I am making it sound From the installation point of view, the repo can be closed, docker image can be private. Only the CloudronVersions.json has to be public. I have added two new fields on the manifest - packagerName and packagerUrl. Going forward, the icon in manifest will be deprecated. We will use iconUrl instead. You said in a separate post you would defer the question of a catalogue of custom apps : is that still the thinking ? Yes, let's think about how people discover these versions files once we have released this.

Fixed - https://git.cloudron.io/platform/box/-/commit/1ce5fcafd908c8362f57a7f6c1955591542bd895

new package version has this fixed

Hello @jadudm Always happy to help.

Hello @hakunamatata Great find. We should still look into that. Thanks to the details I now have an approach to reproduce this issue.

released v0.0.6 plugin installation fixed for installing from local (just download from marketplace and then install the local plugin package file) Investigating the direct marketplace link