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

nimbus

v0.0.28

Published

simple cloud deployment for node apps, follows convention, no lock-in

Downloads

115

Readme

Prereqs:

  • node.js >= 0.6 (with npm)
  • git
  • Foreman
  • Make
  • an account on heroku, joyent, azure, linode, or rackspace

What the user creates:

  • package.json
  • app code
  • git repository
  • .gitignore
  • Procfile
  • nimbus.json

What the user does:

$ nimbus list

lists all the targets defined in the nimbus.json file

$ nimbus provision serviceName

provisions the service at `serviceName`

- root: add keys to the remote system
- root: upgrade basic systems (build chain, etc)
- root: create user for the service
- local: render scripts for the service
- local: copy rendered scripts to the remote machine
- serviceuser: run the remote scripts

$ nimbus update serviceName

updates the service at `serviceName`
(for example, updating config files, environment settings...)
(should be non-destructive... no risk of losing user data)
(should be fast & not require a restart)

$ nimbus deploy serviceName [branch|hash]

deploys the git branch or hash specified to `serviceName`

- system does a git push to remote
- post-receive hook on remote copies the checked out codebase into a versions/{{gitHash}} directory
- post-receive hook then runs npm install
- if npm install goes okay, post-receive hook does an rsync between the new version and the /current directory running the app
- post-receive hook restarts foreman

TODO:

  • set NODE_ENV to production via .env.json