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

nginx-vhosts

v0.0.8

Published

Programmatically add or remove vhosts to a running Nginx instance

Downloads

17

Readme

nginx-vhosts

NPM

Programmatically add or remove vhosts to a running Nginx instance.

To use this you should have your Nginx configuration file set up such that the http section has a include directive for all .conf files in a certain folder on your machine, e.g.:

http {
    ##
    # Virtual Host Configs
    ##

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
}

The machine configured with the configuration about would use either /etc/nginx/conf.d/ or /etc/nginx/sites-enabled/ as the confDir below. Note that the official Ubuntu PPA for Nginx has it configured this way by default.

See also:

  • https://github.com/maxogden/install-nginx-on-ubuntu
  • https://github.com/maxogden/nginx-reload

api

var vhosts = require('nginx-vhosts')(opts, onStopStart)

onStopStart is passed to and called from nginx-reload

var vhosts = require('nginx-vhosts')(opts, function running(isRunning) {
  // isRunning is a boolean, true if nginx is running, false if it is not
  // this function will get called whenever nginx stops or starts
  // note: .reload() does not trigger this function, as nginx does not
  // actually stop during a configuration reload
}

opts defaults to:

{
  confDir: '/usr/local/etc/nginx/conf.d/',
  pidLocation: '/var/run/nginx.pid'
}

vhosts.write(opts, cb)

vhosts.write({
  name: 'test',
  port: '8080',
  domain: 'test.local'
}, function(err, stdout, stderr) {
  // err, stdout, and stderr from the nginx configuration reload
})

This writes a new configuration file to the configuration directory and then tells Nginx to reload its configuration. In the above example it would configure Nginx to proxy requests from test.local to localhost:8080

You can also supply your own config file:

vhosts.write({
  name: 'test',
  config: 'upstream foo { server 127.0.0.1:8080 } ...'
}, cb)

Note: it may take Nginx a few seconds to finish reloading the configuration after the callback is called.

vhosts.remove(name, cb)

vhosts.remove('test', function(err, stdout, stderr) {
  
})

This removes a configuration file and tells Nginx to reload its configuration.

Note: it may take Nginx a few seconds to finish reloading the configuration after the callback is called.

run the tests

There are integration tests available, provided you have the following things set up:

  • your nginx is configured to store a pid file in '/var/run/nginx.pid'
  • your nginx is configured to include confs for http from /usr/local/etc/nginx/conf.d/
  • you have test.local in your /etc/hosts as an entry for localhost
npm install
sudo npm test