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

app-deploy

v0.6.3

Published

Deployment helper

Downloads

13

Readme

app-deploy

Thrifty incremental deploys.

Rough algorithm description:

  1. Figure out which files were changed since last deploy (through git diff).
  2. Figure out which tasks should be executed.
  3. Execute tasks.

Installation

npm install -g app-deploy

Usage

Deploy app to production:

ad deploy production

Looks nice but first you need to configure!

Initial notices

app-deploy is dedicated to do incremental deploy of already running app/service, first time you should setup and run your application manually.

It's not dedicated to deploy "new app instances".

Triggers deploy config

Triggers config must be located in project root (and must be named app-deploy.json). It consists of simple rules and triggers which are used to figure out how to deploy app.

Sample config describes conditions and triggers for app-deploy cli util:

{
	"triggers": {
		// if bower.json was changed since last deploy then execute "bower install"
		"bower.json"   : "bower intall",

		// if bower.json was changed since last deploy then execute "npm install"
		"package.json" : "npm intall",

		// if there are any changed or added fiels matching database/** globa pattern
		// then execute "knex migrate:latest"
		"database/**"  : "knex migrate:latest",

		// if any local dependency which are required by any file under web/**
		// were changed then execute "pm2 restart all"
		"+web": "pm2 restart all"
	}
}

Each "trigger" consits of condition (glob or requires matching pattern) and shell command
which will be executed if condition is true (if files diff since last deploy matches condition pattern)

Add remote server (for remote deploy)

Add remote:

ad remote add <remote name> <ssh connection string> [--env]

Example adding my-localhost-server remote:

ad remote add my-localhost-server [email protected]:/var/www/application --env="override_some_stuff=123"

To work with remote deploys you must configure key-based ssh auth to work from your local machine to remote server.
How To Configure SSH Key-Based Authentication on a Linux Server

Now we are ready to deploy!

ad deploy my-localhost-server

License

MIT