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

superdocker

v0.0.6

Published

Superdocker allows you to manage multiple docker configurations easily

Downloads

3

Readme

superdocker

Superdocker allows you to manage multiple docker hosts easily. This is not for clusters, this is for working with different environments.

For example, let's say you have three environments that you use:

  • local boot2docker install (boot2docker)
  • single network docker host (local)
  • remote swarm cluster (remote)

If you wanted to use your local docker client with each of these, you'd have to keep changing your environment variables or pass the host via -H. But you don't have to live this way, you can superdocker it.

Install

Install via npm:

npm i -g superdocker

Optionally, create a symlink to save you time:

ln -sf /usr/local/bin/superdocker /usr/local/bin/sdocker

Upgrading

Upgrade via npm also:

npm update -g superdocker

Check it's uptodate:

npm outdated -g --depth=0

Create a config file

You'll need to create a config file in your home directory:

touch ~/.superdocker

In this, place your configuration:

[boot2docker]
    DOCKER_CERT_PATH=/Users/adam/.boot2docker/certs/boot2docker-vm
    DOCKER_TLS_VERIFY=1
    DOCKER_HOST=tcp://192.168.59.103:2376

[local]
    DOCKER_HOST=tcp://192.168.1.100:2375

[remote]
    DOCKER_HOST=tcp://swarm.yourhost.com:2375

Optionally, create a default configuration:

[default]
    DOCKER_CERT_PATH=/Users/adam/.boot2docker/certs/boot2docker-vm
    DOCKER_TLS_VERIFY=1
    DOCKER_HOST=tcp://192.168.59.103:2376

All that happens is if you type superdocker ps (no configuration), it'll use the default. If you don't provide a configuration, and there is no default, then you'll get a pleasant message telling you as much.

Check it's working

You can now run superdocker <configuration> <commands>, which is the same as docker <commands>:

$ superdocker boot2docker info
Containers: 12
Images: 405
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 429
 Dirperm1 Supported: true
Execution Driver: native-0.2
Kernel Version: 4.0.3-boot2docker
Operating System: Boot2Docker 1.6.2 (TCL 5.4); master : 4534e65 - Wed May 13 21:24:28 UTC 2015
CPUs: 8
Total Memory: 1.957 GiB
Name: boot2docker
ID: CDUR:6WLL:EYYH:YQPH:FAB5:FRFY:L3MR:SDJN:PYZF:ROX2:6FQG:6AD5
Debug mode (server): true
Debug mode (client): false
Fds: 12
Goroutines: 16
System Time: Wed Jun  3 09:32:06 UTC 2015
EventsListeners: 0
Init SHA1: 7f9c6798b022e64f04d2aff8c75cbf38a2779493
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker

Troubleshooting

Make sure your docker client version matches your docker server version, or you'll have a bad time.

$ superdocker remote info
FATA[0000] Error response from daemon: client and server don't have same version (client : 1.18, server: 1.14)

## Licence

MIT