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 🙏

© 2025 – Pkg Stats / Ryan Hefner

smesh

v0.1.2

Published

manage a mesh of docker and etcd hosts

Downloads

9

Readme

smesh

manage a mesh of etcd hosts

Smesh

install

First - ensure your hostname is set correctly.

Then install docker.

$ wget -qO- https://raw.github.com/binocarlos/docker-install/master/bootstrap.sh | sudo bash

if you are using vagrant - run this command to allow the vagrant user access to the docker socket:

$ sudo usermod -aG docker vagrant

You will then need to restart your command line session.

Then pull the required images:

$ docker pull binocarlos/smesh
$ docker pull coreos/etcd

usage

To make a smesh cluster you first need an etcd token:

node1:~$ export SMESH_TOKEN=$(docker run --rm binocarlos/smesh token)

Then set the SMESH_IP variable to the IP address of an interface accesible by other members of the cluster:

node1:~$ export SMESH_IP=192.168.8.120

Then we can use these values to boot an etcd server

node1:~$ $(docker run --rm binocarlos/smesh start --token $SMESH_TOKEN --hostname $HOSTNAME --address $SMESH_IP)

And then on the other servers:

node2:~$ SMESH_TOKEN=https://discovery.etcd.io/f349523a1502f4e53fabd2b9df22bd72
node2:~$ SMESH_IP=192.168.8.121
node2:~$ $(docker run --rm binocarlos/smesh start --token $SMESH_TOKEN --hostname $HOSTNAME --address $SMESH_IP)

Now there is a cluster of 3 etcd servers running - you can run etcdctl on one of the servers:

node1:-$ docker run --rm binocarlos/etcdctl --peers 192.168.8.120:4001 set /apples hello
node1:-$ docker run --rm binocarlos/etcdctl --peers 192.168.8.120:4001 ls / --recursive

to stop the smesh container:

node1:~$ docker stop smesh && docker rm smesh

manual peers

You can use the --peers option rather than --token if you want to manually co-ordinate the cluster:

node1:~$ $(docker run --rm binocarlos/smesh start --hostname $HOSTNAME --address 192.168.8.120 --peers boot)
node2:~$ $(docker run --rm binocarlos/smesh start --hostname $HOSTNAME --address 192.168.8.121 --peers 192.168.8.120:7001,192.168.8.122:7001)
node3:~$ $(docker run --rm binocarlos/smesh start --hostname $HOSTNAME --address 192.168.8.122 --peers 192.168.8.120:7001,192.168.8.121:7001)

license

MIT