ScuttleSE

I have my playbook like this: ``` - role: nginx-letsencrypt letsencrypt_domains: [example1.org, www.example1.org] - role: nginx-letsencrypt letsencrypt_domains: [example2.se, www.example2.se] - role: nginx-letsencrypt letsencrypt_domains: [rss.example3.org] ``` That creates three different cronjobs...

Welp, this is what I've got :)

Ah, well, the thing is that I have one nginx-server that acts as a reverse proxy for several applications behind that, so I serve about half a dozen or so...

Well, yeah, that would work, but wouldn't that mean that if you look at the cert for example.com, you can see that it is also valid for example2.com, example3.com etc?

Mm...that's something I would like to avoid, but just running the role multiple times isn't a real problem, so I'll stick with that for now :)

This setup works just fine fyi ``` - hosts: proxy_server roles: - role: nginx-letsencrypt letsencrypt_domains: [example.org, www.example.org] - role: nginx-letsencrypt letsencrypt_domains: [example.se, www.example.se] ```

Indeed it does, a large one

Well, in the generated conf-file in sites-enabled there is a root set, in this case to `root /usr/share/nginx/html;`

But since I don't have a root on the nginx-server, what should I set it to? My upstream is on another machine.

The old config was a huge, ugly monolithic conf, can I email it instead?