SODAR CLI
Command line interface for SODAR Server.
Getting Started
SODAR Repositories
- sodar-server
SODAR web server for meta and mass data management.
- sodar-taskflow
Helper component for running tasks with rollback functionality.
Installation
$ git clone git@github.com:bihealth/sodar-cli.git
$ cd sodar-cli
$ conda create -n sodar-cli python=3.7
$ conda activate sodar-cli
$ pip install -e .
$ cat >~/.sodarrc.toml <<EOF
[global]
# URL to SODAR server.
sodar_server_url = "https://sodar.example.com/"
# API token to use for SODAR API.
sodar_api_token = "XXX"
EOF
Releasing
$ $EDITOR HISTORY.rst
$ git tag ...
$ rm -rf dist
$ python setup.py sdist
$ twine upload dist/*.tar.gz
History
v0.1.0
everything is new
Metadata
Release files for sodar-cli 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sodar-cli-0.1.0.tar.gz | 39.3 kB | Without provenance | Details |
Release files / sodar-cli-0.1.0.tar.gz
| Download URL | sodar-cli-0.1.0.tar.gz |
|---|---|
| Size | 39.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed4a82a37f1a874759daac7d9b422210b27441eb278edb6895bca34a43a10edd
|
|
BLAKE2b-256 checksum How to use checksums |
641a89588c1893f201a627f39268aa46c0fbc28a8ee9fb698f4f8c8e1a92a347
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.7.10
|
Security for sodar-cli 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.