Bug-fix: Use canonical domain in publication dirs #102
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
dsilhavy
approved these changes
Oct 11, 2023
…omains list (closes 5G-MAG#101)
davidjwbbc
force-pushed
the
bug-fix/use-canonical-domain-in-publication-dirs
branch
from
4bf7f11
to
f3045b1
Compare
davidjwbbc
deleted the
bug-fix/use-canonical-domain-in-publication-dirs
branch
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.
Adds the canonicalDomainName field values, from ContentHostingConfigurations, to the list of domains to publish the
m8.jsonfile to.This is a fix for an issue noticed on the Linode VM.
Closes #101