I'm looking at job_conf.xml, but there doesn't seem to be an entry for the tool. Is it as simple as copying some default entry and tweaking the momory? Is there a doc that will teach me how to do this?
if there's no entry for the tool then it's probably using a default, although if you have dynamic destinations defined then it could be set in one of those rules
Hey guys, just wanted to say that I’m impressed by the .travis.yml build script for tools-iuc and extensive galaxyproject documentation. :+1:
Anyone here using Kraken and/or Kaiju? I've started work on defining Galaxy datatypes for their databases - see galaxyproject/galaxy#5704 - feedback welcome. Thanks!
[mrscribe] Title: Define kaiju_db and kraken_db as compound datatypes [WIP] by peterjc · Pull Request #5704 · galaxyproject/galaxy · GitHub (at github.com)
So I believe I have made the necessary addition to job_conf.xml. Lance is the one who always restarts galaxy. I've done it on my own instance on my machine, but I don't know what the risks are of me doing it on our production server. Is there anything special someone could do other than running run.sh - like are there special options or something someone might always do? Do I need to be concerned about what user is running run.sh?
it's probably not using run.sh
try using pstree to see what's running galaxy.
What am I looking for in the output? Thanks for the hand-holding, BTW ;)
yeah it'll probably be python, or uwsgi. the -a option to pstree is useful
Wait, Lance just logged into Slack. I think I'll have it from here