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-api-nodejs

v0.10.5

Published

Docker API for NodeJS

Downloads

30

Readme

Docker API NodeJS

Since docker-modem is not really useable currently especially with the new cluster volumes, this project aims to integrate all of the features that docker-modem does not.

Usage

Setup

import { Modem } from "docker-api-nodejs";

const modem = new Modem(<path-to-docker-socket>);

Model

The project uses the responses from docker in a handle model. That means that for a basic request such as listing object like volumes you will get the exact same response as you would when you call the socket directly.

Hoever if you want to get specific information on an object e.g. inspecting its content more closely you can create a handle for that object like so:

Handle for a volume:

const volumeHandle = new VolumeHandle(<modem>, <name of the volume>);
const clusterVolumeHandle = new ClusterVolumeHandle(<modem>, <id of the clusterVolume>);

Create functions always return a handle:

const handle = await Configs.create(<modem>, <configSpec>);

Alternatively you can always get a handle on an object by calling its from<Object> function:

const handle = NodeHandle.fromNode(<modem>, <node-object>);

From there on you can (if the object supports it) inspect, remove, update, ...

The parameters for every operation are based on the official docker api documentation

Stacks

Stacks are handled a little different as there is no endpoint in the docker socket to connect to. See here for more details

Testing

Testing assumes a clean docker environment with no objects other than the standard. So if you want to test the project keep that in mind

License

Licensed under the Apache license, version 2.0 (the "license"); You may not use this file except in compliance with the license. You may obtain a copy of the license at:

http://www.apache.org/licenses/LICENSE-2.0.html

Unless required by applicable law or agreed to in writing, software distributed under the license is distributed on an "as is" basis, without warranties or conditions of any kind, either express or implied. See the license for the specific language governing permissions and limitations under the license.