Am 19.07.2016 um 22:36 schrieb Yip, Miu ki:
Hello Galaxy Team,
We're from the Bioinformatics Shared Resources at Cold Spring Harbor
Lab and we're trying to create a new flavour of Galaxy for local use
in the lab using docker containers.
We want to add tools that are specific for our lab, such as importing
files from our system, onto this flavour of Galaxy using Docker
containers. Is there a recommended way to do this?
Can you try the following, assuming that all your tools are in
ADD ./my_tools_folder /inhouse_tools/
Now we need a tool_conf.xml file. You can create an additional one, no
need to modify the existing one. I would propose to include this config
file also in ./my_tools_folder so it will end up in
With the following environment variable you tell Galaxy about the
additional tool_conf file.
ENV GALAXY_CONFIG_TOOL_CONFIG_FILE =
Please make sure that your new tools in /inhouse_tools/tool_conf.xml
have as path "/inhouse_tools/XXXX.xml".
Let me know if this works, we should add this to the readme.
I've taken a look at the README from:
I have been able to successfully create an instance of Galaxy where
the homepage is different and tools are imported from the Tool Shed.
However, I cannot figure out how to install tools onto Galaxy that
are not from the Tool Shed. I have tried creating a container,
putting the tools into the tools folder, changing the tool conf and
the integrated tool panel xml file. Then committing the container and
creating a new image. From the new image, I tried creating another
container and running it. This does not create a Galaxy instance with
the new tool. (This also does not seem like the best way to go about
something like this.)
Thank you for your help.
Best, Miuki Yip
keep all replies on the list by using "reply all" in your mail
client. To manage your subscriptions to this and other Galaxy lists,
please use the interface at: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: