Configure K8s deployment for easy LetsEncrypt verification.
This is not the certificate setup we will use in production. I'd like to merge this configuration as a reference point because this is the easiest way to handle manual LetsEncrypt verification within the cluster. This allows NGINX to serve static files over HTTP from the ".well-known/acme-challenge" directory, which is necessary for certbot validation of domain ownership.
This commit is contained in:
@@ -9,12 +9,24 @@ data:
|
||||
server {
|
||||
listen ${PORT_PREFIX}342;
|
||||
server_name ${MAIN_DOMAIN};
|
||||
return 301 https://$host$request_uri;
|
||||
root /usr/share/nginx/html;
|
||||
location /.well-known/acme-challenge/ {
|
||||
try_files $uri =404;
|
||||
}
|
||||
location / {
|
||||
return 301 https://$host$request_uri;
|
||||
}
|
||||
}
|
||||
server {
|
||||
listen ${PORT_PREFIX}343;
|
||||
server_name ${AUTH_DOMAIN};
|
||||
return 301 https://$host$request_uri;
|
||||
root /usr/share/nginx/html;
|
||||
location /.well-known/acme-challenge/ {
|
||||
try_files $uri =404;
|
||||
}
|
||||
location / {
|
||||
return 301 https://$host$request_uri;
|
||||
}
|
||||
}
|
||||
server {
|
||||
server_name ${MAIN_DOMAIN};
|
||||
|
Reference in New Issue
Block a user