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-build-layers

v0.0.3

Published

Command line helper to simplify building docker images that have multiple layers.

Downloads

4

Readme

docker-build-layers

Command line helper to simplify building docker images that have multiple layers.

Why

Sometimes you want to layer your docker images to speed up build process when you don't have to go through every step

Install

npm install --save-dev docker-build-layers

Usage

dbl -h

dbl relies on docker command being present in your PATH.

  1. Create docker-build-layers-config.json file with content similar to:

    {
      "prefix": "prefix-string/",
      "afterEach": "gcloud docker push <%= tag %>",
      "images": {
        "base-image": {
          "version": 5,
          "dockerfile": "./Dockerfile-base-image"
        },
        "server": {
          "version": 3,
          "dockerfile": "./Dockerfile-server",
          "isTemplate": true,
          "baseimage": "base-image"
        }
      }
    }
    • prefix: string (optional) A string to prepend to all image names and baseimage names
    • afterEach: string (optional) A command that will be executed after each image build. The command can be a lodash template. A locals of {tag: number} will be applied when compiling the template. tag is the tag of the image just built.
    • images A object of image names to their configurations
      • version: number The version portion of a image tag. The version number will be incremented every time the image it built. When generating an image tag, the version number will be prefixed with a v character. E.g. if image name is demo-image, version is 3, the final tag will become demo-image:v3.

      • dockerfile: string The path to dockerfile of current image.

      • baseimage: string (optional) The baseimage name. Name must point to image configurations under images. This must be specified when isTemplate is true.

      • isTemplate: boolean = false (optional) If true, dockerfile will be treated as a lodash template. A locals of {baseimage_version: number} will be applied. You are responsible to use <%= baseimage_version %> in your dockerfile template. E.g.

        FROM baseimage-name:v<%= baseimage_version %>
        
        ADD index.js /app/index.js
        CMD ["node", "/app/index.js"]

        docker-build-layers will find the baseimage_version according to provided baseimage and use that image configuration's version.

  2. Run dbl -l to see a list of available images to build.

  3. Run dbl -b <image-name> to build the specific image. Any image with baseimage configuration equals to the name of built image will also be built. The baseimage_version of child images will reflect the new parent image version.

  4. At the end docker-build-layers-config.json will be updated with new versions. It is recommended to commit this file to source control.