Skip to content

A replacement Node.js web server for RocketMap, built by devkat, using restify and node-mysql, that supports gzip compression, load limiting, throttling and multiprocessing (+ process management).

License

Notifications You must be signed in to change notification settings

rlodev67/devkat-rm-node-webserver

 
 

Repository files navigation

Donate Python 2.7 license

The Sublimely Magnificent Node.js RM Webserver Mark III

An asynchronous Node.js webserver using restify for the API, node-mysql for MySQL integration and that supports gzip compression, load limiting with toobusy-js, rate limiting with restify's throttling and multiprocessing (+ process management) with cluster.

Since this webserver is meant to be set up as a managed microcomponent - not as a replacement webserver for static components - its functionality is strictly limited to serving dynamic data requests only. Using a more mature webserver to serve static components and as a reverse proxy is highly recommended (nginx on Linux, apache2 on Windows), an example nginx configuration is provided below.

If you want to use a more advanced process manager, we recommend disabling cluster in your configuration to disable process management.

Getting Started

These instructions will help you deploy the project on a live system.

Important: The default configuration example file .env.example overwrites the NODE_ENV environment variable to production for security purposes.

Prerequisites

Windows: To update npm and Node.js, manually download the LTS version from their website.

To update Node.js and npm:
apt-get remove node nodejs
curl -L https://git.io/n-install | bash
n lts

To update only npm:
npm install -g npm

Installing

Start by reading the license in LICENSE.md.

Make sure Node.js and npm are properly installed:

node -v
npm -v

Clone the project and its submodules:

git clone --recursive https://github.com/sebastienvercammen/devkat-rm-node-webserver.git

Make sure you are in the project directory with your terminal, and install the dependencies:

npm install

Copy the example configuration file .env.example to .env:

Linux:
cp .env.example .env

Windows:
copy .env.example .env

And presto, you're ready to configure.

After configuring, start the server with:

node index.js

Configuration

Settings you must review

# Webserver host IP to bind to. 0.0.0.0 binds to all interfaces.
WEB_HOST=0.0.0.0

# Webserver port.
WEB_PORT=8080

# Set up domain(s) to allow CORS for, via comma-separated list.
CORS_WHITELIST=*

# And all database settings.
DB_HOST=localhost
DB_PORT=3306
DB_USER=root
DB_PASS=
DB_DATABASE=database

Enabling gzip compression

ENABLE_GZIP=true

Enabling HTTPS

# HTTPS key file paths.
ENABLE_HTTPS=true
HTTPS_KEY_PATH=privkey.pem
HTTPS_CERT_PATH=cert.pem

Enabling load limiter

# Enable/disable the load limiter.
ENABLE_LOAD_LIMITER=true

# Enable/disable logging when load limiter kicks in on a worker.
ENABLE_LOAD_LIMITER_LOGGING=true

# Represents the maximum amount of time in milliseconds that the event queue
# is behind, before we consider the process "too busy".
MAX_LAG_MS=75

# The check interval for measuring event loop lag, in milliseconds.
LAG_INTERVAL_MS=500

Enabling request throttling

Note: When enabling request throttling, make sure you're not using a reverse proxy, since all requests will come from the same IP.

# Enable/disable webserver request throttling.
ENABLE_THROTTLE=true
# Rate limit: requests per second.
THROTTLE_RATE=5
# Allow user to temporarily go over the rate limit, up to the burst limit.
THROTTLE_BURST=10

Allowing CORS for all domains

Warning: Enabling CORS for all domains is not recommended. You will only make it easier for scrapers to get your data.

# Set up domain(s) to allow CORS for, via comma-separated list.
CORS_WHITELIST=*

Disabling process management with cluster

Note: Disabling process management with cluster will automatically make the webserver ignore all configuration items related to multiprocessing/cluster.

ENABLE_CLUSTER=false

Using nginx as a reverse proxy to /raw_data, with fallback to Flask for unsupported features

If you're using nginx to serve your RocketMap website, make sure your nginx configuration looks like the example below to serve /raw_data with the new webserver, and all other paths with RocketMap's Flask/werkzeug.

This example assumes your RM webserver is running on port 5000 and the devkat webserver on port 1337. Adjust accordingly.

If a feature is not yet implemented in this webserver, the example configuration falls back to the Flask webserver. The focus of this webserver is to have the best performance for /raw_data requests, although other features are planned to be implemented (at a lower priority).

Based on RocketMap's nginx example.

upstream flask {
    server 127.0.0.1:5000;
}
upstream devkat {
    server 127.0.0.1:1337;
}

server {
    listen 80;

    location /raw_data {
        # /stats
        if ($arg_seen = "true") {
            proxy_pass http://flask;
        }

        # /status
        if ($arg_status = "true") {
            proxy_pass http://flask;
        }

        # Appearances & appearance details.
        if ($arg_appearances = "true") {
            proxy_pass http://flask;
        }

        if ($arg_appearancesDetails = "true") {
            proxy_pass http://flask;
        }

        # Spawnpoints.
        if ($arg_spawnpoints = "true") {
            proxy_pass http://flask;
        }

        # Scanned locations.
        if ($arg_scanned = "true") {
            proxy_pass http://flask;
        }

        proxy_pass http://devkat;
    }

    location / {
        proxy_pass http://flask;
    }
}

License

This project is licensed under AGPLv3 - see the LICENSE.md file for details.

About

A replacement Node.js web server for RocketMap, built by devkat, using restify and node-mysql, that supports gzip compression, load limiting, throttling and multiprocessing (+ process management).

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • JavaScript 100.0%