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

zaz

v0.1.0

Published

Simple Node.js deployment, Capistrano-style

Downloads

5

Readme

Zaz: Simple Node.js deployment, Capistrano-style

Build Status NPM version

Why?

In order to set up simple project deployment with minimum configuration/programming.

More opinionated than flexible

Currently, the tool conforms to the following assumptions:

  • the code is being fetched from a Git repositories, accessible from the remote servers;
  • ssh key (~/.ssh/id_rsa.pub) is being used for authentication;
  • the package.json has the following npm scripts described: start, status, stop, deploy (to use with Naught, for example);
  • some more.

Installation

sudo npm install -g zaz

NPM

Configuration

Place somewhere (in your project root, for example) a file named zaz.json with the following structure:

{
  "stages": {
    "staging": {
      "user": "<deployer username>",
      "git": "<git repo containing the code>",
      "path": "<where to put the folder structure on your remote server>",
      "hosts": [
        "<your remote staging host 1>",
        ...
        "<your remote staging host n>"
      ]
    },
    "production": {
      ...
    }
  }
}

Usage

zaz <stage> looks for zaz.json and performs the deployment according

Dependencies

Contributions

  • are welcome;
  • should be tested;
  • should follow the same coding style.

Keep it simple, minimum bells and whistles, please.

License

The MIT License

Copyright (c) 2014 Ruslan Bredikhin