- Can't start uWSGI proxy before proxy SQLite map exists
interactivetools_map
needs to go in thegalaxy
section for the Galaxy side- Docker has to be installed on the Galaxy server even though it won't run there (ok)
- Nodes can't have the job dir root squashed
- Set
<param id="docker_set_user"></param>
on destination to run container as root Not implemented for DRMAA runnerI added the call to get the ports, but container stopping doesn't work. I consider this a container resolver issue and not a runner issue and am using an Epilog script to deal with it for the moment.- Wildcard certs are only valid for a single level, so you need a cert for
*.interactivetoolentrypoint.interactivetool.example.org
whereexample.org
is your Galaxy server. - uWSGI as a proxy seems to have the same problems I encountered when originally trying to set it up as a proxy (enabling
offload-threads
causes connnections to fail after 3 connections are made, disablingoffload-threads
causes them to operate at an absolute crawl), so I used the Node.js proxy updated at https://github.com/usegalaxy-eu/gie-nodejs-proxy/tree/ie2
Last active
February 26, 2020 19:15
-
-
Save natefoo/ff5bcf9c49146c41ec3f124e95ae6e95 to your computer and use it in GitHub Desktop.
Interactive Tools setup notes
And an Ansible role!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we built an alternative proxy (based on the proxy for the original GIEs) that does work unlike the built in one, for multi-user deployments.
https://github.com/usegalaxy-eu/gie-nodejs-proxy/tree/ie2