Support emitting CNAME file for publishing at a custom domain #1311
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
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.
This PR adds a
cnameconfiguration to [output.html] which is rendered into a CNAME file in the root of the generated site as required by GitHub Pages (see Managing a custom domain for your GitHub Pages site).The CNAME file is how GitHub knows which repo's site to serve when someone visits your domain. DNS records only point from domain (serde.rs) to domain (serde-rs.github.io), so the additional information is required to know that serde-rs.github.io/serde (i.e. the Pages site for github.com/serde-rs/serde) is the right repo to serve for that domain.