docs(cf): add deploy-from-release cf push method - #5660
Merged
norman-abramovitz merged 1 commit intoJul 20, 2026
Merged
Conversation
Document pushing the pre-built stratos-cf-<version>.zip from a GitHub release: unpack, set ENCRYPTION_KEY and SESSION_STORE_SECRET in the manifest env (the shipped defaults are a public constant and a placeholder), then cf push. Fix a stale same-page anchor to point at cf-troubleshooting.md#console-fails-to-start.
norman-abramovitz
approved these changes
Jul 20, 2026
norman-abramovitz
left a comment
norman-abramovitz
left a comment
Contributor
There was a problem hiding this comment.
LGTM - reasonable first attempt but needs more work.
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 a third deployment method to the Cloud Foundry deploy doc: pushing the pre-built
stratos-cf-<version>.zipthat each GitHub release now ships (from #5659).Previously the doc only covered deploying from source (git clone → source buildpack build) and from the docker image. Neither describes the released binary package, which is the fastest path — the backend binary and compiled UI are already in the zip, so
cf pushusesbinary_buildpackwith no staging build.The section walks through: download and unpack, edit the manifest,
cf pushfrom the folder. It calls out the two values an operator must change before pushing —ENCRYPTION_KEY(the shipped value is a public constant) andSESSION_STORE_SECRET(a placeholder) — steering both into the manifestenv:block, consistent with the existing "Running Stratos in Production Environments" guidance, which it cross-links rather than duplicates.Also corrects one link: the
#console-fails-to-startanchor resolves to a heading incf-troubleshooting.md, not this page.Doc-only change.