What's coming in 6.0
-
I would love to see the ability to use the + delimiter in emails e.g user+ebay@domain.com or user+pizza@domain.com.
Other providers like Mailcow or Mail in a box have this feature and I find it quite handy when I am filtering spam into its own folder!
Another email feature requests is the ability to create a temporary email from the cloudron admin portal for a logged in user. Mailcow has this feature and it is again quite handy.
-
@ultraviolet itโs already there, see docs: https://cloudron.io/documentation/email/#subaddresses-and-tags
-
@ultraviolet Does Catch-all & Masquerading enabled help?
-
@marcusquinn said in What's coming in 6.0:
@ultraviolet Does Catch-all & Masquerading enabled help?
Yes I use mainly a catchall with alias for email want to use to reply
it is something I was doing with MailCow and it work well with Cloudron too.The only thing in Cloudron you need one catchall per domain while it was possible to alias
catchall@domain2.tld to catchall@domain1.tld in MailCow -
If I can add File Permissions management to the Wishlist for the nice new File Manager please.
-
@marcusquinn said in What's coming in 6.0:
If I can add File Permissions management to the Wishlist for the nice new File Manager please.
Seeing the screenshot in girish's post here (more precisely the icons of the actions on the right), I think it's already done for the next version
-
@nebulon Ahh, I see. Perhaps it could so with a
...
at the end of the row to click as well to show thatFor interest, I get "Cloudron Error" when trying to navigate into the
Contents
directory on my Ghost install. Guessing maybe file permissions or bug? -
@marcusquinn They just pushed a 5.4.1 version to fix a bug when navigating symlinks. Maybe ghosts Contents is actually a symlink and that's what you're hitting ?
-
ty @girish for the update, we are working on OpenLiteSpeed image for WP, we are having some issue with the config file, but we hope to have a beta soon.
-
@girish said in What's coming in 6.0:
Unified dashboard for multiple cloudron setups - This will provide a unified auth across cloudron setups plus a single dashboard to control multiple cloudrons. Details are still being worked on and I will post it once I have more info.
-
@MooCloud_Matt For interest I did a bunch of performance testing for WP a couple of years ago and LiteSpeed didn't give us any edge and was slower in many cases for a large stack (200 plugins).
I have written a ticket for our devs (brandlight.org) to share the things that we tuned for a fast stack, so we will share notes soon with our Brandlight base WP & Woo stack.
Disabling
open_basedir
in php gives a big performance improvement on any stack.And we make all directories non-writable for security, except
/uploads/
, since the only way anything can be deployed is with GitLab CI/CD with appropriate write permissions.We don't use full-page caching, just fragments and transients and these are our TTFB times for interest, like I say 200+ plugins:
- https://status.brandlight.org (Cloudflare)
- https://status.swanson.co.uk (Route53)
- https://status.healthshop.net (Route53 but moving to DNS Made Easy)
Each on Vultr VMs with Network WAF, and no CDN yet.
Plus, on any of those sites, you should see similar times with any language - again I'll ask our dev team to share more on all that when we get time too.
Maybe there's more to LiteSpeed that we missed but the above is with Apache, Nginx and FastCGI.
-
I agree that OLS or LS are not the solution, because Nginx + FastCGI + ProxyCache are excellent (with LS + ESI woocommerce it works better in any situation in this days) especially in big sites with a lot o page, content and static content like images.
But large sites are exceptional cases in the hosting world, especially those who would use cloudron do not have a huge site because they would prefer to use a custom stack in that case.
We are thinking of satisfying the customer who wants performance without doing anything other than installing the LiteSpeed cache plugin. -
We are working with @girish in general to improve the WordPress and NextCloud Apps, probably moving (nothing certain) to Nginx + FastCGI.
The problem will not be nextcloud, but WordPress; We are looking for a way to intelligently implement the cache in wordpress, because one of the problems is cleaning the FastCGI cache from WordPress (we have found some plugins, but they are not always easy to implement) so we are open to advice.