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

Planemo-machine as a Galaxy flavor setup method #56

Open
afgane opened this issue Mar 15, 2016 · 3 comments
Open

Planemo-machine as a Galaxy flavor setup method #56

afgane opened this issue Mar 15, 2016 · 3 comments

Comments

@afgane
Copy link
Contributor

afgane commented Mar 15, 2016

Planemo-machine playbook already links a number of general Galaxy setup Ansible roles but focuses on creating a Galaxy flavor tailored for tool development. It seems it would be desirable to reuse the playbook infrastructure and allow additional flavors to be specified. I feel the easiest way to achieve this would be to simply add additional files such as the current provision.yml that each define given flavor's properties (along with appropriate documentation)?
If this is acceptable and as more flavors get added, I'd suggest changing the name of the repo, perhaps galaxy-flavor-machine?

@jmchilton
Copy link
Member

This is a good idea... I think. I guess I might re-propose the issue and say this - can we merge this project and @mvdbeek's https://github.com/ARTbio/ansible-artimed. Rather than reworking this we should try to build one project that covers both uses and steal what is best from each - @mvdbeek's stuff uses galaxy tools already and a better postgres database role.

@afgane
Copy link
Contributor Author

afgane commented Mar 15, 2016

Ahh... yes! I wasn't aware of the GalaxyKitckstarter playbook so will take a deeper look, give it a try later this week and we can go from there.

@mvdbeek
Copy link
Member

mvdbeek commented Mar 15, 2016

Absolutely, that would be cool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants