Repository navigation
chore(deploy): drop GitHub Pages; the cluster serves gh-pages - #282
Merged
Merged
Conversation
Contributor
Author
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
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.
doc.yarilomail.org now points at the cluster (#281): the certificate is issued and the site answers from the pods, so Pages is no longer in the path.
deploy.yml: theconfigure-pagesandupload-pages-artifactsteps and thedeployjob are gone, and so are thepagesandid-tokenpermissions and the outputs only they used. The build still publishesgh-pages, which the pods pull.indexnowdepends onbuildonly (it was skipped while the Pages job failed). It waits 90 s for the pods' one-minute pull, then the existing key check, then pings.site-root/CNAMEremoved: it only told Pages the custom domain.CNAME.docs:buildpasses. Pages itself is switched off in the repository settings by the owner after merge.