Cloudron Forum

Right, that makes sense!

Thanks for reporting, fixed - https://git.cloudron.io/platform/box/-/commit/dcfb4d0832cd336fd9d46b0f9dd38f65dd5ae981

Thank you, that gave me something to work through!

@joseph said: This might be an excellent feature for the new webmail app, no? Just read about it, I will post it as a feature request there, thanks!

@justjulian said: @ekevu123 Thanks for this fine piece of software and your dedication towards it! Also thank you for making it available via Cloudron. Here a couple of things that would help me a lot: Add an option to add multi-language support for meeting type name and description (which is then controlled by the global language setting on the user side) Give the user the option to choose between several meeting options when booking: In-Person, Video Call Solution A, Video Call Solution B, etc. Let's say I want to offer two video call options to my clients so they choose based on their needs - either MS Teams because maybe they already have a Teams account and it integrates nicely into their workflow or for the more data-privacy aware clients Opentalk. That would put them in charge with which meeting platform they want to share their data with. Regarding the In-Person option above: That would then also need a location that I could enter, like an office address. And, for me personally a highlight would be, integration with Opentalk: https://docs.opentalk.eu/26.2/user/en/technical-documentation/rest-api/ Thank you, I'll take these! I have just finished a series of bug fixes and maintenance upgrades. The next feature update should concern video integration, so I will also see if Opentalk can be integrated.

@fbartels said: @joseph That is it (source: I just tried it myself and directly deleted the app again) Thank you, who would have thought ... I think some better error messages would be good to help the user understand what the issue is. @jdaviescoates said: @ekevu123 hasn't this just been added to the official app store? Not sure it needs to be in both? It apparently was added, I was never notified of that ... that's better then! Does that mean we don't need the cloudron versions file anymore, assuming any Cloudron user would prefer the app store install over the manual community package?

Yes, we used to have this, and I think/ hope they'll be back (along with other improvements) in the next release, see this thread https://forum.cloudron.io/post/117521

Great suggestion, this is implemented now for next version with https://git.cloudron.io/platform/box/-/commit/0223d50bf9f6bc01f53a75815dbe86f4cb5acb86

Hello @ekevu123 I understand the request but in my opinion adding "advanced" sections to the Cloudron dashboard will only lead to issues. Someone who is less skilled will see the button and use it. "Don't press the red button, it will wipe the DB server!" "Oh! A red button!" In your case, since you still need to use the terminal anyway, why not use the cloudron cli directly and have a bash alias ready to execute the interactive DB shell directly for an app? This would even reduce your time spend getting there even further. Instead of your mention steps 1>4 or future 3-dot sub menu, moving the mouse, clicking moving again yada yada, one command from the local shell, and you got what you need. For example: cloudron exec --tty --app $APPID -- sh -c 'mysql --user=${CLOUDRON_MYSQL_USERNAME} --password=${CLOUDRON_MYSQL_PASSWORD} --host=${CLOUDRON_MYSQL_HOST} ${CLOUDRON_MYSQL_DATABASE}'

This is tracked at https://forum.cloudron.io/topic/15683/add-database-terminal-shortcut . Thanks for opening that @ekevu123

Okay, thank you!

@ekevu123 great report. Fixed in https://git.cloudron.io/platform/box/-/commit/c7b2e4d95e3ca00924d3ad11781303b479d787d8

Both. I want to understand if both are correct programmatically, but I can't test them against having an existing docker image, because I find that counter-intuitive - why would I build the docker image before knowing if everything is correct?

Fair enough - mine seems to be working fine, though, since I rewrote my test script, so I guess I triggered it myself on my end.

Fixed for next release with https://git.cloudron.io/platform/box/-/commit/c9547cbdb8372728efbdcb6424497e0d421c08e8

I have put in a fix now to adjust the java heap memory dynamically. Hopefully that works.

Hello @ekevu123 Disabling is not actually disabling, but more disabling a custom override of the default which is 300 seconds.