appup
v1.3.0
Published
CLI to launch apps that use an express main server and an optional restif api server.
Downloads
12
Maintainers
Readme
appup
CLI to launch apps that use an express main server and an optional restif api server.
Servers are super stable with the help of domains and the cluster module.
This means in practice that when a request causes an unhandled error a 500
response is sent, the server shut down
gracefully and a new one spun up.
Two servers are spun up originally for each port, so that while one is restarted, the other one keeps servicing incoming requests.
Installation
npm install appup
CLI
appup [options] file
Options:
--pages port to start pages server on
--watchdir directory to watch for client side JavaScript changes in order to automatically refresh
--dedupe if set it will [dynamically dedupe] (https://github.com/thlorenz/dynamic-dedupe)
all modules as they are being required to work around the fact that symlinks break `npm dedupe`
--api port to start api server on
--apihost address at which api server is hosted [default: "localhost"]
--tunnel sets up local tunnel pointing to pages port and logs url to connect to from remote client
--config point to a config file to override routes, etc. for the pages and api server
--nocluster if set, single servers are launched instead of a cluster of them, which maybe preferred during development
API
generated with docme
config
The config needs to provide either or all of the following properties on the module exports object:
- bundleOpts:
{Object}
options passed tobrowserify().bundle(options)
- initBrowserify:
{Function}
invoked withbrowserify
that needs to return a browserify instance that can be initialized according to our needs - initPages {Function} invoked with
(pagesApp, express, apiServerInfo)
where apiServerInfo is{ host: {string}, port: {number} }
- postInitPages {Function} invoked with
(pagesApp, pagesServer, express)
wherepagesServer
is the result ofpagesApp.listen()
- pagesSend500 {Function} invoked with
(req, res, err)
to allow responding with a 500 error before worker gets taken offline and another one is launched - initApi {Function} invoked with
(apiApp, restify)
- postInitApi {Function} invoked with
(apiApp, apiServer, restify)
whereapiServer
is the result ofapiApp.listen()
- apiSend500 {Function} invoked with
(req, res, err)
to allow responding with a 500 error before worker gets taken offline and another one is launched - events {EventEmitter} used to emit
info
anderror
events, if not provided messages are logged to the console instead
Example config
// Bundle options
exports.bundleOpts = { debug: true, insertGlobals: false };
exports.initBrowserify = function (browserify) {
return browserify().transform('hbsfy');
};
// Server options
// Pages
exports.initPages = function (pagesApp, express, apiServerInfo) {
pagesApp.use(core.renderViewMiddleware(viewPath, { title: 'core' }));
};
exports.postInitPages = function (pagesApp, pagesServer, express) {
};
// API
exports.initApi = function (apiApp, restify) {
};
exports.postInitApi = function (apiApp, apiServer, restify) {
};
License
MIT