[Resending (again) as GMail keeps mangling my email address… sorry for triple
posting...]
Hi Björn,
> Yes it is, but you need the :dev version,
DOH, I should have known…
> Can you explain what you delete? I do really support this idea as we are
> also developing cheminformatics or imaging
Hi Björn,
> Yes it is, but you need the :dev version,
DOH, I should have known…
> Can you explain what you delete? I do really support this idea as we are
> also developing cheminformatics or imaging flavours.
Currently I think I have just removed the datatypes. I haven’t removed
anything
[Resending because GMail keeps mangling my email address…]
Hi Björn,
> Yes it is, but you need the :dev version,
DOH, I should have known…
> Can you explain what you delete? I do really support this idea as we are
> also developing cheminformatics or imaging flavours.
Currently I think I have
Hi Björn,
Have you pushed the new version to the Docker Hub? When I run the
galaxy-stable image with the -e BARE=true option I still get a Galaxy instance
with the default tools.
Also, does this really give me a “bare” Galaxy instance, or just a Galaxy
instance with an empty tool_conf.xml
Hi Stephan,
Thank you for the pointers, they will definitely help. Would you be willing to
share any of the code you have for the upload tool?
Will you be at the LREC conference in Portorož? It might be fun to arrange a
meet up of all Galaxy users if we can.
Cheers,
Keith
> On Mar 31,
Hi Keith,
with this PR merged
https://github.com/bgruening/docker-galaxy-stable/pull/164
You can use the Galaxy Docker Image and pass in the -e BARE=True option.
This will give you an production ready Galaxy Instance without tools,
but with FTP Server, scheduler and activated TS.
You could even
dear keith,
in our work on building the Linguistic Analysis Portal (LAP) at the
University of Oslo, we have had to confront the same two issues you
mention. our general approach has been to separate LAP-specific code
(and specifications) from the Galaxy tree as much as possible.
for example, we
