The new variable is gie_proxy_install(defaults to true). Through this variable, we can decide whether to install (tasks: clone the gx-it-proxy repo and compile the Node JS modules) or not. We (at EU) only want this to be installed on the maintenance node without the systemd service and then on the head node(s), we would need only the systemd service (because at EU, we plan to have 2 head nodes in the near future, so we will have Galaxy installed on one node and then sync it to NFS and from there to the head node(s)). So with this new variable, we can switch them ON and OFF depending on where we are installing. This variable will not affect the current behaviour (the default value is set to true). Other tasks in the playbook already contain variables, so we can use them to switch things ON and OFF.
bgruening
commented
1 year ago
The new variable is
gie_proxy_install(defaults totrue). Through this variable, we can decide whether to install (tasks: clone the gx-it-proxy repo and compile the Node JS modules) or not. We (at EU) only want this to be installed on the maintenance node without the systemd service and then on the head node(s), we would need only the systemd service (because at EU, we plan to have 2 head nodes in the near future, so we will have Galaxy installed on one node and then sync it to NFS and from there to the head node(s)). So with this new variable, we can switch them ON and OFF depending on where we are installing. This variable will not affect the current behaviour (the default value is set totrue). Other tasks in the playbook already contain variables, so we can use them to switch things ON and OFF.