Add possibility to not enable the sites that we don't want to be enabled #201
Conversation
This file contains 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
If a site is mentioned in nginx_disabled_sites list, then no link to .conf file is created in 'sites-availiable'
inponomarev
changed the title
|
@inponomarev Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes it's feasible to leave site not enabled after running nginx role.
E. g. if we want to use nginx role to pre-configure the site, then automatically obtain an ssl certificate via letsencrypt (that requires nginx to be running) and do some additional configuration steps before we finally enable the site.
If a site is mentioned in nginx_disabled_sites list, then no link to .conf file is created from 'sites-availiable' to 'sites-enabled'.