Package Recipe 'eva-sub-cli'

recipe eva-sub-cli

EVA Submission Command Line Interface.

Homepage:: https://github.com/EBIvariation/eva-sub-cli
Documentation:: https://github.com/EBIvariation/eva-sub-cli/blob/main/docs/Getting_Started_with_eva_sub_cli.md
License:: APACHE / Apache-2.0
Recipe:: /eva-sub-cli/meta.yaml

package eva-sub-cli¶

Versions:

0.6.1-0, 0.6.0-0, 0.5.3-0, 0.5.2-0, 0.5.1-0, 0.5.0-0, 0.4.14-0, 0.4.13-0, 0.4.12-0,

0.6.1-0, 0.6.0-0, 0.5.3-0, 0.5.2-0, 0.5.1-0, 0.5.0-0, 0.4.14-0, 0.4.13-0, 0.4.12-0, 0.4.11-0, 0.4.10-0, 0.4.9-0, 0.4.8-0, 0.4.7-0, 0.4.6-0, 0.4.4-0, 0.4.3-0, 0.4.2-0, 0.4.1-0, 0.4-0, 0.3-0, 0.2-0

Depends:

on ebi-eva-common-pyutils >=0.7.1
on jinja2
on jsonschema
on nextflow >=23.10.1
on nodejs >=20.1.0
on openpyxl
on packaging
on pysam
on python >=3.13,<3.14.0a0
on pyyaml
on requests
on vcf-validator >=0.10.0

Additional platforms:

Installation¶

You need a conda-compatible package manager (currently either pixi, conda, or micromamba) and the Bioconda channel already activated (see Usage). Below, we show how to install with either pixi or conda (for micromamba and mamba, commands are essentially the same as with conda).

Pixi¶

With pixi installed and the Bioconda channel set up (see Usage), to install globally, run:

pixi global install eva-sub-cli

to add into an existing workspace instead, run:

pixi add eva-sub-cli

In the latter case, make sure to first add bioconda and conda-forge to the channels considered by the workspace:

pixi workspace channel add conda-forge
pixi workspace channel add bioconda

Conda¶

With conda installed and the Bioconda channel set up (see Usage), to install into an existing and activated environment, run:

conda install eva-sub-cli

Alternatively, to install into a new environment, run:

conda create -n envname eva-sub-cli

with envname being the name of the desired environment.

Container¶

Alternatively, every Bioconda package is available as a container image for usage with your preferred container runtime. For e.g. docker, run:

docker pull quay.io/biocontainers/eva-sub-cli:<tag>

(see eva-sub-cli/tags for valid values for <tag>).

Integrated deployment¶

Finally, note that many scientific workflow management systems directly integrate both conda and container based software deployment. Thus, workflow steps can be often directly annotated to use the package, leading to automatic deployment by the respective workflow management system, thereby improving reproducibility and transparency. Check the documentation of your workflow management system to find out about the integration.

Download stats¶

Link to this page¶

Render an badge with the following MarkDown:

[![install with bioconda](https://img.shields.io/badge/install%20with-bioconda-brightgreen.svg?style=flat)](http://bioconda.github.io/recipes/eva-sub-cli/README.html)