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

nodeploy

v0.3.6

Published

Deploy a commit after a successful build

Downloads

12

Readme

nodeploy Build Status

Automatic deployment script to facilitate deployment of a Node application to a production server after a successful build.

First it pulls in the successful build from git, and installs dependencies. Then it takes a copy to the releaseDir (defaults to $HOME/relases), copies the diff to the deployDir and finally restarts the app as specified in restartService run-script in package.json.

Required options

The following options are required - also, every directory must exist! (this should probably be changed, so the directory simply is created if it doesn't exist).

branch

Which branch to deploy. Should probably always be the branch containing the successful build - e.g. $TRAVIS_BRANCH.

commit

Which commit to deploy. To deploy the successfully build commit from Travis, use $TRAVIS_COMMIT.

repoDir

Directory containing the git repository.

deployDir

Directory containing the app. Files in this directory will be changed to match the new release.

Note

  • Remember to create a deploy key and add to github.
  • --releaseDir defaults to $HOME/releases
  • All directories must exist.

Usage example

Using ssh with an authorized_keys entry like(travis pubkey gives you the repository's public key):

command="deploy $SSH_ORIGINAL_COMMAND",no-port-forwarding,no-X11-forwarding,\
no-agent-forwarding,no-pty ssh-rsa AAAA...==

Put the following in your .travis.yml file - this should work for private repository's build by travis-ci.com.

after_success:
  - ssh -o StrictHostKeyChecking=no [user@]hostname "deploy -b $TRAVIS_BRANCH -c $TRAVIS_COMMIT --repoDir <path> --deployDir <path>"