Skip to content
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

Closed
mfitzp opened this issue Aug 25, 2015 · 5 comments
Closed

Remote bulk-import of scripts #46

mfitzp opened this issue Aug 25, 2015 · 5 comments

Comments

@mfitzp
Copy link
Member

mfitzp commented Aug 25, 2015

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.

python manage.py add_scripts https://github.com/wooey/biowoo/archive/master.zip

We could simplify this further by adding an in-built set of bundle names somehow, e.g.

python manage.py add_scripts biowoo

...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).

@Chris7
Copy link
Member

Chris7 commented Aug 25, 2015

Can go in with the ideas from #15 as well.

@mfitzp
Copy link
Member Author

mfitzp commented Aug 26, 2015

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 FileField will not get picked up.

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?

@Chris7
Copy link
Member

Chris7 commented Aug 27, 2015

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.

@mfitzp
Copy link
Member Author

mfitzp commented Aug 27, 2015

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).

@mfitzp
Copy link
Member Author

mfitzp commented Aug 27, 2015

Closing this in favour of #15

@mfitzp mfitzp closed this as completed Aug 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants