-
Notifications
You must be signed in to change notification settings - Fork 11
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
galaxyprojectdotorg.tools role does not exist in galaxyFS.yml #15
Comments
That should be All the pre-tasks can be commented but that depends if the dirs those pre-tasks already exist, although it really doesn't hurt to leave them uncommented. If you're trying to just install some tools, this playbook may be a bit easier to digest: https://github.com/afgane/galaxy-tools-playbook |
I see, thanks. I'm trying to install some tools, customize some |
You can probably customize the basic playbook (https://github.com/afgane/galaxy-tools-playbook) a bit then and just add a couple of tasks there that change |
OK, thanks. I should have mentioned that I also need to produce a galaxyFS archive that could be used in our private Cloud Launch instance along with a custom galaxyIndices volume (which I've already prepared manually). |
Ahh - then take back what I said and use this playbook - it has provisions to build the archive and all. If you run it a couple of times as tests, you'll get a hang of how it behaves. Also feel free to send me the config you're using if you run into problems and I can take a look. |
The README file says on lines 205-208:
If you wish to use this playbook only to install some Galaxy tools, comment out all roles except
galaxyprojectdotorg.tools
ingalaxyFS.yml
file. You may also want to comment out thepre_tasks
, depending on where you are running this.However, there is no
galaxyprojectdotorg.tools
role ingalaxyFS.yml
, so it's not clear which roles to remove. Also, it is not clear whichpre_tasks
to remove.The text was updated successfully, but these errors were encountered: