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

navy-clock-install

v1.1.2

Published

Navy Order to install a Clock project for deployment

Downloads

6

Readme

Clock Install Order

This is an Order which is used by Captains as part of the Navy deployment suite.

It does the following actions:

  • Symlink the application build directory to its final location
  • Generate upstart scripts for the applications services
  • Run the Restart order on this captain

This order assumes that the following configuration keys have been added to the Admiral for the application you are trying to prepare:

  • nodeVersion: Version of node this project should use to execute
  • buildDir: Location of the directory containing your applications build directory
  • services: Object containing thes services that this application has. The key forms the suffix of the name of the upstart jobs e.g node-myproject-staging-<-service->. The value is the relative path to the start script of the service
  • env (optional): Any custom environment variables that need to be set at run time

An example Admiral application configuration might look like:

{ "name": "My Application"
, "appId": "myApp"
, "buildDir": "/tmp/build"
, "nodeVersion": "0.10.22"
, "services":
  { "admin": "admin/app.js"
  , "site": "site/app.js"
  , "api": "api/app.js"
  , "message-bus": "message-bus.js"
  }
, "env":
  { "EXAMPLE_VAR": "example env var"
  }
}