You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used a modified version of this role to install Galaxy in a privilege separation mode. As the virtualenv is owned by a privsep user, galaxy (galaxy user) can not auto update the newly arising requirements in the virtualenv (e.g due to enabling new options in the config) .
For example the drmaa package is not installed by default. The option in the role defaults where the packages to install in the virtualenv seem to be mentioned here -
Should I add required packages (e.g drmaa ) to the pinned-requirements.txt in the Galaxy source ? Or is there a way that I have missed? Also is there a way to know which packages are not present when a new option is enabled in the configs. E.g when enabling cluster access in job config, the information that the drmaa package is missing and needs to be added.
Thanks Again and please let me know if something is missing/wrong in this post.
Regards,
Saurabh
The text was updated successfully, but these errors were encountered:
drmaa is a conditional dependency and is installed if a drmaa-backed runner plugin is enabled in Galaxy's job config. This happens in the role via these tasks in dependencies.yml:
Thanks a ton! The issue was caused by mismanagement of configs from my side and also me not checking the correct venv dir.
The role correctly and appropriately installs the requirements as they arise. Thanks also for pointing out the source snippets which are useful and answer all my queries.
Just to add, this role has been a lifesaver for me and thanks for creating/maintaining. I consider the issue closed from my side.
Dear All,
First of all thanks so much for this role!
I have used a modified version of this role to install Galaxy in a privilege separation mode. As the virtualenv is owned by a privsep user, galaxy (galaxy user) can not auto update the newly arising requirements in the virtualenv (e.g due to enabling new options in the config) .
For example the
drmaa
package is not installed by default. The option in the role defaults where the packages to install in the virtualenv seem to be mentioned here -Should I add required packages (e.g drmaa ) to the
pinned-requirements.txt
in the Galaxy source ? Or is there a way that I have missed? Also is there a way to know which packages are not present when a new option is enabled in the configs. E.g when enabling cluster access in job config, the information that thedrmaa
package is missing and needs to be added.Thanks Again and please let me know if something is missing/wrong in this post.
Regards,
Saurabh
The text was updated successfully, but these errors were encountered: