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

bouncy-forever

v0.0.1

Published

Wiring up bouncy and forever to allow multiple domain names to be mapped to different servers listening on different ports.

Downloads

3

Readme

bouncy-forever

Wiring up bouncy and forever to provide a streamlined service:

  1. Launch multiple servers(processes) and have them listen to different ports.
  2. Forward requests for multiple domains to the desired servers(processes).

Install

> npm install -g bouncy-forever

Usage

This package aims at simple setup for doing the job. There are only 2 steps in setting this up.

  1. Create a configuration file at ~/.bouncy-forever/config.json
  2. Run the bouncy-forever server: > bouncyforever

The configuration file (~/.bouncy-forever/config.json)

File structure:

{
  "cv.ycmjason.com": {
    "name": "cv",
    "start_script": "npm start",
    "base_dir": "~/Development/curriculum-vitae"
  },
  "ycmjason.com": {
    "name": "ycmjason.com",
    "start_script": "python server.py --prod --port=$PORT",
    "base_dir": "~/Development/ycmjason.com",
    "env": {
      "MAX_VISITOR": "16"
    }
  }
}

Do NOT specify env.PORT for your app since bouncy-forever will assign it to a free port.

This also means that your app should listen to env.PORT for bouncy-forever to work.

Alternatively, you can specify the port by using $PORT in your start_script entry. You could see this in the above example.

Command Line Interface (CLI)

To run the server:

> bouncyforever

`cv` launched and listening on port 38186...
`ycmjason.com` launched and listening on port 46606...

Mapping...
  cv.ycmjason.com:8080(cv) to port 38186
  ycmjason.com:8080(ycmjason.com) to port 46606
bouncy-forever server launched and listening on port 8080...

You can also run the server as a daemon (i.e. in the background):

> bouncyforever start
Starting bouncy-forever-server daemon...
bouncy-forever-server daemon started. PID: 10614

> bouncyforever restart
Stopping bouncy-forever-server daemon...
bouncy-forever-server daemon stopped.
Starting bouncy-forever-server daemon...
bouncy-forever-server daemon started. PID: 11023

> bouncyforever stop
Stopping bouncy-forever-server daemon...
bouncy-forever-server daemon stopped.

The bouncy-forever server will listen on port 8080 by default but could easily be changed by specifying the PORT environment variable:

> PORT=80 bouncyforever

Logs

The output of your apps will be piped into the following directory ~/.bouncy-forever/logs/.

> cd ~/.bouncy-forever/logs/
> ls
cv/  ycmjason.com/
> cd cv
> ls
out.log
> cat out.log
Listening on 38186...

License

MIT