handbook/sales: gate the PoV environment on outbound network access, not just install - #5724
Draft
dgatti0213 wants to merge 1 commit into
Draft
handbook/sales: gate the PoV environment on outbound network access, not just install#5724dgatti0213 wants to merge 1 commit into
dgatti0213 wants to merge 1 commit into
Conversation
…not just install For self-hosted installs, "FlowFuse installed" is not the same as a ready environment. If the environment can't reach the hosts FlowFuse needs to install and update nodes/packages, the PoV stalls the first time someone adds a node — a recent PoV lost a week to exactly this. Strengthen gate #5 in both the Solution "What the SE produces" list and the Pre-PoV checklist: the outbound access must be filed *and proven* during Solution, and links to the Networking requirements docs page for the host list to hand the customer's network team. Depends on FlowFuse/flowfuse#8354, which adds /docs/install/networking-requirements — keep this PR in draft until that merges (the link 404s until then). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KT4u2XgENWkw2Rm6oEXFXx
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
What
For self-hosted installs, "FlowFuse installed" is not the same as a ready environment. If the environment can't reach the hosts FlowFuse needs to install/update nodes and packages, the PoV stalls the first time someone adds a node — a recent PoV lost a week to exactly this.
Strengthens gate #5 in both places it lives:
sales/meetings/solution.md→ "What the SE produces in Solution" (Remove placeholder blog posts #5, A ready environment)sales/meetings/pov.md→ "Pre-PoV checklist" (Remove placeholder blog posts #5, FlowFuse is available to test)The outbound access must be filed and proven during Solution (not discovered mid-PoV), and both spots now link to the Networking requirements docs page for the host list to hand the customer's network team.
Links to
/docs/install/networking-requirements/, which is added by FlowFuse/flowfuse#8354. Keep this in draft until that merges — the link 404s until then.