This is possible but will increase complexity in deploys and maintenance. I have also noticed that MySQL changes things between patch releases a lot. Maybe because their release numbers don't follow semver .

Good morning, that sounds acceptable for me. Have a nice day!

@girish yes, that’s a much better idea. Essentially the ability to “swap” app instances, or in other words the ability to easily promote from staging app instance to production app instance on the same server. That’d be ideal.

Yeah, email ids don't go via LDAP. Email ids and aliases are restricted because in other email systems people can use _, - and + as subaddress. Cloudron only supports + right now but might extend it to - and _. @nebulon IIRC, the _ restriction comes when we had 1-1 mapping between username and email. Maybe it's not relevant anymore. I am more open in allowing it in usernames than mailbox names.

Firefox Monitor Server -- breach data is powered by haveibeenpwned https://github.com/mozilla/blurts-server https://monitor.firefox.com/

I like this idea! I have sorted the graphs by usage for now.

I absolutely would love this option - and by "option" i mean like maybe we can make it "optional". So that you can activate on your cloudron if you want, but if you don't want thats fine as well!

This is awesome!!! Thanks @nebulon

Thanks for clarifying. I could do that, but I’m only looking to put certain apps behind IP restriction, not all of them.

Maybe we could at least introduce an optimization of the databases from time to time. The size of the referenced "ttrss_entries" table went from an insane 1,238 MB (!) to 583 MB after optimization. The following command, maybe via a button, should to the trick: mysqlcheck -Aos --user=${MYSQL_USERNAME} --password=${MYSQL_PASSWORD} --host=${MYSQL_HOST};

@necrevistonnezr Still evaluating what is the best option to update existing installations. Most likely we won't do dist-upgrade automatically. Also, new installations will default to 18.04.