Question: load workflow create history in config?
0
Heads up! This is a static archive of our support site. Please go to help.galaxyproject.org if you want to reach the Galaxy community. If you want to search this archive visit the Galaxy Hub search
Please log in to add an answer.
Use of this site constitutes acceptance of our User
Agreement
and Privacy
Policy.
Powered by Biostar
version 16.09
Traffic: 176 users visited in the last hour
Could you please describe your use case a bit?
Thanks for the reply. I'm trying to install a workflow and create a named history without using an api. This is to make a setup process for my application to require less steps. For example, I can generally install custom tools by just referencing them in galaxy.ini (tool_config_file=) Can I install workflows in the same way?
Thanks
I understand what you want to do, I am curious about why you want to do it (ie what does your application do).
afaik you cannot install workflows this way. And you can load tools into galaxy by referring to them in configs, but you won't have the dependencies installed thus losing reproducibility I believe.
Thanks. I'm writing a jbrowse plugin that executes a galaxy workflow. Trying to figure out how to setup an easy example.
If you are going to execute the workflow anyway why are you avoiding having Galaxy up for the installation/loading?
I do assume that the user has to setup galaxy, jbrowse, and our sample workflows. Just trying to make that process easier, if I can automate some of it (or all of it).
Giving the user an ansible playbook to execute all of this might be the simplest approach here. Depends on how tech savvy your users are.
ok. I'll have to look into it. thanks.