Release v2.1.0

General

• Bump cryptography requirement version to 3.2
• Create tools to handle multiple docker stacks in docker_tools repository (toggl galaxy state, update service)

Input config.yml file

• Fix typo in parameter galaxy_default_admin_user
• Add parameter galaxy_default_admin_key (required to create the admin user galaxy_default_admin_user in Galaxy)
• Check that all required parameters are not empty

Input organisms.yml file

• Add the parameter picture_path in the description section to add this picture in the Tripal homepage
• Add parameter contig_prefix in the data section to list the prefixes used for contig names. Required when they are multiple strains from the same species to map the contig name prefix to the right JBrowse dataset ID in Tripal (see Step "init")
• Add the go summary functionality in Tripal. This functionality can be activated with parameter go set to 1 in the services section
• Remove unused performed_by parameter
• Fix code for empty strain and/or sex

Step "init"

• Add a picture of the species in the Tripal homepage (the picture of the main strain if exists, the picture of another strain if not)
• Fix Tripal site name
• Add env variable JBROWSE_LINKS in the Tripal service, to map the contig name prefix to the right JBrowse dataset ID in Tripal (for Tripal hyperlinks to JBrowse)

Step "get data"

• Change data file names: use prefix strain_sex

Step "run workflow Phaeoexplorer"

• Create a parent module run_workflow_phaeo.py, with classes and methods used by the workflow scripts
• Create file constants_phaeo.py to store constants used in step "run workflow Phaeoexplorer" (workflows and galaxy tools details)
• Script gga_run_workflow_phaeo_jbrowse.py: runs a Galaxy workflow to load the genome, the annotations and the proteins to Chado, Tripal and JBrowse, for one or two strains of the same species
• Work in progress: workflows to load blast and interpro results

README.md

@@ -35,10 +35,10 @@ and a [swarm](https://docs.docker.com/engine/swarm/swarm-tutorial) (for cluster
 
 ## Reverse proxy and authentication
 
-Traefik is a reverse proxy which allows to direct HTTP traffic to various Docker Swarm services.
+[Traefik](https://doc.traefik.io/traefik/) is a reverse proxy which allows to direct HTTP traffic to various Docker Swarm services.
 The Traefik dashboard is deployed at [https://hostname/traefik/](https://hostname/traefik/)
 
-Authelia is an authentication agent, which can be plugged to an LDAP server, and that Traefik can used to check permissions to access services.
+[Authelia](https://www.authelia.com/docs/) is an authentication agent, which can be plugged to an LDAP server, and that Traefik can used to check permissions to access services.
 The authentication layer is optional. If used, the config file needs the variables `https_port`, `authentication_domain_name`, `authelia_config_path`, `authelia_secrets_env_path`, `authelia_db_postgres_password`.
 
 Authelia is accessed automatically by Traefik to check permissions everytime someones wants to access a page. 
@@ -52,7 +52,8 @@ The "gga_load_data" tools are composed of 4 scripts:
 - gga_init: Create directory tree for organisms and deploy stacks for the input organisms as well as Traefik and optionally Authelia stacks
 - gga_get_data: Create `src_data` directory tree for organisms and copy datasets for the input organisms into `src_data`
 - gga_load_data: Load the datasets of the input organisms into their Galaxy library
-- run_workflow_phaeoexplorer: Remotely run a custom workflow in Galaxy, proposed as an "example script" to take inspiration from as workflow parameters are specific to the [Phaeoexplorer](https://phaeoexplorer.sb-roscoff.fr) data
+- gga_run_workflow_phaeo*: Multiple scripts to run custom workflows in Galaxy, proposed as "example scripts" to take inspiration from 
+  as workflow parameters are specific to the [Phaeoexplorer](https://phaeoexplorer.sb-roscoff.fr) data
 
 ## Usage:
 
@@ -68,31 +69,37 @@ in the `examples` folder.
 - Deploy stacks part: 
 
 ```bash
-$ python3 /path/to/repo/gga_init.py input_file.yml -c/--config config_file.yml [-v/--verbose] [OPTIONS]
-		--main-directory $PATH (Path where to create/update stacks; default=current directory)
-		--force-traefik (If specified, will overwrite traefik and authelia files; default=False)
+$ python3 /path/to/repo/gga_init.py input_file.yml \
+-c/--config config_file.yml \
+--main-directory $PATH (Path where to create/update stacks; default=current directory) \
+--force-traefik (If specified, will overwrite traefik and authelia files; default=False) \
+[-v/--verbose]
 ```
 
 - Copy source data file: 
 
 ```bash
-$ python3 /path/to/repo/gga_get_data.py input_file.yml [-v/--verbose] [OPTIONS]
-		--main-directory $PATH (Path where to access stacks; default=current directory)
+$ python3 /path/to/repo/gga_get_data.py input_file.yml \
+--main-directory $PATH (Path where to access stacks; default=current directory) \
+[-v/--verbose]
 ```
 
 - Load data in Galaxy library and prepare Galaxy instance: 
 
 ```bash
-$ python3 /path/to/repo/gga_load_data.py input_file.yml -c/--config config_file.yml [-v/--verbose]
-		--main-directory $PATH (Path where to access stacks; default=current directory)
+$ python3 /path/to/repo/gga_load_data.py input_file.yml \
+-c/--config config_file.yml \
+--main-directory $PATH (Path where to access stacks; default=current directory)\
+[-v/--verbose]
 ```
 
-- Run a workflow in galaxy: 
+- Run a workflow in galaxy (example): 
  
 ```bash
-$ python3 /path/to/repo/run_workflow_phaeoexplorer.py input_file.yml -c/--config config_file --workflow workflow_type [-v/--verbose] [OPTIONS]
-		--workflow (Valid options: "chado_load_fasta_gff_jbrowse", "blast", "interpro", preset workflows are available in the "workflows_phaeoexplorer" directory)
-		--main-directory $PATH (Path where to access stacks; default=current directory)
+$ python3 /path/to/repo/gga_run_workflow_phaeo_jbrowse.py input_file.yml \
+-c/--config config_file	\
+--main-directory $PATH (Path where to access stacks; default=current directory) \
+[-v/--verbose]
 ```
 
 The data loading into Galaxy with `gga_load_data.py` should be run only once the Galaxy service deployed with `gga_init.py` is ready.