|
| 1 | +# .dockstore.yml for Xena |
| 2 | +version: 1.1 |
| 3 | +service: |
| 4 | + type: docker-compose |
| 5 | + name: UCSC Xena Browser |
| 6 | + author: UCSC Genomics Institute |
| 7 | + description: | |
| 8 | + The UCSC Xena browser is an exploration tool for public and private, |
| 9 | + multi-omic and clinical/phenotype data. |
| 10 | + It is recommended that you configure a reverse proxy to handle HTTPS |
| 11 | + # These are files the Dockstore will index. They will be directly downloadable from Dockstore |
| 12 | + files: |
| 13 | + - docker-compose.yml |
| 14 | + - README.md |
| 15 | + - stand_up.sh |
| 16 | + - load.sh |
| 17 | + - port.sh |
| 18 | + - stop.sh |
| 19 | + |
| 20 | + scripts: |
| 21 | + # The scripts preprovision, prestart, start, poststart, and postprovision will be executed in order. |
| 22 | + # The only script required to have a value is start. |
| 23 | + |
| 24 | + # Before any provisioning |
| 25 | + preprovision: |
| 26 | + |
| 27 | + # After provisioning, before starting the service |
| 28 | + prestart: |
| 29 | + |
| 30 | + # Starts the service |
| 31 | + start: stand_up.sh |
| 32 | + |
| 33 | + # After the service has started |
| 34 | + poststart: |
| 35 | + |
| 36 | + # After the service has started. For multiple provisionings, e.g., the user may decide to add more data later. |
| 37 | + postprovision: load.sh |
| 38 | + |
| 39 | + # Returns the port the service is exposing. Can be used by a client to know what port to proxy |
| 40 | + port: port.sh |
| 41 | + |
| 42 | + # Returns an exit code of 0 if service is running successfully. |
| 43 | + healthcheck: |
| 44 | + |
| 45 | + # Stops the service |
| 46 | + stop: stop.sh |
| 47 | + |
| 48 | + # Items in this section are passed to the scripts as environment variables. |
| 49 | + # The names must be valid enviornment variable names. |
| 50 | + environment: |
| 51 | + httpPort: # The name of the environment variable |
| 52 | + default: "7222" # An optional default value |
| 53 | + # A description that tools can use for prompting a user. |
| 54 | + description: The host's HTTP port. The default is 7222. |
| 55 | + |
| 56 | + # Data are files that are provisioned locally for the service. Each key is a dataset name, |
| 57 | + # and each dataset can contain 1 to n files |
| 58 | + data: |
| 59 | + # The name of a dataset, can be anything |
| 60 | + dataset_1: |
| 61 | + # The location on the local system where files should be downloaded to. This |
| 62 | + # can be overriden if desired on an individual file level. |
| 63 | + # In this case, Xena requires files to be located in the subdirectory xena/files |
| 64 | + # relative to where Xena is running. |
| 65 | + targetDirectory: xena/files |
| 66 | + |
| 67 | + # The files property is required for datasets. It contains one or more files. |
| 68 | + # The sets of files can be repeated. In the sample xena-all.json, there are |
| 69 | + # 3 pairs of tsv/metadata files. |
| 70 | + files: |
| 71 | + tsv: |
| 72 | + description: Data for Xena in TSV format |
| 73 | + |
| 74 | + # Could override targetDirectory here, but since all files go into xena/files, no need |
| 75 | + # targetDirectory: |
| 76 | + metadata: |
| 77 | + description: The metadata, in JSON format, that corresponds to the previous tsv file |
0 commit comments