-
Notifications
You must be signed in to change notification settings - Fork 629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins offline: Nextflow self-contained distribution allows only core plugins
#4330
Comments
Related to #4329 |
I think #4340 will make it possible to get around this problem by using the regular Nextflow distribution and downloading the desired set of core plugins. Otherwise we will need to change the self-contained distribution to support non-core plugins, and I don't know how difficult that would be. |
Ok, yeah sounds like we probably need to drop the I guess tied to this is that we could do with a user friendly way to distribute Nextflow in offline systems to replace that dist. Running Nextflow on another system and then transferring a bunch of directories is quite indirect and unintuitive. Could we have some kind of "downloader" web pages, that generates an |
Could we extend You could write a bash script to install everything you need for offline usage:
|
Could be an option, yeah 👍🏻 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
With Nextflow 24.07.0-edge, the "all" release has been replaced with the "dist" release which (1) includes fewer core plugins (since most of them aren't used offline anyway) and (2) has the ability to use third-party plugins. So it should now be possible to use the "dist" release offline with e.g. nf-validation. Let's have some people test this out and if it works we can close this issue. |
This should be solved as commented by Ben. |
Reopening, as the docs are outdated and need to be fixed. |
'cc @christopher-hakkaart - is this something you could add to your backlog please? Note that I don't know what the correct procedure is now for running offline with custom plugins. |
Reading again, the update may be as simple as basically |
does |
Talking to @Alexander-Stuckey about running offline with plugins, I pointed to these docs for fetching plugins for offline use, but it seems that it doesn't work if you use the
-all
distribution of Nextflow:This is currently the recommended method from nf-core, so it's causing some confusion.
We're starting to see these kinds of problems a lot now, since @nf-core pipelines are adopting the nf-validation plugin. I think that this is probably some of the first very widespread adoption of a non-core Nextflow plugin.
The text was updated successfully, but these errors were encountered: