A virtual research environment for running and managing life science analyses, brought to you by ELIXIR On-Cloud. Users log in with LS Login, find compute services in a Cloud Registry, run tasks on GA4GH Task Execution Service (TES) and workflows on GA4GH Workflow Execution Service (WES) instances, and follow their runs. Deploy Krini with its container image for your own registry and services; other OpenID Connect providers than LS Login are planned (#43).
Read the documentation: the user guide, the operator guide for the deployment, configuration and upgrades, and development for the local setup, checks, tests and releases.
| Deployment | Operated by | Notes |
|---|---|---|
| https://krini.rahtiapp.fi/ | ELIXIR On-Cloud | Hosted on CSC Rahti |
Running Krini yourself? Open a pull request that adds your deployment to the
table in README.md.
Write the settings to a file outside the repository, e.g.
~/krini/settings.env (see Configuration; plain
KEY=value lines without quotes, as Docker doesn't strip them), and start
the image of a release; it reads all settings when the
container starts:
docker run --rm -p 3000:3000 --read-only --tmpfs /tmp \
--env-file ~/krini/settings.env docker.io/elixircloud/krini:<version>The operator guide describes the image tags, how to verify an image, and what the login provider and the TES and WES services need.
If you use Krini, please cite it with the metadata in
CITATION.cff: on GitHub, "Cite this repository" in the
sidebar of the repository formats it as APA or BibTeX.
Contributions are welcome! See the organisation's contributing
guide, mind our code of conduct, and see
Development in the documentation for the setup, checks,
tests and releases of this repository; the sources of the documentation are
in docs/.
Use the issue tracker to request features or report bugs. For anything else, write to cloud-service@elixir-europe.org.
Krini is released under the Apache License 2.0; third-party
material that it contains or builds on is listed in NOTICE.