nginx: add www subdomain & redirect as default

[cybrmakr]

NGINX forwarding

It's common to have a server blocks regarding forwarding like this :)

server {
listen 80;
server_name www.example.com;
return 301 http://example.com$request_uri;
}

server {
listen 80;
server_name example.com;
...
}

Would be amazing if this could be added to Ansible in order to configure this in nginx automatically.
Same applies to HTTPS, right? Also, is it possible to enter subdomains in the Ansible script for gettings certificates via certbot for both,
www.example.com as well as example.com itself.

Currently when opening browsing the www. version nginx default page appears. :)

[Nutomic]

You are more than welcome to make a pull request with these changes.

[ticoombs]

While this seems like a good example, it is actually more trouble than it's worth.
As now that it's 2023, not everyone uses the full domain.

While it's true that for some this would be a benefit, the majority (looks at instance federation list) are already using subdomains. adding www.subdomain.example.com as a redirect seems redundant. Unless! If browsers still try www automatically for existing subdomains then this would be needed.

If we want to tackle this issue, having a section behind an {% if www_enabled is true %} and have it as www.{{domain}} would suffice

[codyro]

Let's Encrypts allows certificates to have multiple SANs, so if we wanted to support this, we could do something more flexible.

Maybe we can have a SAN list that will get used when certbot requests the initial certificate?

pseudo-code

ssl_san:
  - www
  - staging
  - testing

The above would generate a valid certificate for www.{{ domain }}, staging.{{ domain }}, etc.

I don't necessarily think the above is the best approach, but making it limited to "do you want www or not" doesn't feel right to me.

Whether the juice is worth the squeeze, I don't know. The above proposal changes can be done quickly, though.