-
Notifications
You must be signed in to change notification settings - Fork 17
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
Backend service for plugin metadata #34
Comments
I think we should start planning a backend-like system to manage plugins metadata, keep the |
And I bet you want to use surrealdb for it? 😄 |
Is this a hackathon project? I'd be interested in helping, as it may make my merges simpler. |
We will probably handle this internally since we'll need to host the service anyway. |
bentsherman
changed the title
Split
Backend service for plugin metadata
Nov 2, 2023
plugins.json
into separate file for each plugin
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the plugin ecosystem grows, it might be better to separate the plugins file into separate files for each plugin. This way Nextflow doesn't have to download the entire file just to get the metadata for a few plugins.
The problem is that older versions of Nextflow won't be able to pull plugins, or they will be stuck on the last version of the all-in-one file and won't be able to pull new plugins.
In any case, I don't think it will be an issue unless there are e.g. thousands of plugins.
The text was updated successfully, but these errors were encountered: