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

cloudux-starter-kit-service

v2.2.5

Published

CloudUx starter kit for creating NodeJS based services

Downloads

7

Readme

pipeline status coverage report

MediaCentral CloudUX Service Starter kit

Starter kit for creating a service for CloudUX

Getting started

To use this application you will need following tools:

  1. running MediaCentral | Cloud UX 2018.6 machine
  2. node.js and npm
  3. proxy ball for more information check FAQ

Installation:

Using npm type in your CLI:

npm install -g cloudux-starter-kit-service

Run from CLI:

In your CLI type:

  • cloudux-starter-kit-service to create service with creator.
  • cloudux-starter-kit-service --help Do display help page.

Installation can be executed by providing flags to your toolkit.

Usage :

  • -N New Service
    • -n Project name (required)
    • -d Project description (required)
    • -i MediaCentral server host IP (required)
    • -r Realm (required)
    • -v Service version (required)
    • -m File with methods of you service (optional)
    • -p project path (optional)
  • -B Build Service
    • -p path to a project root (required)
    • -n project name (Should match project/src/project.json under identity.appName) (required)
    • -z app version should match project/src/project.config.json version field (required)
    • -o organization should match project/src/project.config.json organization field (required)
    • -i appID should match project/src/project.config.json appID field (required)
    • -j appSecret should match project/src/project.config.json appID field (required)
    • -d developerID should match project/src/project.config.json developerID field (optional)
    • -x https_proxy For docker build (optional)
  • -I Build DockerImage
    • -p project path (required)
    • -n project name (Should match project/src/project.json under identity.appName) (required)
    • -z app version should match project/src/project.config.json version field (required)
    • -o organization should match project/src/project.config.json organization field (required)
    • -i appID should match project/src/project.config.json appID field (required)
    • -j appSecret should match project/src/project.config.json appID field (required)
    • -x https_proxy For docker build (optional)
    • -d developerID should match project/src/project.config.json developerID field (optional)
  • -P Publish project
    • -p path to a project root (required)
    • -n project name (Should match project/src/project.json under identity.appName) (required)
    • -z app version should match project/src/project.config.json version field (required)
    • -o organization should match project/src/project.config.json organization field (required)
    • -k privateKeyPath should match project/src/project.config.json privateKeyPath field (required)
    • -i appID should match project/src/project.config.json appID field (required)
    • -j appSecret should match project/src/project.config.json appID field (required)
    • -x https_proxy For docker build (optional)
    • -d developerID should match project/src/project.config.json developerID field (optional)
    • -s password to ssh private key (optional)

API

const kit = require('cloudux-starter-kit-service')
kit(options)
kit({options})
  • For new service:
    • name -- project name (required)
    • project_description -- project description (required)
    • project_hostIp -- MediaCentral server Ip (required)
    • relm -- realm (required)
    • version -- Version of your service (required)
    • project -- path to save project (optional)
    • project_service_methods_file -- File with methods of you service (optional)
  • Building Service:
    • build -- set build to true to build your project (required)
    • project -- path to save project (required)
    • name -- project name (required)
    • https_proxy -- For docker build (optional)
    • config -- Object with fields :
      • version -- Version of your service (required)
      • organization -- Name of organization (required)
      • developerId -- Your developer ID (optional)
  • Publish Service:
    • publish -- set publish to true to publish your project (required)
    • build -- set build to false (required)
    • project -- path to save project (required)
    • name -- project name (required)
    • password -- password to your ssh key (optional)
    • https_proxy -- For docker build (optional)
    • config -- path to a project config file (optional if the config is project/src/project.config.json)
      • version -- version of your app (required)
      • organization -- name of you organization (required)
      • privateKeyPath -- Path to your private key (required)
      • appID - your Application ID (required)
      • developerID -- your developer ID (optional)
  • buildImage -- set buildImage to true to build image of your project
    • project -- path to your project (required)
    • name -- path to your project (required)
    • https_proxy -- For docker build (optional)
    • config -- path to your project (required)
      • version -- App version (required)
      • appID - your Application ID (required)
      • appSecret - your Application Secret (required)
      • organization -- Organization name (required)
      • developerId -- Organization name (optional)

FAQ

Why am I getting '404 Not Found: proxy-bal'?

You'll need to include proxy-bal module.

How to include proxy-bal

Proxy-bal is package accesible only for developers with a Avid developer account
Steps include proxy-bal:

  1. Download proxy-bal package from https://my.avid.com/cpp/sdk/apc (Avid Platform Connector Node)
  2. Extract downloaded files
  3. Enter the extracted directory and then node_modules directory
  4. Extract proxy-bal.tgz file
  5. Rename package directory to proxy-bal
  6. Copy the proxy-bal directory to node_modules in service directory
  7. Open command line inside proxy-bal directory and type npm update

Why my service won't connect because of 'unauthorized token'?

Because you need to receive appID and appSecret and paste it to your project.config.json. Check Development Guide to find out how optain AppID and AppSecret.

Check our CloudUX examples on Avid-Technology Github

Check our Quick Start for CloudUX

Latest Changes

[2.2.4] (2023-02-17)

Bug Fixes

  • Umigrate to helm v3.

[2.2.3] (2022-12-07)

Bug Fixes

  • Update dependencies. Removed critical vulnerabilities.

[2.2.2] (2022-07-13)

Bug Fixes

  • config yaml file now is optional and not needed for the feature-pack installation without env variables.

[2.2.1] (2022-07-12)

Bug Fixes

  • Fixed env variables.

2.2.0 (2019-11-14)

Features

2.0.3 (2019-10-20)

Bug Fixes

  • DTKT-729 feature install fails because of wrong configmap template variable (e0e0e0c)