Framework for handling the details of setting up an express.js server by specifying server options, plug-ins to load, and then starting the server.
npm install express-modular-server
If you just want a HTTP/HTTPS server up and running as fast as possible, install any desired services and webapps and then run the server. For example, the following commands will install and run the "hello" server in a new directory:
npm install express-modular-server
npm install service-app
npm install webapp-app
npm install webapp-hello
node node_modules/express-modular-server/index.js
When started directly from the command line in this way, the default is to create an HTTP server on port 8080, and to autoload all services (node modules named starting with "service-") that it can find in a standard ancestor searching starting in the express-modular-server directory (see the autoload parameter below for more details).
This behavior can be altered via environment variables or command line parameters. The latter takes precedence.
These take precedence over any environment variables specified.
Specifies the TCP port to run the HTTP server on. The default is 8080.
Example:
Start the HTTP server on port 9000.
node node_modules/express-modular-server/index.js --port=9000
Specifies the TCP port to run the HTTPS server on. The default is 8082.
Specifies that the HTTPS server is to be run. One or more hostname:path pairs separated by commas must be provided. Each host name is a the full host name to listen on, while the path is the path to a directory which must contain certificate files and private keys.
Example:
Listen on two hosts: www.example.com and internal.example.com, using port 8500 for HTTP and port 8900 for HTTPS, where the first host has certificate files in /home/michael/.ssl/www.example.com/ and the second in /home/michael/.ssl/internal.example.com/.
node node_modules/express-modular-server/index.js --port=8500 --sslport=8900 --hosts=www.example.com:/home/michael/.ssl/www.example.com/,internal.example.com:/home/michael/.ssl/internal.example.com/
Specifies the IP address to listen on. If no IP address is specified, "0.0.0.0" is used.
Specifies the TCP port to run the HTTP server on. The default is 8080.
Specifies the TCP port to run the HTTPS server on. The default is 8082.
Specifies that the HTTPS server is to be run. One or more hostname:path pairs separated by commas must be provided. Each host name is a the full host name to listen on, while the path is the path to a directory which must contain certificate files and private keys.
Specifies the IP address to listen on. If no IP address is specified, "0.0.0.0" is used.
Example:
Listen on two hosts: www.example.com and internal.example.com, using port 8500 for HTTP and port 8900 for HTTPS, where the first host has certificate files in /home/michael/.ssl/www.example.com/ and the second in /home/michael/.ssl/internal.example.com/.
PORT=8500 SSLPORT=8900 HOSTS=www.example.com:/home/michael/.ssl/www.example.com/,internal.example.com:/home/michael/.ssl/internal.example.com/ node node_modules/express-modular-server/index.js
For greater control, you can require the express-modular-server in your own code and then call API functions on the returned object to start the server.
The work is done in the function returned when you require the module. This function takes a single argument, which is an object taking configuration values. All functions returns the module, allowing you to chain calls. The module contains two function: API to load a plug-in, and start to start the server. The start function should come last. The API call is not used if the autoload option is provided and true as this automatically detects and loads services. This allows for service modules to be dynamically added or removed without (in most cases) the need to change the main server module, simply by running "npm install" or "npm uninstall" for the desired service.
Example: Start an HTTP server on port 8080, automatically loading all services modules found.
var server = require("express-modular-server")({
http:true,
autoload:true
}).start("127.0.0.1")
Example: Configure a single http server on the default port (8080) and load the service plug-ins "gpio", "mma8451", "mx28adc", and "app" before starting the server.
var server = require("express-modular-server")({
http:true
})
.API("gpio")
.API("mma8451")
.API("mx28adc")
.API("app")
.start()
When calling the function returned by requiring express-modular-server, the following configuration keys are recognized in the first parameter:
When this key is present, express.js will service requests using the http network protocol. If this value is true the default port is used. If the environment variable PORT is present, its numerical values is used as the default, otherwise 8080 is the default. If this value is a number, the specified number is used. An invalid value may also be interpreted as using the default.
When this key is present, express.js will service requests using the https network protocol. The value of this key must be an object containing keys which are the host name to listen on, and values corresponding to the directory containing the credentials files for each server. The following files must be present in each directory: cert.pem containing the SSL certificate for the host name, privkey.pem containing the private key, and chain.pem containing the SSL chain.
When this key is present and is a true value, all modules beginning with service- will be loaded and initialized before the require function returns. The search path starts in the node_modules directory of the top-level module and in every parent directory to the root and to find all immediate sub-directories beginning with service- in every node_modules directory found along that path. After loading, if the module.exports is a function it will be called, passing the app, express, and options parameters.
The options parameter to each module will be determined by applying any configuration found in the EMS.cfg file and the autoconfig parameter (in that order) to the default of
{
"last": "service-app"
}
If the resulting object has a key which is the full name of the module, then its value will be passed as the options parameter to that module.
The search path for the EMS.cfg file is the directory the top-level module is in and every parent directory until the file is found (at most one config file will be loaded) or no more directores are left. The EMS.cfg format is JSON.
See the next secton for the full format of the autoconfig object.
When this key is present it must be an object containing autload configuration information. This configuration takes precedence over any configuration in an EMS.cfg file, which takes precedence over the default (see last section).
The following keys are recognized:
Must be a string value containing the full name of the module which is to be initialized last. The default is service-app. The purpose of having a last module is generally to create an express default route.
Must be an array containing strings where each string is the full name of a module which is to be ignored and not loaded. This provides a way to avoid loading a module without uninstalling it, as well as to avoid autloading non-EMS modules which happen to start with "service-".
Any other key starting with "service-" is interpreted as the full name of a module which might be loaded. The value associated with this key is the value to pass as the options parameter to the function exported by the module for initialization. If the specified service is not loaded this value is ignored.
This key can be either a string, or an array of strings. Each string specifies the path to a file to log messages logged by the Log function. If no log is specifed, messages will be logged to the console.
In addition to calls to the Log function, all requests that express.js is about to service will be logged with the format:
<ISO8601Time>:<IPAddress>:<METHOD> <URL>
A plug-in is a separate package that adheres to the following conventions. Its name must begin with service-. The API call to load this plug-in must omit this prefix, but all references to it in the autoconfig must not. If the API call is used, then the top-level code invoking the server must include all plug-ins used in its list of dependencies. If the autoload feature is used, this is not necessary, instead, services can be installed and uninstalled in whatever manner is desired with only a server restart required to reflect the change.
A plug-in must declare its module.exports to be a function taking the following arguments: the app express object, the express express object, and an options argument. Often the second and third arguments will be optional. In this function, the plug-in must set up any endpoints via the app and/or express objects provided, as well as define any functionality needed to service these requests.
The following example defines a GPIO service utilizing the gpio function. It provides one available option to change the endpoint, and displays an initialization message to the log.
function gpio(req,res) {
// actual implementation would go here
}
var endpoint = "/gpio/"
module.exports = function(app,express,options) {
if (options && typeof options == "string") {
endpoint = options
}
Log("service gpio ",endpoint)
app.get(endpoint, gpio)
}
The server defines a few convenience functions which plug-in can call.
Logs a message to wherever messages are configured to be logged to. All arguments to this function are combined into a single string with the current time and a colon prepended.
Converts a buffer to Base-64. Takes the value to convert as a parameter and returns the converted value.
Converts from Base-64. Takes the value to convert as a parameter and returns the converted value.
There are a few changes in version 2.0 which technically make it incompatible with 1.0:
- Support for express-streamline has been removed in favor of promises and the new async/await syntax which now has widespread support.
- The behavior of loading modules has been reverted to simply requiring the specified modules, rather than trying to autoload the entire directory.
- Support for the obsolete "server-" prefix has been removed: all modules must now begin with "service-".
Written by Michael Schmidt.
GPL 3.0