@robi how did you land at "api"? If you want an ai agent to handle your inbox then there are probably better apis than the imap protocol, yes. but that is a different topic to oidc and mfa.

+1 - Great idea! Even the ability to automatically pull an IP list into the blocklist on a set cron schedule would be extremely beneficial.

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

@girish said: The messages are fixed now Does that include colours coming back too?

Ohh, also one thing missing is distinguishing of different builds by build number in the UI. If 2 of 3 are stuck, which ones do I stop?

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}'

Fantastic! Thanks so much, @james

@m3pilot it's not a problem. Cloudron periodically checks (everyday) if the namecheap credentials are working. If not working, it will give you a notification that DNS credentials are not working. As part of the check, a DNS entry is created and deleted immediately .

Yes, that's correct.

If the image still isn't found, the Docker daemon fetches the image from the canonical repository on Docker Hub. that's a feature of docker daemon itself. Fallback through the list of configured registry-mirrors. The key here is that docker pull docker.io/cloudron/base is treated exactly as "docker pull cloudron/base" (implicit hub.docker.com) whereas docker pull registry.docker.com/cloudron/base is ignoring registry-mirror list because it is an explicit registry image ref. quay.io would also fail in a "restricted" network environment. One of the other solutions I considered is to allow a "cloudron base registry" option in the installer.

I'm currently looking for such a feature. We want to block any request to applications as a security measurement. It would hinder any unauthenticated request to any resource which would create a significant barrier for any application which is not supposed to be publicly accessible. No request would reach the application if the client does not have a valid Cloudron SSO token. Nice and practical feature on top of that: create an allow-list for resources or path-patterns which may be excluded from the proxyAuth requirement. This would allow us to selectively publish certain parts of an application.

Yes, is something in .NET, but runs on many plattforms (Linux, Windows, Docker, macOS, RasPi...)

I have implemented this in Cloudron 10 . You can set the maxmemoryPolicy in the manifest.

@ekevu123 This was the idea suggested here, I think: https://forum.cloudron.io/topic/8745/my-apps-dashboard-ux-tailoring-apps-category

@alwynispat https://docs.cloudron.io/server#default-data-directory

Thanks - I see where you are coming from, but this is not directly what I aimed for with my initial post as a cheeky attempt to get consideration for a mail archiving app officially packaged for Cloudron. nonetheless, I see both as valuable topic of discussion: Legal compliance with business email archiving, especially in transactional email scenario - as a Cloudron feature tight to cloudron email server Email archiving app, possibly providing the above functionality by delegation of the feature but also enabling the archive of other emailing solution not residing on Cloudron (e.g. gmail, outlook etc..). Selfishly, the later is what is most attracting to me due to the need of archiving emails from various email solutions / providers as well as cloudron ones.

@gobenizzle so the next release will be all about mail improvements. We will investigate this feature request as well.

Great catch! Always good to have users with resource out of the ordinary Fixed with https://git.cloudron.io/platform/box/-/commit/d504db161a839acb6742f6f7bf156e9b8a5bb0a6 but didn't made it into 9.2