What's coming in 5.6
-
A progress update on the release.
-
VAAPI (hardware transcoding on linux) support work well now. I had posted an update here - https://forum.cloudron.io/topic/3035/transcoding-update
-
Lots of activity on the email side:
-
You can set the mail server location:
-
Adjust the max message size:
-
Adjust spam configuration:
-
We have decided against separating the mail and box backups for this release. There's some complications to do this properly (the mailbox and domain information is currently in the box code, we have to move this to the mail container. it's quite a bit of work and we feel this feature is not important at this point to justify the surgery).
-
Cloudron will not auto-update to pre-release version if you simply just checked for an update.
-
Scheduler: if you have a bunch of WP apps (especially unmanaged WP), you will see a lot of networking churn in dmesg and docker logs output. We have seen in a couple of customers who have over 100 WP installations, docker gets into some strange deadlock (iptables locking). To circumvent this, the cron job scheduler has been re-designed now so as to not create a new container for every cron run and also shares the networking namespace of the app container. This change requires no changes to apps.
-
Allow box auto update pattern to be configurable. The update schedule that in the Settings UI now applies to both the app and platform auto updates (previously, it only applied to app auto updates). This gives you more control on when the updates happen.
Phew, already changes are piling up, so will probably have to drop some of the planned features.
-
-
-
Nice work on the Mail server side of things!
Being able to set mail server subdomains to the more commonly used
mail.will be a bonus.Thunderbird checks common subdomains as a second resort, although the extra DNS records for the standard autoconfig stuff would be better for more clients to autodetect.
I'm hoping that will help with email client auto-setups but anything you can do to also add the necessary records would be super handy:
-
-
@doodlemania2 It turns out collecting network information for each container is quite complicated. It's easy to collect the stats at a point in time (like docker stats does) but to do it over a time period, requires us to periodically track the container/process. I put some notes here - https://git.cloudron.io/cloudron/box/-/issues/734 . I have to postpone that task since it's quite complicated. If someone has better technical knowledge on this, please do leave a note on gitlab.
-
Thanks for the update good sir!
-
For the email auto-configuration, for now I will just add docs on how to set this up manually. It's a bit complicated to automatically set all this up because outlooks requires SRV records (for which we have to write automation code for the DNS providers) and thunderbird/k9 requires setup of
.well-knownfiles. This has the same issue as mastodon where we can automate only the website is also on Cloudron. So, for now, I will put docs on how anyone can set this up manually. -
@will It can but it only works when the domain's web server is hosted on Cloudron. For example, cloudron.io website is hosted on a different server than cloudron.io email. The well-known has to be added on whichever server is hosting the website and not the email server.
-
-
@will I see what @girish is saying:
- One Cloudron managed server has Email hosted with it's various subdomains
- Another (maybe Cloudron managed) server has the root website domain.
- So the
.well-knownfile needs hosting on the root domain server.
I've been thinking a fair amount recently about whether to
www.the main website or not.Originally, I though, who still types
www.?But, that misses the ability to manage it as just another subdomain, and have the main root domain 301 redirect to
www..Reasons for having
www.? Well, this use-case could be one. CNAME load-balancing could be another.I'm thinking that Google does
www.for their main domain and many other big players do too, so maybe they are right and my non-www.thinking for succinct brevity was missing some of these other possibilities that usingwww.enables.Might be an SEO risk changing large websites and potentially messing up the 301 redirects for all indexed URLs but I'm having a serious think about going back to
www.given those using it probably know more than I do as to why it might be better.Web Design https://www.evergreen.je
Development https://brandlight.org
Life https://marcusquinn.com -
@marcusquinn For most people it doesn't matter if we use www or non-www, but I found this page many years ago which has made me stay consistent in using www over non-www, which you may find interesting too.
It mostly comes down to technicalities really (but this is probably a good example of one too): https://www.yes-www.org/
Or more specifically, this direct page for the reasons why to use www over non-www: https://www.yes-www.org/why-use-www/
With that said though, while the vast majority of major websites use www, some very large companies don't either, so there must be some valid reason or workaround they've found to any restrictions. Twitter is one that comes to mind, for example. That article actually mentions Twitter too. haha.
-
@d19dotca Very handy, thank you - you and they have me convinced now.
We have a load of Kubernetes stacks - but I feel they are overkill for most of your needs and the pods and replication has network latency, so I'm looking at more of a master-slave hot-swap high-availability strategy that will ultimately be cheaper, easier to understand and simpler to scale.
