WWW - Where is the "Change Location" redirect setting on Cloudron?

[LoudLemur]

The correct way on Cloudron to do these redirects is to use the "change location" setting, but I can't find it. For example:

https://www.example.com
to
https://example.com

[Solution]

https://docs.cloudron.io/apps/#redirections

[marcusquinn]

This is the correct way for your main website. www. should be the default, and naked redirecting to it.

You'd only use aliases if you had a multi-lingual site with regional domains.

[LoudLemur]

@marcusquinn Thanks! Confidence grows!

@girish - can we have @marcusquinn 's post above included in the docs?

[girish]

@LoudLemur is it not already mentioned in the 'note' section of https://docs.cloudron.io/apps/#redirections ?

[LoudLemur]

@girish said in WWW - Where is the "Change Location" redirect setting on Cloudron?:

@LoudLemur is it not already mentioned in the 'note' section of https://docs.cloudron.io/apps/#redirections ?

I would add something like this:

Worked Example:

• You have a domain name: marcusquinn.com
• You want people who arrive at your website to land there on one of your applications there, Wordpress:
• In the Cloudron control panel, you would mouse over the Wordpress application and enter it using the cog at the top right.
• From the "Location" tab, you would enter
  www
  in the location field and then save.
• Remember to restart your application, wordpress

I would include that screenshot marcusquinn had too

[jdaviescoates]

@marcusquinn said in WWW - Where is the "Change Location" redirect setting on Cloudron?:

www. should be the default, and naked redirecting to it.

Says who?

I'm not sure what way around you have it really matters, but I prefer naked as default and www redirecting to that.

[LoudLemur]

@jdaviescoates This is interesting philosophy and I would like to hear arguments for both sides of this www vs naked debate

I like the terseness of naked domain, however, www is less vague.

[girish]

@LoudLemur www vs bare domain discussion is as old as time It's the vi vs emacs or tab vs whitespace kind of discussion . Redirecting from bare to www is very common (Cloudron, Google, Bing, Cloudflare etc) redirects from bare to www but there's plenty of examples other way around (stackoverflow, slashdot, kagi, duckduckgo ...)

This doesn't apply to Cloudron hosting but technically the main "limitation" (or behavior) comes from DNS website hosting. If your site is hosted on some hosting site, usually they want a CNAME record. If a bare domain has a CNAME record, then it cannot have any more DNS entries for that bare domain. So, if example.com is a CNAME record, then the MX record also gets cname'd . This is why www subdomain is more common since it is easier to CNAME .

[marcusquinn]

@jdaviescoates Says me, since www. tells people to expect the main brand website. naked doesn't tell them anything, eg: SaaS apps often use naked for their login, and www. for the marketing site.

Check out pretty much any big brand you can think of that ought to know, www.google.com etc.

I'm sure I read a deeper article on the whys somewhere, but I was in your shorter is better camp for a long time until I realised there were good reasons for the www. being the destination.

Cookies containment from subdomains and use of CDNs are a couple of reasons I remember off the top of my head. I'm sure there's others.