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

replicated-scribe

v1.0.0

Published

update a replicated yaml's docker tag(s) in a GitHub repository

Downloads

12

Readme

Replicated Scribe

Built to update docker tags in a replicated yaml programmatically; most likely from the context of CI post-build.

Build Status Coverage Status Conventional Commits

Q. Why not just make a node script? A.: The prospect of maintaining a node script across 20+ repos that is subject to change is yuck city. Plus there's not a great way to test that mess.

CLI

Note: the a Github API Token providing write access should be set to the environment variable GITHUB_API_TOKEN

replicated-scribe updateTag --repo=repoSlug --filePath=./path/to/yaml --image=anDockerImage --tag=newTag --branch=branchName

Allows for CI builds to update a replicated.yaml in a branch to make use of a newly available Docker image.

  • repo - the slug should be in the form of userName/repoName
  • branch - the branch name to push the change to
  • filePath - the path (relative to the repo) to the replicated.yaml file
  • image - the Docker image (as specified) in the yaml file
  • tag - the new tag to apply (this is under a version property in the yaml)

branch defaults to "update-docker-image" and filePath defaults to "./replicated.yaml" when those arguments are not provided.

The result of this command, when successful, will be a commit to the branch on the specified repository with the version property changed to the new tag value for any Docker image matching the image argument.