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

docker-cache

v1.1.2

Published

Monitor docker instance(s) and populate redis for centralized reference and monitoring

Downloads

11

Readme

Docker Cache

Full Disclosure: This project was inspired by Sam Alba's GoLang Docker Cache project and most of the code was ported from Go over to Node.JS. A lot of the readme is borrowed from the https://github.com/samalba/docker-cache because it uses the same data pattern. samalba's project is no longer maintained and Node.JS played more to my strengths, hence the rewrite. Much of this readme is also from his original project and/or inspired by it.

The purpose of the docker cache application is to monitor docker instances and populate a redis server with information about the containers and images that exist on that docker instance. Docker Cache can be used to monitor just one or multiple docker instances provided they are accessible via tcp port.

Why?

Docker-Cache brings full visibility on what is happening on your cluster in real-time:

  • How many Docker hosts are running?
  • How many containers on each of them?
  • What is the configuration for each container?

Those data are updated in realtime and you can access them quickly in one location (Redis).

The Cache server is volatile, you can lose the dataset, the data will be repopulated quickly as long as there is a Cache server running.