Cloudron Forum

@Jean-Henri it was a bug in the Cloudron integration. This is fixed now. We reverted the broken packages.

Our ci test pipeline succeeded now and the package update is out

New package with 3.0.1 is out now.

Pushed the package update now.

Thanks @CptPlastic & @nebulon for working through this. I've got mine up and running now.

Best,

Jon

@CptPlastic Cal.com is great and I am using both for different scenarios, but for some use cases I prefer Easy!Appointments in regards of the ease of use and simple handing for non-tech users.

This is what was updated in Cloudron

image.png

@shrey said in Using Mistral API seems broken on cloudron:

@nebulon Thanks!
Indeed, that was it.

RAM was set at 2GB. Whereas, it seems to require a min. of 5.5GB to function.

That's right, and if you can provide it with at least 8-16GB of RAM you will see a huge difference. These things are meant to consume large resources for now, but it's getting better.

@MiroTalk 👍
standard cloudron app installation.
efee5428-e018-4be1-abb3-241683f5ab28-image.png

We only update apps to the upstream versions which are marked as latest stable.

Thank You

We fixed the issue and the new package with typebot version 2.18.2 is out now

@BrutalBirdie yes, I think that needs to be fixed. Obviously, nothing is right/wrong, but this is just a convention to guide people and makes support simpler. The convention is:

If the app uses environment variables, just use env.sh pattern and expect people to add export keyword. A motivation for this is that in many app doc pages, they have export and people copy/paste it. If the app uses .env , dotenv and other styles, just use env. Same rationale as above. Use dot files in /app/data only for package internal files. Do not use for app files. For example, it would be htaccess and not .htaccess if needed in /app/data/ . But, we use .initialized since it's a package thing and not related to the app.

Any deviation from above is mostly just oversight...

It just took a while to come up but I stopped and started it waited and it seems to come up just fine...

Installed Stopped after it installed Started it and waited, came up just fine.

@shrey I have made the package a bit more robust now. Let me know if you can reproduce this again.