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

http-multi-site

v0.0.2

Published

http-multi-site ============

Downloads

3

Readme

http-multi-site

Stability - 2 Example Usage for Linux

An example layout for handling multiple website/services using nodejitsu/forever module. Modify proxy.json to match your layout for webservices urls. Modify bin/nodejs file ROOT_DIR to match the location of your http-multi-site installation, and copy bin/nodejs to /etc/init.d to auto-start and stop on system reboot. Each website/webservice should be a nodejs http server (ex. express, http, etc.) that can be launched from node.

proxy.json contents
{
  "hostnameOnly": "true", //required to be true for nodejitsu/forever to handle the hostport option properly
  "domains": {
    "example1.com": { //domain name for site 1
       "hostport": "localhost:3003", //url location for webservice/site 1
       "dir": "/home/nodejs/websites/example1.com" //full path to the root directory of example1.com
    },
    "example2.com": { //domain name for site 2
       "hostport": "localhost:3002", //url location for webservice/site 1
       "dir": "/home/nodejs/websites/example2.com" //full path to the root directory of example2.com
    },
    "example3.com": { //domain name for site 3
       "hostport": "localhost:3001", //url location for webservice/site 1
       "dir": "/home/nodejs/websites/example3.com" //full path to the root directory of example3.com
    }
  }
}