Since Cloudron is handling the redirects, I don't think it would be efficient to do in the .htaccess for every site.
Based on this Google Pagespeed report for
http://marcusquinn.comwhich will be the first try for anyone typing in a domain:
In reference to these articles:
It seems this generator would be good for the default setup when
www.is the Main location:
My website if you're interested in my ramblings on technology too :
Will do a proper write-up post on Cloudron once I'm happy with my setup
@girish Yes please Same principles would be equally valuable to those using Ghost / Wordpress / Surfer for their
Might be worth a note in the Docs too with a link to the above commentary on the reasons for choosing to use
www.as it would help make high-availability multi-Cloudron setups possible, where you can have multiple CNAME IPs for a subdomain but not the naked root domain AFAIK.
I simply add www for most apps because too many people are used to type this before reaching their destination.
But from reading this thread I'm even more confused ?
I thought dropping www was not such bad idea, a bit a useless remain from when hosting was hard? I may be completely wrong but I really want to understand what's the best thing to do, certainly if it impacts SEO etc...
@rmdes I think from a user point of view it just needs to work with either, they don't really care as long as typing results in what they were hoping for. From a Sys Admin point of view, www. is more flexible for scaling and high-availability setups. As an example, if you use Odoo enterprise, it must be www. for the websites.