document common use case: (1) make default wordpress (2) redirect www

[pedro-nonfree]

Hi,

I found complex to solve this problem, and I think documentation should improve in this direction

this documentation helped https://forum.yunohost.org/t/dns-config-for-my-domain-redirect-www/7783/5

I think we should have a page explaining documentation to set up a wordpress in a domain example.com as default application, and a redirect in www.example.com to example.com

let me start a draft (substitute example.com with your domain):

• get example.com working
  • enter yunohost admin
  • in domains menu, click add domain
  • inside that domain configuration (domains menu, click that domain)
  • configure dns
  • ssl certificate (letsencrypt)
• install wordpress application and make default application
  • enter yunohost admin
  • applications, click install
  • search wordpress, install
  • inside wordpress application configuration (application menu, click wordpress app)
  • click make default
• create domain www.example.com
  • enter yunohost admin
  • in domains menu, click add domain
  • inside that domain configuration (domains menu, click that domain)
  • (you don't need to configure dns again)
  • ssl certificate (letsencrypt)
• install redirect application
  • enter yunohost admin
  • applications, click install
  • search redirect, install
  • be careful, this application can only be configured in installation time (if you fail with redirection, you have to uninstall and install again; you can install multiple redirections), the options are:
  • Label for Redirect: redirect from www.example.com to example.com
    • this is free text, that is the value I suggest
  • Choose a domain for your redirect: www. example.com
  • Choose a path for your redirect: /
    • of course, this produce a warning saying that you cannot install applications for www.example.com (supposedly this is what you want)
  • Redirect destination path: https://example.com
  • Redirect type: Visible redirect (302, temporary). Everybody will be able to access it.

check that it went fine with curl:

 $ curl -I www.example.com
HTTP/1.1 302 Moved Temporarily
Server: nginx
Date: Sun, 16 Feb 2020 13:54:04 GMT
Content-Type: text/html
Content-Length: 154
Connection: keep-alive
Location: https://example.com

[Neustradamus]

@alexAubin: The best solution is to redirect automaticaly www.domain.tld to domain.tld and block "www" like subdomain, no?

[alexAubin]

@Neustradamus : that's what was proposed in https://github.com/YunoHost/issues/issues/249 ... Didn't think hard enough about it to have an opinion on if that's the right thing to do or not and if it's worth it ... (On the technical side, I doubt that it's as simple as adding a line in nginx's conf)

[Neustradamus]

@alexAubin: Thanks in advance! And maybe with a feature to disable this forced redirection too but never enable by default.