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

mediacentral-service-rest-bridge-toolkit

v1.0.4

Published

Toolkit to generate platfrom facades for REST services

Downloads

3

Readme

Mediacentral service rest bridge toolkit

Generates platform bridge service that acts as a facade for external REST service

Motivation:

  1. Expose external REST service into the platform
  2. Controll the access to the API via secure gateway
  3. ACL vi IAM

Install the package

Install the service rest bridge toolkit from npmjs

npm i -g mediacentral-service-rest-bridge-toolkit

Usage

Step 1 - Create or obtain the RAML file for your RESTful service

Create RAML definition for your API.

See examples in ./RamlSamples folder.

Step 2 - generate your service

To see the generatr usage help run it without parameters

mediacentral-service-rest-bridge-toolkit

or

mediacentral-service-rest-bridge-toolkit --help

To generate the service provide the path to the RAML file and output folder

mediacentral-service-rest-bridge-toolkit -r ./NetflixConductor.raml -o ./netflix-confuctor

To generate the service exposed via upstream specify the option

mediacentral-service-rest-bridge-toolkit -r ../NetflixConductor.raml -o ./netflix-confuctor -u true

Step 4 - build the docker image for your service

Build the image

docker build -t netflix-conductor:1.0 .

Step 5 - run your service

docker run --name netflix -d -t -e ACS_GATEWAY_HOST=<PLATFORM_HOST> -e BASE_URI=<SERVICE_HOST> netflix-conductor:1.0

Extensibility

Service is generated based on the serviceDefinition object created as part of RAML interpretation.

The code is generated using ejs templates. You can modify or create new teamplates according to your needs.

After service is generated you can use it as a foundation and add/change/modify the service logic.

FAQ

Why am I seeing 'Authentication error: Client IP is not allowed either by gateway or service policy'?

You'll need to make sure the IP mask is open on the gateway

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