tfuji/yevis-web

Web application for browsing Yevis workflow registry

yevis-web

Web application for browsing Yevis workflow registry.

https://ddbj.github.io/yevis-web/ is deployed for ddbj/workflow-registry.

In addition, see the below links:

• ddbj/workflow-registry: a workflow registry built and maintained by DDBJ using yevis-cli
• ddbj/yevis-cli: a CLI tool to support building and maintaining Yevis workflow registry
• Yevis Getting Started: the document for Yevis system installation and usage
• Yevis Getting Started Ja: 日本語での Yevis system の使い方

Development

Launch the development server:

$ npm run dev
> yevis-web@0.0.0 dev
> vite
  vite v2.8.3 dev server running at:

  > Local: http://localhost:3000/
  > Network: use `--host` to expose

Build and Deploy

See Vite - Guide - Deploying a Static Site as a reference.

Build and local preview:

$ npm run build
$ npm run preview

---

To manage the yevis-web, describe a .env file as follows:

VITE_WF_REPO=ddbj/yevis-workflows
VITE_WF_REPO_GH_PAGES_BRANCH=gh-pages
VITE_TRS_ENDPOINT=https://ddbj.github.io/yevis-workflows/

As an explanation of these variables:

• VITE_WF_REPO: GitHub repository deployed by yevis-cli.
• VITE_WF_REPO_GH_PAGES_BRANCH: A branch name of the GitHub repository deployed by yevis-cli.
• VITE_TRS_ENDPOINT: An endpoint of the GA4GH Tool Registry Service (TRS) API. Usually, an endpoint of GitHub Pages.

This example is set with default values. Create a .env file and set them to change them.

---

To deploy yevis-web to GitHub Pages, application base needs to be set. (See Vite - Guide - GitHub Pages as a reference)

Pass the environment variable YEVIS_WEB_BASE to set base at build time:

$ YEVIS_WEB_BASE=/yevis-web/ npm run build
$ YEVIS_WEB_BASE=/yevis-web/ npm run preview

---

Then deploy to GitHub Pages using npm - gh-pages, etc.

$ npm install -g gh-pages
$ gh-pages -d ./dist

License

Apache-2.0. See the LICENSE.