Conversation
Signed-off-by: Karol Latecki <karol.latecki@nutanix.com>
ssl_certificate and ssl_certificate_key paths in nginx configuration file are quite probably not "localhost" when running things in production and will be using the actual domain's directory. Use .env.nginx and envsubst to create a config file with ssl options potining to correct directory. Signed-off-by: Karol Latecki <karol.latecki@nutanix.com>
| - /bin/bash | ||
| - -c | ||
| - | | ||
| envsubst '$${NGINX_SSL_DOMAIN_NAME}' < /etc/nginx/conf.d/default.conf.template > /etc/nginx/conf.d/default.conf |
Contributor
There was a problem hiding this comment.
I probably would've ended up eval ing it instead (or just seding).
eval "cat <<-SUBST
$(< template)
SUBST
" >conf
TIL envsubst exists. In any case, LGTM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ssl_certificate and ssl_certificate_key paths in nginx
configuration file are quite probably not "localhost"
when running things in production and will be using
the actual domain's directory.
Use .env.nginx and envsubst to create a config file
with ssl options potining to correct directory.