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
In the "Starting Pulsar" and "Daemonizing" we are starting Pulsar by hand, why is that not done as part of the Ansible role (or playbook)? Then trainees can log in on the Pulsar machine just to look at the logs
In the "Configure Galaxy" hands-on, it is not specified which job_conf.xml file should be modified, the one in /srv/galaxy/config/ or the one in ~/ansible/files/galaxy/config/ ? The second looks a better choice, but in any case we need to specify how to restart Galaxy (point 3), i.e. with supervisor or with ansible-playbook -i hosts galaxy.yml respectively.
The text was updated successfully, but these errors were encountered:
nsoranzo
changed the title
Pulsar tutorial missing systemd
Pulsar tutorial issues
Jul 4, 2019
job_conf.xml
file should be modified, the one in/srv/galaxy/config/
or the one in~/ansible/files/galaxy/config/
? The second looks a better choice, but in any case we need to specify how to restart Galaxy (point 3), i.e. with supervisor or withansible-playbook -i hosts galaxy.yml
respectively.The text was updated successfully, but these errors were encountered: