Ok, thanks for the update. Works for me as it is, but was curious if the ideas discussed above are still to be implemented.

Thank you

Cloudron community teamwork wins again 🙂 🤜🤛 🙂

IIRC, the reason for this is we had a global lock. This is not true anymore so there is probably no reason to block operations anymore. I have to investigate.

Looks good and prevents issues like looking wrong in a short sight. Thanks!

If anyone would be searching for that, unsend mail is stored at /home/yellowtent/boxdata/mail/haraka-queue - handy when your 25 port is firewalled.

This is now implemented.

@nebulon Amazing! Exactly what I was looking for. Thanks!

however, i have tryed to follow the docs.
however, when trying to get into a test application i made for this perpus, it didn't work and it kept telling me that it didn't exist, even when typing in the12diget ID. i couldn't bash into it. so yeah. and if i attempted to put this on the system itself, that could cause many problems, or potentially break cloudron.

@girish
Not looking good: https://community.letsencrypt.org/t/verified-mark-certificates/176835/9

@nebulon said in Filemanager Drag'n'drop folder trees does not work:

Ah I guess you mean the github repo for drag'n'drop! So we use vuejs with the primevue components set in the new views, moving away from the now unsupported angularjs v1.

Yes, https://github.com/jhiesey/drag-drop

@adison it reads "You are seeing this page because the DNS record of $host is set to this server's IP but Cloudron has no app configured for this domain." But instead of $host its the ip or dns name you just requested.

I understand the use case might be a bit narrow, but for those who understand - that's an absolute killer.

There is a plugin but would need to dig deeper to see if you can force the settings.

https://github.com/gianlucagiacometti/roundcube-toolbox

I like the idea. For lack of a better name, let's call this "lock/unlock" app containers.

Container starts locked. When unlocked:

It will make the container rw Disables automatic updates Gives warning to user that all changes will be lost when updating and are not part of any backups Automatically starts up the container (unlike debug mode which keeps the container in paused mode).

I think this gives the customer a window to "hotfix" things until upstream (or packaging team) figures out some fix.

Indeed, I have been noticing this as well. Our appstore server is a bit loaded now with so many cloudron installations out there. Time to add some caching.

Staring at the backup logs for a while, it dawned on me that it might be easy to extract the App sizes based on the data reported of what is uploaded ex: 48M@5Mps

Sounds easy to add all those up from a backup run and have a total backup size based on what was transferred in parts.