"Thank's" is like.... [image: 1722345022070-90ea0e22-68ef-4c6a-aa8f-2e9dbc9eebe4-image.png]

Indeed, we have space there, so this makes sense to not hide it unnecessarily. Fixed for next release https://git.cloudron.io/cloudron/box/-/commit/44d3baf51aaab4acc3e3a4d5188c38d4dffef257

@humptydumpty Not only on home servers, also OVH and Vultr. Additional files will definitely be with local providers. In this file "50-cloud-init.conf" as it actually is, I simply delete the line

@jdaviescoates currently, those behemoths are not on OIDC yet... But nextcloud has already been ported to OIDC. Just needs a lots of testing

Is it maybe possible to change the order in which incoming mails are filtered? With sieve you can tell the server to discard mails that match certain criteria, but that only works for mails that have not already been classified as SPAM. i suspect this is not that trivial though because the sieve filters work at the mailbox level.

@IniBudi said in Add Github Rating Score On App Store: The idea is simple like App Store or Playstore there's a rating and review section on Cloudron list apps. So we can see the star rating and review from the GitHub users or Cloudron users. I can assure you we've grasped the idea

@fbartels said in Extra Auth: Android app then also this app needs to know how to pass the "extra auth". Good point! In all likelihood it will break APIs

I will move this to Feature Requests since we don't have this feature

@ekevu123 there are other posts suggesting more options in performing backups. Might be worth doing a search. This sounds a duplicate. Doesn’t mean it’s not worthwhile. Just clarifying.

I guess the placeholder text is not ideal for that textarea but the default is to allow the app iteself to respond to the robots request. The docs state this more clearer https://docs.cloudron.io/apps/#robotstxt "By default, Cloudron does not setup a robots.txt for apps. When unset, the app is free to provide it's own robots.txt." So the default basically is not to allow all but to let the app handle it.

@alpro I have no idea what is involved either. I have moved this to feature requests to investigate for later.

Well, I thought you would say that. But how about at least make some suitable limits? E.g. the memory limit shouldn't be higher than what I can afford based on my usage. Also, if I can only upload up to three parts simultaneously that require as much memory, why can the memory limit and the upload part size differ? Wouldn't it make more sense to have one setting for both?

Atleast, for CPU and memory, in theory , we could apply the settings without an app restart. For other features like changing location etc, we have to do this case by case.