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

samson-cli

v0.2.4

Published

Samson command line interface

Downloads

10

Readme

Samson CLI

Command line utility to manage deploys in Zendesk's Samson

Requirements

git and Node.js >=4 with npm.

How to install

Just install the samson-cli globally.

npm install -g samson-cli

Configuration

You should create a samsonrc.json file in each of your project directories. samson will look for it when you run the tool. The file should have this shape:

{
  "url": "http://my-samson-url.com",
  "project": "myProjectName",
  "auth": "<authentication cookie>",
  "samson": {
    "production": true
  }
}

The auth key expects the value of your Samson session cookie. We still don't have a better authentication system (perhaps based in a Samson user token) due to Samson API limitations.

Usage

samson <command> [options...]

Commands

deploy

Performs a deploy of a branch or tag to a stage.

Syntax:

samson deploy <stage> <reference>

Where stage is a valid stage (see samson stages) and reference is a branch, tag or commit SHA.

Example:

samson deploy staging master

deploys

Prints the last 15 deploys.

Syntax:

samson deploys

builds

Prints the last builds.

Syntax:

samson builds

stages

Prints the configured stages.

Syntax:

samson stages

Options

-c | --config

You can specify a custom config, in json format

Syntax:

samson <command> -c '{ "url": "http://my-samson-url.com", ...}'

Note: You may not need to have a samsonrc.json file in order to use the program if the config is specified this way, but some autocompletion features will be disabled

To do

  • [ ] Authenticate using Samson token instead of the session cookie
  • [ ] Better help and readme
  • [ ] Show deploy output
  • [ ] Be able to specify a custom samsonrc.json
  • [ ] Fail when no samsonrc.json is found
  • [ ] Manage configuration defaults