updated README.md

This commit is contained in:
2020-03-18 19:15:05 -04:00
parent e76cae13fc
commit fe4b7d3a80

View File

@@ -8,4 +8,7 @@ HTTPS is forced
Since this nginx is exposed to the internet, I have setup a script that will generate a publicly trusted Let's Encrypt certificate for HTTPS sessions. On my LAN, my HTTPS services all use certificates generated from my internal certificate authority, so they would never be publicly trusted. Since this nginx is exposed to the internet, I have setup a script that will generate a publicly trusted Let's Encrypt certificate for HTTPS sessions. On my LAN, my HTTPS services all use certificates generated from my internal certificate authority, so they would never be publicly trusted.
### Domain names only ### Domain names only
No connections by IP only are allowed, everyone must have a hostname when conencting. No connections by IP only are allowed, everyone must have a hostname when conencting.
### conf.d
For simple deployments, all internal services that I would like to expose to the internet can be setup using `.conf` files in the `conf.d` directory. Let's Encrypt uses these configs to verify a domain name.