-
Notifications
You must be signed in to change notification settings - Fork 186
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
Remote bulk-import of scripts #46
Comments
Can go in with the ideas from #15 as well. |
Ah good point missed that. For an example of a good library of scripts there is https://github.com/jorvis/biocode this library available which contains a large number of Python scripts predominantly for working with FASTA currently. The scripts are well-designed and documented (with a file-header text block something we might want to support in preference to a separate markdown file?) One issue is that they use strings for the input/output file so the Think it might be worth forking it (into the Wooey org) and applying the neccessary changes to get it to work and see if they'll accept a PR? |
That is bizarre they don't use the filetypes. The only case I've done something similar was when I had an argument that could be a file or a directory (do you ever do this?). If they're interested and it'd be helpful, why not. It would give users the ability to preload wooey with a ton of biological scripts. |
See #55 for a first implementation. Regarding biocode it may simply be that they don't know about it — I first discovered they were there when I was working on Wooey :) They have pretty strict design guidelines/etc. so I suspect they'll be keen on doing it "the right way". I'll fork it into the wooey org and convert them (probably be able to do most of it automatically). |
Closing this in favour of #15 |
Add support for bulk-importing multiple scripts (optionally from a remote URL). The use-case I'm thinking would be to have repositories ("BioWoo" etc.) containing bundles of useful-for-everyone scripts that new installations can import, e.g.
We could simplify this further by adding an in-built set of bundle names somehow, e.g.
...and all the scripts would be installed and set up automatically. A nice way to get from a fresh installation to a completely working/useable system. We could also add support for this in the admin panel (I'd suggest installating bulk-sets like this under a specific script group so they can be bulk activated/deactivated/deleted).
The text was updated successfully, but these errors were encountered: