[codex] Clarify Fusion standalone usage in FAQ#1269
Draft
llewellyn-sl wants to merge 2 commits intomasterfrom
Draft
[codex] Clarify Fusion standalone usage in FAQ#1269llewellyn-sl wants to merge 2 commits intomasterfrom
llewellyn-sl wants to merge 2 commits intomasterfrom
Conversation
✅ Deploy Preview for seqera-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
|
||
| ### Can I use Fusion without Seqera Platform? | ||
|
|
||
| Yes. Fusion can be enabled directly in a Nextflow pipeline that runs outside Seqera Platform, provided that you also enable Wave and supply a Seqera Platform access token in your Nextflow configuration. Seqera Platform is not required to run Fusion, but it is required if you want Seqera to manage the compute environment setup for you. |
Member
There was a problem hiding this comment.
Suggested change
| Yes. Fusion can be enabled directly in a Nextflow pipeline that runs outside Seqera Platform, provided that you also enable Wave and supply a Seqera Platform access token in your Nextflow configuration. Seqera Platform is not required to run Fusion, but it is required if you want Seqera to manage the compute environment setup for you. | |
| Yes. Fusion can be enabled directly in a Nextflow pipeline that runs outside Seqera Platform, provided that you also enable Wave and supply a Seqera Platform access token in your Nextflow configuration. Seqera Platform is not required to run Fusion, but it is required if you want Seqera to manage the compute environment setup. |
Member
|
Leaving this PR open so it can be used in the discussion/optimization of the automation. Minor nitpick on language, but otherwise I think it's a fair assessment of the issue. Language is in line with the rest of the language on the page. |
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
3 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.
Summary
Source
Doc target
fusion_docs→fusion_docs/faq.mdRationale
The ticket update was driven by repeated prospect confusion about whether Fusion v2 requires Seqera Platform. The existing docs implied standalone use through the Nextflow setup flow, but they did not answer the question directly where readers would expect it. This patch adds an explicit answer in the FAQ and keeps the guidance aligned with the current get-started page.
Validation
node_modulesare not available in the automation cloneFollow-up questions / gaps
fusion_docs/get-started.mdandfusion_docs/licensing.md.