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

@auto-it/docker

v11.3.0

Published

Facilitates publishing built images to a Docker Registry.

Downloads

997

Readme

Docker Plugin

This plugin automates tagging and publishing images to a docker registry.

Prerequisites

To publish to a docker registry, you'll first need to authenticate with the target registry. For example, the Docker Login Action for GitHub, or the withRegistry helper in Jenkins.

Installation

This plugin is not included with the auto CLI installed via NPM. To install:

npm i --save-dev @auto-it/docker
# or
yarn add -D @auto-it/docker

Usage

IMPORTANT: You must first must build the desired image to publish.

The following options are available for this plugin:

|option|required|default|environment variable|description| |-|-|-|-|-| | image | X | | IMAGE | The image ID, digest, or tag of the locally available image to tag and publish (must be built before this plugin is run) | | registry | X | | REGISTRY | Docker registry to publish to | | tagLatest | | false | TAG_LATEST | Tag latest release with latest tag | | tagPullRequestAliases | | false | TAG_PULL_REQUEST_ALIASES | Tag pull requests with pr-<number> tag | | tagPrereleaseAliases | | false | TAG_PRERELEASE_ALIASES | Tag prerelease branches | prereleaseAliasMappings | | {} | | Tag prerelease branches with different names (e.g. {"develop": "next"}) |

Example 1: Tag releases only

{
  "plugins": [
    ["docker", { "registry": "ghcr.io/my/app", "image": "someLocalImage:myLocalTag" }]
    // other plugins
  ]
}

This will publish releases from the local docker image someLocalImage:myLocalTag to: - ghcr.io/my/app:<version>

Example 2: Tag latest releases

{
  "plugins": [
    ["docker", { "registry": "ghcr.io/my/app", "image": "someLocalImage:myLocalTag", "tagLatest": true }]
    // other plugins
  ]
}

This will publish releases from the local docker image someLocalImage:myLocalTag to: - ghcr.io/my/app:<version>

  • ghcr.io/my/app:latest

Example 3: Tag Prereleases (with Custom Tags)

{
  "prereleaseBranches": ["develop", "someOtherPrereleaseBranch"],
  "plugins": [
    ["docker", { "registry": "ghcr.io/my/app", "image": "someLocalImage:myLocalTag", "tagPrereleaseAliases": true, "prereleaseAliasMapping": { "develop": "next" } }]
    // other plugins
  ]
}

For pushes to develop branch this will create the following tags:

  • ghcr.io/my/app:<prereleaseVersion>
  • ghcr.io/my/app:next

For pushes to someOtherReleaseBranch this will create the following tags:

  • ghcr.io/my/app:<prereleaseVersion>
  • ghcr.io/my/app:someOtherReleaseBranch

Example 4: Tag Pull Requests

{
  "plugins": [
    ["docker", { "registry": "ghcr.io/my/app", "image": "someLocalImage:myLocalTag", "tagPullRequestAliases": true }]
    // other plugins
  ]
}

If this is run against a pull request the following tags will be created against someLocalImage:myLocalTag:

  • ghcr.io/my/app:<canaryVersion>
  • ghcr.io/my/app:pr-<prNumber>