Added 'CUSTOM_DOCS' support when using 'CUSTOM_DOMAIN' #250
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.
Original Issue:
CUSTOM_DOMAIN
with an MkDocs project with a customdocs_dir
(e.g., my RGBwiki project), deployment fails becauseactions.sh
was statically set to add the CNAME to the/docs
directory; meanwhile themkdocs.yml
file is expecting a different directory.Fix:
CUSTOM_DOCS
that allows you to to specify thedocs_dir
to echo the CNAME to.CUSTOM_DOCS
is not used,docs
is the assumed path.(Note: also bulleted and added to the README.md to make it easier on the eyes)