Publish documentation website to GitHub Pages - #5586
Merged
norman-abramovitz merged 2 commits intoJul 6, 2026
Merged
Conversation
norman-abramovitz
approved these changes
Jul 6, 2026
norman-abramovitz
left a comment
norman-abramovitz
left a comment
Contributor
There was a problem hiding this comment.
LGTM - Deploying to my cloned Stratos repo
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
2 participants
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 publishing leg of the docs/website work merged in #5583.
website-deploy.ymlworkflow: builds the Docusaurus site and deploys it to GitHub Pages on everydeveloppush touchingdocs/orwebsite/(plus manual dispatch). Uses the official upload/deploy-pages actions; node/bun versions matchpr.yml.stratos.cloudfoundry.orgcustom domain exists, the site is built for project Pages (<owner>.github.io/stratos/).docusaurus.config.jsgainsSITE_URL/SITE_BASE_URLenv overrides (defaults unchanged); the workflow derives them from the repository owner, so the same workflow also deploys fork previews. Once the CNAME lands, set them tohttps://stratos.cloudfoundry.organd/.website/manifest.yml: the built site can also be pushed to any Cloud Foundry as a staticfile app (make build website && cf push -f website/manifest.yml).Requires a repo admin to enable Pages (Settings → Pages → source "GitHub Actions") before the deploy job succeeds. Verified end to end on a fork: the workflow run deploys and the site renders correctly under the
/stratos/base path.