Cloudron Forum

@Elephant thank you Will add it to the packaging list.

@MiroTalk thank you, that's a very clear response I don't have a clear view of whether I will need a Licence or not, but you have a generous offer so have signed up. Thank you

The Docker image is already packaged specifically for Cloudron and includes the CloudronManifest.json, so no additional manifest is required for installation when using the image. Feel free to add it to your custom installer if that’s useful for users, but everything needed is already bundled in the image itself. Repo is here: said in Fizzy on Cloudron - the Kanban tracking tool for issues and ideas by 37signals: Git: https://github.com/patattzel/fizzy-cloudron

This will take some time because it requires Mongo DB 8.x . Cloudron's mongodb was in 6.x but was just upgraded to 7.x in Cloudron 9.0.16 . Cloudron 9.1 will have mongodb 8.x . We can only move step by step because mongodb does not support jumping versions.

Hello @sebastienserre Did you checkout the other topic related to synology? https://forum.cloudron.io/tags/synology

Yep - it does. Stop & start didn't help, unfortunately.

Hello @potemkin_ai Since this is a rather unique issue, I assume this has something to do with how Cloudron streams this to the browser. This can be very hard to debug, and I would like to first ensure that a simple reboot does not solve the issue. If a reboot solves the issue, I can also deduce that this is some docker network issue and can then look deeper into it.

In general yes Pangolin could do something like that. But I don't think this will work without fiddling with Cloudron internals. Its probably best if this would be a feature of the Cloudron native vpn app.

I have revoked this package version to investigate further.

@joseph said in Add UnifiedPush settings in documentation: Maybe I am missing something but isn't that rule giving anon access to channels starting with 'up' from the upstream docs linked above: The topic names used by UnifiedPush all start with the up* prefix. @joseph said in Add UnifiedPush settings in documentation: Why should this be in default Cloudron package? I could be missing something and I'm not even using the app, but just because I'd guess most people would want UnifiedPush stuff on in an app that's all about getting notified about stuff.

Thanks @humptydumpty

@girish Running. Problem solved.

Hello @abo_shahad and welcome to the Cloudrom Forum @abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest): When updating GitLab via Cloudron, does it upgrade directly to the latest version (e.g. 17.4.2 → 18.8)? Since you are running GitLab version 17.4.2 this is the Cloudron package version 1.95.1. No. Cloudron does not skip from a current version to the latest since this could cause some major issues. You are ~40 versions behind, this means, you will have to update your GitLab app ~40 times. May I ask why your GitLab app is so far behind? Did you disable automatic updated for the app? @abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest): Or does Cloudron internally handle sequential version upgrades to satisfy GitLab’s upgrade path requirements? Yes. This is the case for all Cloudron apps. All apps need be updated sequentially. Also, if you did not know, each Cloudron app update goes through an automatic life-cycle test and a manual review process that ensures that each app update should cause no issues before it gets shipped to everyone. @abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest): I’m aware that on self-managed GitLab installations, skipping certain major versions is not recommended, so I want to make sure Cloudron’s packaging and migration process safely handles this. That is what Cloudron does for every app. The user, you, should not have to worry about app updates. And even if an app update fails, a quick backup restore to the backup created before the update saves you a lot of headaches. @abo_shahad said in GitLab upgrade path on Cloudron (17.4.2 → latest): Any clarification from the Cloudron team or users who’ve upgraded GitLab across major versions would be appreciated. Since the Cloudron GitLab https://git.cloudron.io/ is also running on Cloudron, we are doing the same GitLab app update as you are. If something were wrong, we would have this issue on our own hands immediately. If you have any more questions, please never hesitate to ask.

Hello @flamotte Can you please give feedback if my last assumption with the missing amount field in the invoice is correct or not?

@robi although I made it for ClouDNS, I guess it could be extended to others “DNS Steward” I would need to do some research as I only use ClouDNS and I would volunteer testers.

@humptydumpty Ooops, sorry, brain in dev mode on another project If you have ZM alpha in your CCAI-P, it means a previous catalogue was imported. You can remove the alpha config by going to File Manager and editing /app/data/apps-config.json. Remove the "block" for ZM Alpha (it probably won't work now anyway). To preserve the JSON integrity, ensure you delete the block including the enclosing {} braces, and the closing } brace is followed by a comma , unless it is the last in the list. This is a bit 'hacky' so will add a UI to CCAI-P so you can do it in browser more safely. About finding Cloudron Meilisearch in the catalogue : ooops, sorry ! no, it's not shared out yet - my bad but also note that during development, I changed the name of the app to "SRTD" (explanation in earlier messages in this topic) I will publish the repo tonight and add to CCAI so you can update master your CCAI-P from the master catalogue will post here when done