We are happy to announce the release of Cloudron 1.2.0.
For those unaware, Cloudron is a platform that makes it easy to run apps on your server and keep them up-to-date.
Mail Relay support
Cloudron has an internal mail server and all outbound emails from users and apps are routed via this server to recipients. To ensure reliable delivery of email, Cloudron automatically sets up DKIM, SPF, DMARC, PTR and MX records.
However, the world's email delivery network relies a lot on server IP and domain reputation. For this reason, it is sometimes necessary to send emails via trusted relay providers to deliver email. In addition, public cloud providers like Google Compute, Amazon EC2 and Digital Oceanpartially or completely block outbound email to mitigate spam.
For these reasons, Cloudron now has a mechanism to send outbound emails via mail relays like Amazon SES, Google, Mailgun, Postmark, Sendgrid or any other external SMTP server.
First select a relay provider:
And then provide the credentials and click save:
Note that Cloudron will validate the SMTP credentials when you save. For this reason, the SMTP provider must be available at the time.
Docker Overlayfs support
Cloudron sets up Docker to use the devicemapper storage backend. Some users have reported seeing significant performance improvements when using the Overlay2 backend especially when using non-SSD drives.
For this reason, we have decided to push experimental support for overlay2. You will have to setup Docker to use overlay2 manually for now. Cloudron will preserve the overlay2 setting across it's updates (previously, we used to enforce devicemapper backend during updates).
You can move your Cloudron to use overlay2 by following the instructions here.
Moving forward, if we see that overlay2 is stable and reliable, we will push an update that will transparently convert all existing Cloudron installations to use overlay2.
MySQL password length
Some PHP applications like Typo3 place restrictions on the length of the database password. We have reduced the length of the passwords generated for the MySQL addon as a result. This change is transparent to Cloudron users and is merely mentioned here for curiosity's sake :-)