Flexible site-conf.js selection during build #82
Merged
Conversation
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
Contributor
Author
|
Tested and confirmed working so changing to proper PR. |
… with fallback to the one for EMULATE_DOMAIN if no site-conf exists for DOMAIN.
jonasbardino
force-pushed
the
adjust/flexible-site-conf-selection
branch
from
fc32ff9 to
73e97bd
Compare
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.
Set up
site-conf.jsto point to any matchingsite-conf-{$DOMAIN}.jswith fallback to the one forEMULATE_DOMAINif no site-conf exists forDOMAIN. Similar to how theindex.htmlpage is chosen and useful e.g. in relation to status site deployments.This is still untested in action so only a draft PR for now.