|
16
|
1 Configuration of Galaxy to run GLASSgo via Docker
|
|
|
2 =================================================
|
|
13
|
3
|
|
|
4 Prerequisites
|
|
|
5 -------------
|
|
|
6
|
|
16
|
7 1) configure Galaxy to run tools in Docker as described at https://galaxyproject.org/admin/tools/docker/.
|
|
|
8 In addition, GLASSgo requires the current BLAST nucleotide database. For that, the `tool-data/blastdb.loc`
|
|
|
9 has to be configured accordingly as the GLASSgo wrapper reads this information as options when laying out
|
|
|
10 the user interface. We use Docker volumes to do so (Docker CLI option -v). For that, we add Docker volumes
|
|
|
11 to the (id=`docker_local`) Docker destination
|
|
13
|
12
|
|
16
|
13 `<param id="docker_volumes">$defaults,/Volumes/TC1/nt:/Volumes/TC1/nt/</param>`
|
|
13
|
14
|
|
16
|
15 More information can be found in the ./config/job_conf.xml.sample_advanced (https://github.com/galaxyproject/galaxy/blob/release_18.09/config/job_conf.xml.sample_advanced#L378) of any Galaxy instance. Obviously, the exposed folder needs to be identical with the path specified in `tool-data/blastdb.loc`. Here the local folder `Volumes/TC1/nt` contains the BLAST database and is exposed to the Docker container. In this case, the folder is bound to the same location in the container. This allows to execute the GLASSgo call in the tool XML file directly with the selected option.
|
|
13
|
16
|
|
16
|
17 2) Install GLASSgo from the Galaxy Toolshed (https://toolshed.g2.bx.psu.edu/view/computationaltranscriptomics/glassgo).
|
|
|
18 Afterwards, the Galaxy instance needs to be configured such that it is aware of the accession lists. This can be done either
|
|
|
19 manually or using a custom script.
|
|
|
20
|
|
|
21 - manually
|
|
|
22 download the accession lists from Zenodo (https://zenodo.org/record/1320180) and add the corresponding paths to the file
|
|
|
23 glassgo_accession_list.txt Afterwards, copy the file into the folder tool-data of Galaxy (e.g., /galaxy/tool-data/) or
|
|
|
24 - using the script
|
|
|
25 use the config_lookup script that downloads the lookup tables and creates glassgo_accession_list.txt in tool-data of the Galaxy instance.
|
|
13
|
26
|
|
16
|
27 Restart Galaxy.
|
|
13
|
28
|
|
|
29
|
|
|
30 config_lookup
|
|
|
31 -------------
|
|
16
|
32 We provide the source file config_lookup.py as well as a one-file bundled executable config_lookup
|
|
13
|
33 `
|
|
16
|
34 usage: config_lookup [-h] --galaxy GALAXY [--acclinks ACCLINKS --acclists ACCLISTS]
|
|
13
|
35
|
|
|
36 incorporate the accession lists in GLASSgo/Galaxy to enable clade-specific searches
|
|
|
37
|
|
|
38 optional arguments:
|
|
|
39 -h, --help show this help message and exit
|
|
|
40 --galaxy GALAXY (absolute) path to the root directory of the Galaxy instance
|
|
|
41 --acclinks ACCLINKS (absolute) path to file containing URLs to the accession lists
|
|
|
42 --acclists ACCLISTS (absolute) path to directory to save the accession lists to
|
|
|
43 `
|
|
|
44
|
|
|
45
|
|
|
46
|
