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

cs-manager

v8.0.12

Published

Backend in charge of handling API calls, GQL, and ACL logic related to CS. General flow of request is received from Gateway or directly from service (i.e. portal). There will be ACL middleware checks and if user has proper access on said charge station an

Downloads

10

Readme

CS Manager

Backend in charge of handling API calls, GQL, and ACL logic related to CS. General flow of request is received from Gateway or directly from service (i.e. portal). There will be ACL middleware checks and if user has proper access on said charge station and action, the action will be carried out.

Dependencies

  • CS manager is not a standalone service and depends on different tables and services.

  • ACL Service - Used for middleware of user privileges

  • CS Database - Holds information for

  • Kafka - Messaging service used for issuing out requests

  • Consul - DNS, Service finder of some sort.

  • Depending on the testing you are doing you will you need other services. Gateway, consul, etcd, etc.

Building & Running

npm install

npm start

  • Chances are low this will work out of the box. The is a useless bullet look below.
  • If you come across issues during install they may be related to node version. You can use nvm to get around this. nvm use 10 or to set as default nvm alias default 10 and node -v to confirm.
  • You need to have the replica set populated properly (I think). You need to follow the steps below to run the DB locally and run npm test to properly set up the replica set.
  • If you do not have config/local.coffee copy config/local.coffee.sample and rename.

Setting up dependencies

To simulate the environment on its own you need to set up the dependencies in Docker or to build and run dependencies from source.

  • To run ACL Service in Docker: ./path/to/script.sh

  • To run Kafka in docker: ./path/to/script.sh

  • For the Database, you will need to create a local instance and copy over database to local with a replica set. If you have mongo running already in Docker stop it firstly. Getting Mongo with replica set ./trust/the/script.sh. Run npm test to properly set up rs0. Staging data can be connected to staging-master:30106 and you will need to copy over the collections you need to local. If collections are named staging-xxx change to development-xxx. Best to ask which collections are actually needed for work you will be doing to not copy over unnecessary collections (e.g. user/express logs).