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

stack-components

v0.0.1

Published

run specific components of a large project

Downloads

2

Readme

node-host-components

run components of a large project on separate machines

Example

Place your existing node application in a sub directory, and create a server.js file so it is relative to the other files like this. Let's assume we started with two node modules or servers that work together (api and application) We handled deployment and version control of these applications separately because, well, we had to, but it's about to get a lot easier.

├─┬ api
│ ├── server.js
│ └── .git
├─┬ application
│ ├── server.js
│ └── .git
├── .git
├── deploy.js
├── network.json
└── server.js

Create a very simple network.json file. The important part when creating components here is to name the directory that holds the component the same as in the network.json

network.json


{
  "api": { },
  "application": { }
}

Now add to the new server.js

server.js


var host_component = require('node-host-components')
var network = require('network.json')

host_component({ 
  network: network 
})

Before you deploy, set your hostname so it contains the name of the component you want to run on the machine. Avoid overly generalized names and collisions.

› hostname
  spinoza-api

Since our hostname contains api and this matches with our network.json and subdirectory named api -- a call to node server will trigger the api component to load. Now you can deploy the same source code to every machine for maximum DRYness.

Let's setup the application machine too.

› hostname
  locke-application

Ok great, now lets go back and update our network.json file so it looks something like this. Now you can feel free to add more components to your system without a lot of complexity. Just remember to choose hostnames wisely.

network.json


{
  "api": { 
    "spinoza": {
      "public": "spinoza-api.joyent.us" 
    },
    "aquinas": {
      "public": "aquinas-api.joyent.us" 
    },
    "socrates": {
      "public": "socrates-api.joyent.us" 
    }
  },
  "application": {
    "locke": {
      "public": "locke-application.joyent.us" 
    }
  }
}

Finally, we deploy to all of our machines with a simple node deploy command using another npm module node-network-deploy.

deploy.js

var deploy = require('node-network-deploy')

deploy({
  network: require(__dirname +'/network.json'), 
  provider: 'joyent', // default
  username: 'node',  // default
  branch: 'master',  // default
  path: 'repo', // default
  port: 80 // default
})

Success!

License

MIT