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

@base-cms/travis-rancher-deployer

v1.0.3

Published

A project to automate deployments to a Rancher 1.6 private cloud via TravisCI

Downloads

20

Readme

travis-rancher-deployer

A project to automate deployments to a Rancher 1.6 private cloud via TravisCI

Usage

To use this project, you should install it as part of your build process. For example under yarn: yarn global add @base-cms/travis-rancher-deployer.

You can then use the deploy-to-rancher command from the CLI. The command expects the following arguments:

  • image: The docker image to deploy, e.g; base-cms/parcel-plug:v1
  • service: The Rancher service label value to target.
# travis.yml
deploy:
  -
    provider: script
    script: cd scripts/deploy.sh
    on:
      tags: true
      condition: "$TRAVIS_TAG =~ ^v[0-9]+\\.[0-9]+\\.[0-9]+$"
# scripts/deploy.sh
#!/bin/sh
yarn global add @base-cms/travis-rancher-deployer
deploy-to-rancher "myorg/my-image:${TRAVIS_TAG}" "what-to-upgrade"

This project uses envalid to ensure that the following required deployment parameters have been specified. You can set these in your Travis env matrix, or via the TravisCI repository settings.

RANCHER_URI=https://my_rancher_url/v2-beta/projects/my_project_id
RANCHER_ACCESS_KEY=my_access_key
RANCHER_SECRET_KEY=my_secret_key

Using the configuration above will search for services using a label of service=what-to-upgrade and upgrade them to myorg/my-image:${TRAVIS_TAG}.