Release 1.0
All threads resolved!
All threads resolved!
Compare changes
- Loraine Gueguen authored
+ 19
− 17
@@ -8,6 +8,14 @@ See `examples/example.yml` for an example of what information can be described a
@@ -8,6 +8,14 @@ See `examples/example.yml` for an example of what information can be described a
Each GGA environment is deployed at [https://hostname/sp/genus_species/](https://hostname/sp/genus_species/).
@@ -71,6 +79,17 @@ $ python3 /path/to/repo/gga_load_data.py input_file.yml -c/--config config_file
@@ -71,6 +79,17 @@ $ python3 /path/to/repo/gga_load_data.py input_file.yml -c/--config config_file
For every input organism, a dedicated directory is created with `gga_get_data.py`. The script creates this directory and all subdirectories required.
@@ -126,23 +145,6 @@ Directory tree structure:
@@ -126,23 +145,6 @@ Directory tree structure:
The stacks deployment and the data loading into Galaxy should be run separately and only once the Galaxy service is ready.
The `gga_load_data.py` script check that the Galaxy service is ready before loading the data and exit with a notification if it is not.
The status of the Galaxy service can be checked manually with `$ docker service logs -f genus_species_galaxy` or
When deploying the stack of services, the Galaxy service can take a long time to be ready, because of the data persistence.
In development mode only, this can be disabled by setting the variable `persist_galaxy_data` to `False` in the config file.