Cloudron Forum

FWIW, Dify.ai is licensed under a modified version of the Apache License 2.0 with additional conditions:- https://github.com/langgenius/dify/blob/main/LICENSE

@robi These were patches made to the openclaw package. I'd say best is you guys test what you are trying to do then we can make all moving parts work

Well done!

@girish apologies, I jumped the gun on that last post. You were right. I had a look at the box source code (src/scheduler.js, src/docker.js) and the manifest command IS respected by the scheduler. The php artisan schedule:run on my instance came from a custom crontab entry carried over when we migrated from a standalone install to Cloudron over 2 years ago. That entry must have slipped through unnoticed, but it explains everything. After removing it, the scheduler container (now suffixed -housekeeping instead of -crontab.0) correctly runs cron.sh: $ docker inspect --format '{{.Config.Cmd}}' 1af144bb-fbf4-434d-8edd-bb4b95c00ef5-housekeeping Cmd: [/bin/sh -c /app/pkg/cron.sh] Things are working correctly with cron.sh + gosu now I should have caught this sooner. In my defense (barely), the Cron tab of the app doesn't mention that commands run as root. I eventually found it in the documentation at the bottom of the Cron page. A small note in the Cron tab itself would probably help others avoid the same mistake. Cheers, JD

@charlesnw [image: 1773858777076-screenshot-2026-03-18-at-18.32.36-resized.png] you should invite some friends !

Is that recommened? Or should it be run on another VM and cross linked via the UI settings? I mean, I suppose its somewhat blast radius limited to the container. Is anyone running OpenTerminal (either on cloudron as a side car or on a remote server)?

I use the darkreader plugin for sites that don't have dark mode and have it set on a schedule. Sometimes it makes text hard to read as it gets the color inversion wrong, but overall it's pretty good. https://darkreader.org/ You can easily disable it for certain sites with a single click (marked in red). The on/off buttons are for the entire plugin. The "configure automation" is where you set the schedule. [image: 1773852264553-7703688b-119f-42df-a8b4-f54dac6f40b8-image.jpeg]

@stevespaw thanks for sharing!

@LoudLemur said: Strapi: Strapi (Node.js headless CMS) loves the latest Node 24, MongoDB 8, and Redis. Not true. Strapi dropped NoSQL DB Support. Link. @LoudLemur said: The Cloudron Strapi package runs with a read-only /app/code filesystem. This means the Content-Type Builder is permanently unusable in production mode, and there is no supported way to deploy custom content types to it. Schema files cannot be written via transfer, push, or direct filesystem access. The only partial workaround is: build content types locally in dev mode → use strapi transfer --exclude files to push to production. However this only works if the schemas already exist on the destination, which they cannot, making it a circular problem. This is not "because of running in read-only filesystem" - its by design. Link. To manage Collections or Content-Types, you always have to build in local dev setup and push the changes. For a Cloudron app that means building a new image, push it and update your app. No magic. (And for sure no complicated strapi transfer workaround needed....). Which, to be honest, IS ALWAYS a good idea, because you're messing with the Database... Even worse, a prod one in that case (Like Directus...) So, (just my opinion...) i'd rather use Strapi with a dev / staging cycle and have clear easy migrations instead of a "heart operation" with directus... sure you can develop your directus upgrade locally, but then the CI/CD turns into hell... (This is of course assuming you don't mean some small self-project or no business logic depends on it. If not - Directus may actually a good choice.)

@girish Thank you for explaining! It doesn't appear to be working that way for installs. I don't see any visual indicator for the Community App when installing it, nor on the app after it's installed. Here is the link to the versions file. https://raw.githubusercontent.com/sfeldkamp/cloudron-bluesky-pds/main/CloudronVersions.json Let me know if I should cross post this to support as a bug report (or elsewhere). I haven't tested whether "testing" prevents an automatic update from being discovered.

Without the DNS entry mail from cloudron ends up with ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@smtpcorp.com header.s=a1-4 header.b=38VpoA5C; dkim=pass header.i=@permamed.org header.s=s1004192 header.b=IvzZvAEF; dkim=permerror (no key for signature) header.i=@permamed.org header.s=cloudron-0d9262 header.b=cSc2yqyX; spf=pass (google.com: domain of bounce.3wqhqixyft3pua6=46muc2596w7f=34l98tc3oj4uzw@em1004192.permamed.org designates 158.120.86.203 as permitted sender) Once I add the entry I get ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@smtpcorp.com header.s=a1-4 header.b=hge5ICDL; dkim=pass header.i=@permamed.org header.s=s1004192 header.b=HnqT1ibh; dkim=pass header.i=@permamed.org header.s=cloudron-0d9262 header.b="bpPl/+t5"; spf=pass (google.com: domain of bounce.w5qkkdyfnaxsxb7=ojoiat7bxbcy=pc4cfvy7huru7n@em1004192.permamed.org designates 158.120.86.203 as permitted sender)

@nebulon I see. Ok this solves it for me. Yes build build left me spinning last week but I understood eventually

@girish yeah did found a solution, I only did recreate container before updating and it fixed the mysql issue.

@girish Thank you so much for adding this.

I changed nothing, but it is working today. I imagine what is happening is that the upstream storage drops connections occasionally and cloudron simply passes that on to the user instead of having a retry loop in the background. So, I still believe this functionality would benefit from being more robust, as before it would manage 20-50MB per go before drop, and if the thing was in a retry loop it would be able to get the archive out by just resuming downloads. I realise it is annoying having to deal with people who insist on unreliable storage... but it is what we have.

Hello @jamie_casper and welcome to the Cloudron Forum