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

gdeployer

v1.4.0

Published

Automated deployment tool

Downloads

65

Readme

gdeployer

Automated deployment tool - nodejs library

NPM

Install

$ npm install -g gdeployer

Usage

Usage: gdeployer [options] [dir]

Options:
    -h, --help            output usage information
    -V, --version         output the version number
    -c, --config <n>      config file path, relative to repository path (default gdeployer.json)
    -r, --repository <n>  repository name (default origin)
    -b, --branch <n>      branch name (default master)
    -f, --from <n>        deploy version from (branch || tag) (default branch)
    -t, --tag <n>         deploy version from tag name
    -e, --export <n>      reletive path from deploy path, where to export version file

eg

$ gdeployer --help
$ gdeployer --version
    
# deploy latest code from branch
$ gdeployer --config configs/production.json --repository origin --branch develop --from branch /repo/path
    
# deploy code from latest tag
$ gdeployer --config configs/production.json --from tag /repo/path
    
# deploy code from specific tag
$ gdeployer --config configs/production.json --tag 0.5.0 /repo/path

# export version name and timestamp to a file
$ gdeployer --config configs/production.json --export ./public /repo/path

Config

Create gdeployer.json config file and put to repository root directory

Config file options:

{
  "destinationPath": "deployment/path",
  "versionsToKeep": 4,
  "changeFileOwner": "www",
  "tasks": {
    "before": [
      "echo before live task"
    ],
    "after": [
      "echo after live task"
    ]
  }
}

License

(The MIT License) see LICENSE file for details...