- If using data from existing galaxy and gold databases, these should be dumped and imported to the current databases
- Galaxy framework
- SLURM rpms
- Munge rpms
- Polish DRMAA library
- Project management module
- Customized drmaa solution
- Galaxy main config file (galaxy.ini)
- Galaxy job_resource_params.xml (job parameters file for the cluster)
- Galaxy custom environment file (local_env.sh)
- file (.venv/bin/activate) which sets the path for the custom python packs (like drmaa_usit.py)
clone the repo to your /tmp directory and run
./deploy_full_procedure.sh
Follow the procedures in the script. The script will deploy the setup of the features mentioned above. Please refer to the final requirements which will be displayed at the end of the script execution.
/work/projects/galaxy/external_dbs/project_managers.txt
which shall contain all the project managers. This file is called by the controller lib/usit/python/Project_managers.py
This file should be edited with visudo, to avoid syntax errors. Visudo uses the editor set by the EDITOR environment variable. You can use nano this way:
sudo EDITOR=nano visudo
add the following lines
Cmnd_Alias GOLD = /opt/gold/bin/*
Defaults:galaxy !requiretty
galaxy <HOSTNAME>=(gold) NOPASSWD: GOLD
where is the hostname of the server.
ATTENTION : In order to use the project management feature, GOLD shall be running on your Galaxy instance!
- /etc/init.d/galaxyd is not modified according to settings.sh, and may need manual changes.
setting-template.sh
local_env.sh
deploy_filesender_apache_config.sh
deploy_filesender_code.sh
deploy_filesender_galaxy_config.sh
deploy_filesender_simplesamlphp_code.sh
filesender.conf
filesender-php.ini
php.conf
config-filesender.php
saml20-idp-remote.php
site_splash.html.php