Cloudron Forum

Not too sure what to do with that list. So memory limits on Cloudron for apps are just the upper limit on when the app gets restarted. If any of your apps hit this limit, you will see a notification in Cloudron about the app getting restarted due to out-of-memory. Until you see this, it all looks fine and it seems your server just has more memory than the apps currently need.

so that instance is a shared instance, which means everyone using the demo is using the same admin user. The more people who are at any point trying it, the more likely it is that apps get uninstalled. Mostly the demo is to showcase Cloudron not so much the app itself.

The memory limit is really just the maxiumum upper limit for an app at which it gets restarted. The actual memory used by apps heavily depends on their software stack. Often app use runtimes like nodejs or ruby or such, where those runtimes have their own memory usage behavior. Maybe the server just does not have enough apps installed to with enough usage to exhaust that?

So currently one can set a title and a description, which both are publicly shown. I will make a change to allow the description to be markdown, that allows some better customization. We can also maybe add a custom icon rendered there, though I am not too sure how imporant that really is.

Further maybe instead of allowing it to be hosted by some other domain, which will need much more integration, like link generation in emails to the corresponding domain as well as DNS setup/certificates. Maybe allowing that page to be iframed is a good middleground?

This is fixed for next release.

Haven't tried it yet myself but I just saw https://vikunja.io/docs/openid/#users-must-log-in-before-they-can-be-assigned-to-tasks

If both those apps are installed and using the same disk, I can't quite see how filesystem operations would in any case impact how Grav is serving up files. On top of this, the Grav package is also using apache to serve up the files.

Yes this should work with most matrix clients, only Element X is known to not work, but the main official Element client works also.

Good catch, certainly something we should fix. I have created a work item in the project now https://git.cloudron.io/apps/calendar/-/work_items/38

Alright so after some debugging we found the root cause. The cookie was exceeding the max cookie size. We have reworked the logic now to not store as much info in the jwt cookie: https://git.cloudron.io/platform/box/-/commit/0cddd129e64ec062f13618bc9938c194023aeedf

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

do you see the same error messages or something else, also have you adjust the config manually somehow?

Oh that slipped through, we made yet another package release which at least has fixed this on my test instance. Sadly it is hard to test the app in an automated way since one needs residential IPs to do any useful testing.

that makes sense that it fails then. Issue here is that the webview has no real clue of what kind of process is running in the webterminal itself. So all that menu option really does is blindly pasting the hardcoded string into the tty. No clue on how to maybe fix this on some other level....

not exactly sure what "interactive shell" here means in your case, but this command line for postgres is really just a regular linux shell commandline. If elixir runs some other "shell" like repl, than this wil likely not work at all. Though why cant you just open a second terminal into the app in a new browser tab to run postgres cli?

We have cut a new release for invidious updating it to latest master.

haven't seen this in my production instance, especially strange about the db schema issues, since immich performs db migration on startup, so all I can think of is, that some run may have crashed mid way, so maybe try to rollback and try again for that.

But before this, do you have made any tweaks to the configuration, since there is another issue:

Jul 05 21:56:31 Error: Invalid system config:
Jul 05 21:56:31 - [ffmpeg.acceptedAudioCodecs.2] Invalid option: expected one of "mp3"|"aac"|"opus"|"pcm_s16le"

which could be the reason the migration didn't run in the first place.

We have identified one issue on android, so maybe this also fixes iOS. We will test this later. The fix is to set the correct mimetype on download: https://git.cloudron.io/platform/box/-/commit/d843f60cb5b98a7e3f2589b899cff7440ac3d0cb

Thanks for giving us access to debug this. It turns out the update info was not cleared on the backend, maybe the update task crashed at the end just before it would have cleared it. We have added a fix for the next release with https://git.cloudron.io/platform/box/-/commit/4c0033f57210b233754f66f2cf4c70c3ff39db1f

This is a bit out of scope the moment to add a settings via admins or so to disable this. The main issue is that the app itself has no admin panel or such, in fact not even a concept of admins, so this will have to be done at a later stage. For the moment we try to get closer to what google calendar has as a baseline, and that has pretty much exactly that in the UI without a way to disable this as far as I can tell. But not to discourage feedback here, keep this coming, we will revisit those either way!