Document Remote Metadata

galaxyproject / pulsar

Distributed job execution application built for Galaxy

https://pulsar.readthedocs.io

Apache License 2.0

37 stars 50 forks source link

Document Remote Metadata #200

Closed jmchilton closed 4 years ago

jmchilton commented 5 years ago

Set GALAXY_VIRTUAL_ENV when starting Pulsar.
Set in Pulsar conf:
- galaxy_home: /Users/john/workspace/galaxy
- galaxy_virtual_env: /Users/john/workspace/galaxy/.venv (probably not used)
Set Galaxy job conf:
- <param id="remote_metadata">true</param>
- <param id="use_metadata_binary">true</param> (new parameter in dev)
- or
- <param id="use_remote_datatypes">false</param>
- <param id="remote_property_galaxy_home">/Users/john/workspace/galaxy</param>

natefoo commented 4 years ago

galaxy_virtual_env: /Users/john/workspace/galaxy/.venv (probably not used)

seems to match my observation that setting it as a remote property in the job conf doesn't work either.

I have set GALAXY_HOME in my local_env.sh and remote_property_galaxy_home in my Galaxy destination config, but not galaxy_home in app.yml. So I can't tell you which of those are required.