npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@molgenis-experimental/molgenis-app-lifelines-webshop

v4.7.8

Published

## Install

Downloads

21

Readme

Lifelines webshop

Install

cp .lifelinesrc.example .lifelinesrc
yarn install
yarn run serve
  • i18n For development and testing you can add your translations to i18n.schemas.js For production make sure to add the translations to the molgenis entity Localization using lifelines-webshop as a namespace.

    tip: Use i18n.schemas.js to create the Localization entities. For msgid add the schema key (for example: "lifelines-webshop-sidebar-header") The namespace should be lifelines-webshop and than add all of the needed translations.

Common commands

yarn build     # Compile and minify
yarn test      # Run your tests
yarn lint      # Lints and fixes files
yarn test:e2e  # Run your end-to-end tests
yarn test:unit # Run your unit tests

Deployment (Kubernetes)

Ask Ops for help to setup kubectl and Rancher if you don't have them setup yet.

  • Deploy the lifelines-webshop Helm chart on Rancher. Write down the generated Molgenis token in the TRANSFORM section.

  • Install Molgenis commander

  • Add deployment/datasets directory to the dataset_folders section of ~/.mcmd/mcmc.yaml

  • Add deployment/resources folder to the resource_folders section of ~/.mcmd/mcmc.yaml

  • Configure Molgenis commander to run on the lifelines server

    mcmd config add host
    mcmd config set host
  • Set the ll_admin password in the lifelines script

    cp ./deployment/lifelines ~/.mcmd/scripts/
    vim ~/.mcmd/scripts/lifelines
    add user ll_admin --set-password *******
  • Proxy the Molgenis instance and follow the commander script to setup the server:

    kubectl port-forward svc/molgenis 8080:8080 --namespace lifelines-catalog-test
    mcmd run lifelines -i
  • Login as admin to Molgenis and add the TRANSFORM Molgenis token you generated earlier the Helm chart.

  • Go to the Transform pod on Rancher and test the Transform with:

kubectl create job manual-transform --from cronjob/transform --namespace lifelines-catalog-test

Dataflows

https://yuml.me/edit/e9dd81eb To transform the raw data to a format that can be used by this app, use the molgenis-py-lifelines-transform tool.

Workflow of the catalog

order states

Order process

order states

Production settings

A couple of things have to be configured in order to run this app in production:

  • vue.config.js Add a public path to specify the path on which the app is served.

    const packageJson = require('./package.json')
    
    ...
    module.export
      ...
      publicPath: process.env.NODE_ENV === 'production'
        ? packageJson.name + '/dist/'
        : '/',
  • package.json Add a scope for the package name to publish to a organisation scope on NPM.

    "name": "*scope*/molgenis-app-lifelines-webshop",

    Add the publish config with scope public, otherwise you cannot publish to NPM.

    "publishConfig": {
      "access": "public"
    },

    Add a target for webservers to resolve to.

    "main": "dist/index.html",

    Add directories to pick up when building for production.

    "files": [
      "dist",
      "src"
    ],
  • route.ts Change the default base when you want to serve your app on a path other than /

    export default new Router({
    ...
    base: process.env.NODE_ENV === 'production' ? packageJson.name : process.env.BASE_URL,