Skip to content

Latest commit

 

History

History
867 lines (675 loc) · 43.3 KB

README.md

File metadata and controls

867 lines (675 loc) · 43.3 KB
Raw

Roosevelt MVC web framework

Greenkeeper badge Build Status Coverage Status npm

Roosevelt is a web application development framework based on Express. Roosevelt abstracts all the crusty boilerplate necessary to build a typical web application using Express and provides a uniform MVC structure for your app.

Named for the most badass President of all-time, whose facial hair is a curly brace, Roosevelt's main goal is to be the easiest web framework to learn and use on the Node.js stack by setting sane defaults while also providing easy ways to override the defaults and tap into the full potential of Express.

By default Roosevelt integrates Teddy for HTML templating, LESS for CSS preprocessing, and UglifyJS for JS minification. But you can use other templating systems, CSS preprocessors, or JS minifiers if you like, as Roosevelt is easy to configure.

Roosevelt will also automatically validate your HTML in development mode using a local instance of the Nu HTML Checker.

Teddy Roosevelt's facial hair is a curly brace.

Note: this is documentation for Roosevelt 0.11.x. If you need API documentation for a previous version of Roosevelt, look here.

Table of contents

Why use Roosevelt?

Roosevelt is easy to use and has a low learning curve, unlike many other popular Node.js web frameworks.

Reasons for this include:

  • Minimal boilerplate to get started. All the magic of Express is preconfigured for you.
  • Default directory structure is simple, but easily configured.
  • Concise MVC architecture.
  • Teddy HTML templates are much easier to read and maintain than popular alternatives.
  • Automatic HTML validation.
  • LESS and UglifyJS preconfigured out of the box to intelligently minify your external facing CSS and JS files.
  • Built-in, easy to use interface to browserify bundling for frontend JS modularization using the Node.js module exports and require syntax.

Create and run a Roosevelt app

First you will need to install Node.js. Both the current and LTS version of Node.js are supported. It is recommended that you install using a Node.js version manager like nvm rather than the official installer, as a version manager will allow you to switch between multiple versions of Node.js easily.

Some important caveats to note:

  • nvm is not available on Windows.
  • Linux/macOS users who install Node.js without a version manager like nvm may need to resolve some commonly encountered permissions headaches associated with npm. As such, use of nvm is strongly recommended.

The Java JDK is also required for development work. The JDK is required for the local HTML validator feature.

Once you have a sane developmemt environment, you can proceed with the standard install procedure below.

Install Roosevelt and create an app

Note: Windows users may need to run their command line as administrator to avoid permission errors relating to symlink creation.

Globally install Yeoman:

npm i -g yo

Globally install the Roosevelt Yeoman generator:

npm i -g generator-roosevelt

Create a Roosevelt app:

yo roosevelt

Then follow the prompts.

Afterward...

Install dependencies:

npm i

Run in development mode:

npm run dev

Or run in production mode:

npm run prod

Note: npm start is aliased to npm run prod.

It is also possible to create a Roosevelt app without using generator-roosevelt. This will result in a more minimalist default configuration (e.g. no CSS or JS preprocessors enabled by default).

To do that:

  • First create a new folder and cd into it.
  • Then npm i roosevelt. This will create a node_modules folder with Roosevelt and its bare minimum dependencies.
  • Create app.js.
  • Put this code in app.js: 
    require('roosevelt')({
  'generateFolderStructure': true
}).startServer()
  • Then node app.js. If the generateFolderStructure param is set to true like the above code example, an entire Roosevelt app with bare minimum viability will be created and the server will be started. See below for more information about parameter configuration.

Other useful scripts

Roosevelt apps created with the generator come with a range of other useful npm scripts beyond npm run dev and npm run prod:

Run your app with the HTML validator enabled:

npm run dev -- --enable-validator
  • --html-validator or -h can also be used.

Run your app with the HTML validator disabled:

npm run dev -- --disable-validaor
  • --raw or -r can also be used.

Run your app with a detached HTML validator instead of the default attached validator (runs validator as a separate process in the background; process must be manually killed later, see below):

npm run dev -- --background-validator
  • -b can also be used.

After running your app with a detached HTML validator, use this command to shut down the HTML validator:

npm run kill-validator

Or if your app is configured to detach the validator by default, you can force the validator to be attached like so:

npm run dev -- -attach-validator
  • -a can also be used.

Configure how many CPUs your app will run on:

npm run dev -- --cores 2
  • -c can also be used.
  • Can set to max to use all available CPUs.
  • Default is 1.

Remove all build artifacts (symlinks and directories) auto-generated by Roosevelt (will prompt to confirm before deleting any files):

npm run cleanup

Scan current rooseveltConfig and scripts in package.json and warn about any params or npm scripts that don't match the current API:

npm run audit

See also the the full list of default scripts.

Default directory structure

  • app.js: main app file. Feel free to rename this, but make sure to update package.json's reference to it.
  • mvc: folder for models, views, and controllers. All configurable via params (see below).
    • controllers: folder for controller files.
    • models: folder for model files.
    • views: folder for view files.
  • node_modules: a standard folder where all modules your app depends on (such as Roosevelt) are installed to. This folder is created by the npm install command.
  • package.json: a standard file in Node.js apps for configuring your app.
  • public: all contents within this folder will be exposed as static files.
  • statics: folder for source CSS, images, JS files, and other statics. Some of the contents of this folder are symlinked to from public, which you can configure (see below).
    • css: folder for source CSS files.
    • images: folder for source image files.
    • js: folder for source JS files.
  • .gitignore: a standard file which contains a list of files and folders to ignore if your project is in a git repo.

Default .gitignore

The default .gitignore file contains many common important things to ignore, however you may need to tweak it to your liking before using a fresh Roosevelt app in your git repo.

Some notable things ignored by default and why:

  • public: It's recommended that you don't create files in this folder manually, but instead use the staticsSymlinksToPublic feature detailed below to expose folders in your statics directory via auto-generated symlinks.
  • .build: By default Roosevelt will compile LESS and JS files down to minified versions in statics/.build when the server starts. As such, it's not recommended to place files in the build directory manually.
  • node_modules: This folder will be auto-generated when you run the npm install step to set up your app. Since some modules you might include later in your app can be platform-specific and are compiled for your OS during the install step, it's generally not recommended to commit the node_modules folder to git.

Configure your app with parameters

Roosevelt is designed to have a minimal amount of boilerplate so you can focus on just writing your app. All parameters are optional. As such, by default, all that's in app.js is this:

require('roosevelt')().startServer();

Roosevelt will determine your app's name by examining "name" in package.json. If none is provided, it will use Roosevelt Express instead.

Also, while it is recommended that you pass params to Roosevelt via package.json under "rooseveltConfig", you can also pass params programmatically via Roosevelt's constructor like so:

require('roosevelt')({
  paramName: 'paramValue',
  param2:    'value2',
  etc:       'etc'
}).startServer();

This is particularly useful for setting params that can't be defined in package.json such as event handlers (see below).

App behavior parameters

  • port: The port your app will run on. Can also be defined using HTTP_PORT or NODE_PORT environment variable.

    • Default: [Number] 43711.

  • nodeEnv: [String] Param to override the NODE_ENV environment variable.

    • Default: undefined.

  • generateFolderStructure: When enabled Roosevelt will generate user specified directories (e.g. MVC parameters and statics parameters).

    • Default: [Boolean] true.
      • Note: When package.json is not present or rooseveltConfig is not present in package.json, this param will be reset to false by default. This is a defensive measure to minimize the risk of files and folders being created in scenarios when they are not wanted.
    • This param is useful in scenarios when you want to create a Roosevelt app entirely from nothing (without using generator-roosevelt). See above for an example.

  • appDir: Project root. Can be useful to change in testing environments like Mocha or if you just want to specify it by hand.

    • Default: [String] The directory where your project package.json is located.

    • Example customization:

      {
  "appDir": "/some/other/path"
}

  • localhostOnly: Listen only to requests coming from localhost in production mode. This is useful in environments where it is expected that HTTP requests to your app will be proxied through a more traditional web server like Apache or nginx. This setting is ignored in development mode.

    • Default: [Boolean] true.

  • suppressLogs: Accepts an object containing two related parameters:

    • httpLogs: [Boolean] When set to true, Roosevelt will not log HTTP requests to the console.

    • rooseveltLogs: [Boolean] When set to true, Roosevelt will not log app status to the console.

    • rooseveltWarnings: [Boolean] When set to true, Roosevelt will not log app warnings to the console.

    • Default: [Object]

      {
  "httpLogs": false,
  "rooseveltLogs": false,
  "rooseveltWarnings": false
}

  • noMinify: Disables HTML minification as well as the minification step in supporting CSS and JS compilers. Automatically enabled during development mode.

    • Default: [Boolean] false.

  • htmlValidator: Params to send to html-validator:

    • enable: [Boolean] Enables or disables the built-in HTML validator.

      • Note: The validator is only available in development mode.
      • You can also force the validator off in development mode regardless of app settings with npm run dev -- --disable-validator.
      • You can also force the validator on in development mode regardless of app settings with npm run dev -- --enable-validator.

    • exceptions: [Object] Use this to customize the name of the request header or model value that is used to disable the HTML validator.

    • port: [Number] Port to spawn the validator process on.

    • separateProcess: [Boolean] When set to true, the HTML validator will run detached (separate from the node process) by default. You can kill the process by running npm run kill-validator.

    • suppressWarnings: [Boolean] When set to true, validation warnings will be hidden and only errors will be shown.

    • Default: [Object]

      {
  "enabled": false,
  "exceptions": {
    "requestHeader": "Partial",
    "modelValue": "_disableValidator"
  },
  "port": 8888,
  "separateProcess": false,
  "suppressWarnings": false
}

  • multipart: Settings to pass along to formidable using formidable's API for multipart form processing. Access files uploaded in your controllers by examining the req.files object. Roosevelt will remove any files uploaded to the uploadDir when the request ends automatically. To keep any, be sure to move them before the request ends. To disable multipart forms entirely, set this option to false.

    • Default: [Boolean] 
      {
  "multiples": true
}

  • toobusy: Params to pass to the node-toobusy module.

    • maxLagPerRequest: [Number] Maximum amount of time in miliseconds a given request is allowed to take before being interrupted with a 503 error.

    • lagCheckInterval: [Number] Interval for checking event loop lag in miliseconds.

    • Default: [Object]

      {
  "maxLagPerRequest": 70,
  "lagCheckInterval": 500,
}

  • shutdownTimeout: Maximum amount of time in miliseconds given to Roosevelt to gracefully shut itself down when sent the kill signal.

    • Default: [Number] 30000 (30 seconds).

  • bodyParserUrlencodedParams: Parameters to supply to body-parser.urlencoded.

    • Default: [Object]

      {
  "extended": true
}

  • bodyParserJsonParams: Parameters to supply to body-parser.json.

    • Default: [Object] {}.

HTTPS parameters

  • https: [Object] Run a HTTPS server using Roosevelt.
    • Object members:
    • enable: Enable HTTPS server.
      • Default: [Boolean] false.
    • httpsOnly: Disable HTTP server when running a HTTPS server.
      • Default: [Boolean] false.
    • httpsPort: The port your app will run a HTTPS server on. Can also be defined using the HTTPS_PORT environment variable.
      • Default: [Number] 43733.
    • pfx: Specify whether or not your app will use pfx or standard certification.
      • Default: [Boolean] false.
    • keyPath: Stores the file paths of specific key/certificate to be used by the server.
      • Default: null.
      • When set: [Object] pfx, key, cert -- use one of {pfx} or {key, cert}.
    • passphrase: [String] Supply the HTTPS server with the password for the certificate being used, if necessary.
      • Default: null.
    • ca: [String] Certificate authority to match client certificates against, as a file path or array of file paths. Can also be a full certificate string, requiring cafile to be false.
      • Default: null.
    • cafile: Whether or not the entry supplied by ca is a file.
      • Default: [Boolean] true.
    • requestCert: Request a certificate from a client and attempt to verify it.
      • Default: [Boolean] false.
    • rejectUnauthorized: Upon failing to authorize a user with supplied CA(s), reject their connection entirely.
      • Default: [Boolean] false.
    • Default: [Object] {}.

MVC parameters

  • modelsPath: Relative path on filesystem to where your model files are located.

    • Default: [String] "mvc/models".

  • viewsPath: Relative path on filesystem to where your view files are located.

    • Default: [String] "mvc/views".

  • viewEngine: What templating engine to use, formatted as "fileExtension: nodeModule".

    • generator-roosevelt default: [String] "html: teddy".

    • Also by default when using the generator, the module teddy is marked as a dependency in package.json.

    • Bare Roosevelt default (when an app is created without the generator): [String] none. Can also be set to null to use no templating engine.

    • To use multiple templating systems, supply an array of engines to use in the same string format. Each engine you use must also be marked as a dependency in your app's package.json. Whichever engine you supply first with this parameter will be considered the default.

    • Example configuration using multiple templating systems: [Object]

      {
  "viewEngine": [
    "html: teddy",
    "mustache: mustache",
    "handlebars: handlebars",
    "ejs: ejs"
  ]
}

  • controllersPath: Relative path on filesystem to where your controller files are located.

    • Default: [String] "mvc/controllers".

Error page parameters

  • error404: Relative path on filesystem to where your "404 Not Found" controller is located. If you do not supply one, Roosevelt will use its default 404 controller instead.
    • Default: [String] "404.js".
  • error5xx: Relative path on filesystem to where your "Internal Server Error" controller is located. If you do not supply one, Roosevelt will use its default controller instead.
    • Default: [String] "5xx.jx".
  • error503: Relative path on filesystem to where your "503 Service Unavailable" controller is located. If you do not supply one, Roosevelt will use its default 503 controller instead.
    • Default: [String] "503.js".

Statics parameters

  • staticsRoot: Relative path on filesystem to where your source static assets are located. By default this folder will not be made public, but is instead meant to store unprocessed or uncompressed source assets that will later be preprocessed and exposed in public.

    • Default: [String] "statics".

  • htmlMinify: Params to send to express-minify-html, an Express middleware for html-minifier:

    • Set override [Boolean] to false to disable minification entirely.

    • For other usage, see express-minify-html usage.

    • Default: [Object]

      {
  "override": true,
  "exception_url": false,
  "htmlMinifier": {
    "html5": true
  }
}

  • css: [Object] CSS-related configuration options.

    • Object members:

    • sourceDir: Subdirectory within staticsRoot where your CSS files are located. By default this folder will not be made public, but is instead meant to store unminified CSS source files which will be minified and stored in a build directory when the app is started.

    • compiler: [Object] Which Roosevelt CSS preprocessor middleware, if any, to use.

      • Your chosen Roosevelt CSS preprocessor module must be marked as a dependency in your app's package.json.

      • The default preprocessor for a Roosevelt app created with generator-roosevelt is roosevelt-less, which is marked as a dependency in package.json on freshly generated Roosevelt apps. See roosevelt-less usage for details on what params are available.

      • generator-roosevelt default configuration: [Object]

        {
  "nodeModule": "roosevelt-less",
  "params": {
    "cleanCSS": {
      "advanced": true,
      "aggressiveMerging": true
    },
    "sourceMap": null
  }
}

      • Bare Roosevelt default (when an app is created without the generator): [String] none. Can also be set to null to use no CSS compiler.

    • whitelist: Array of CSS files to whitelist for compiling. Leave undefined to compile all files. Supply a : character after each file name to delimit an alternate file path and/or file name for the minified file.

      • Example array member: [String] less/example.less:.build/css/example.min.css (compiles less/example.less into .build/css/example.min.css).

    • output: Where to place compiled CSS files. This folder will be symlinked into public by default.

    • versionFile: If enabled, Roosevelt will create a CSS file which declares a CSS variable containing your app's version number from package.json. Enable this option by supplying an object with the member variables fileName and varName.

      • Default: null.

      • Example usage (with roosevelt-less): [Object]

        {
  "fileName": "_version.less",
  "varName": "appVersion"
}

      • Assuming the default Roosevelt configuration otherwise, this will result in a file statics/css/_version.less with the following content:

        /* do not edit; generated automatically by Roosevelt */ @appVersion: '0.1.0';

      • Some things to note:

        • If there is already a file there with that name, this will overwrite it, so be careful!
        • It's generally a good idea to add this file to .gitignore, since it is a build artifact.

    • Default: [Object]

      {
  "sourceDir": "css",
  "compiler": {
    "nodeModule": "roosevelt-less",
    "params": {
      "cleanCSS": {
        "advanced": true,
        "aggressiveMerging": true
      },
      "sourceMap": null
    }
  },
  "whitelist": null,
  "output": ".build/css",
  "versionFile": null
}

  • js: [Object] JS-related configuration options.

    • Object members:

    • sourceDir: Subdirectory within staticsRoot where your JS files are located. By default this folder will not be made public, but is instead meant to store unminified JS source files which will be minified and stored in a build directory when the app is started.

    • compiler: Which Roosevelt JS minifier middleware, if any, to use.

      • Your chosen Roosevelt JS minifier module must also be marked as a dependency in your app's package.json.

      • showWarnings param: [Boolean] Set to true to display compiler module warnings.

      • The default minifier for a Roosevelt app created with generator-roosevelt is roosevelt-uglify, which is marked as a dependency in package.json on freshly generated Roosevelt apps. See roosevelt-uglify usage for details on what params are available.

        • The Roosevelt team also maintains roosevelt-closure, an alternative to roosevelt-uglify.

      • generator-roosevelt default configuration: [Object]

        {
  "nodeModule": "roosevelt-uglify",
  "showWarnings": false,
  "params": {}
}

      • Bare Roosevelt default (when an app is created without the generator): [String] none. Can also be set to null to use no JS minifier.

    • whitelist: Array of JS files to whitelist for minification. Leave undefined to compile all files. Supply a : character after each file name to delimit an alternate file path and/or file name for the minified file.

      • Default: null (compiles all JS files, if a JS minifier is enabled).
      • Example array member: [String] library-name/example.js:lib/example.min.js (compiles library-name/example.js into lib/example.min.js).

    • blacklist: Array of JS files to exempt from minification. These files will be copied as-is to the build folder. Leave undefined to compile all files.

      • Default: null (compiles all JS files, if a JS minifier is enabled).
      • Example: [String] example.js.

    • output: Where to place compiled JS files. This folder will be symlinked into public by default.

      • Default: [String] ".build/js".

    • bundler: Params related to bundling JS with browserify.

      • bundles: [Array] Declare one or more files in your sourceDir to be browserify bundles via its bundle method. Use of browserify in Roosevelt is optional. If no bundles are defined here, the browserify step will be skipped.

        • env param: [String] bundle only in dev or prod mode. Omitting env will result in bundling in both modes.

        • params param: [Object] the browserify params to send to browserify. If it is not set, these default params will be sent: {"paths": your jsPath}.

        • Examples: [Array] of [Objects]

        • Browserify bundle example declaring one bundle:

          [
  {
    "outputFile": "bundle.js",
    "files": [
      "landingPage.js",
      "main.js",
      "etc.js"
    ],
    "params": {
      "someOpt":
      "someValue"
    }
  }
]

        • Browserify bundle example declaring one bundle only used in dev mode:

          [
  {
    "outputFile": "bundle.js",
    "env": "dev",
    "files": [
      "landingPage.js",
      "main.js",
      "etc.js"
    ],
    "params": {
      "someOpt": "someValue"
    }
  }
]

        • Browserify bundle example declaring multiple bundles:

          [
  {
    "outputFile": "bundle1.js",
    "files": [
      "landingPage.js",
      "main.js",
      "etc.js"
    ],
    "params": {
      "someOpt": "someValue"
    }
  },
  {
    "outputFile": "bundle2.js",
    "files": [
      "somethingElse.js",
      "anotherThing.js",
      "etc.js"
    ]
  },
  etc...
]

        • Default: [Array] [].

      • output: Subdirectory within sourceDir where you would like browserify to deposit bundled JS files it produces (if you use browserify).

        • Default: [String] ".bundled".

      • expose: Whether or not to copy the output directory to your build directory.

        • Default: [Boolean] true.

    • Default: [Object]

        {
    "sourceDir": "js",
    "compiler": {
      "nodeModule": "roosevelt-uglify",
      "showWarnings": false,
      "params": {}
    }
    },
    "whitelist": null,
    "blacklist": null
    "output": ".build/js",
    "bundler": {
      "bundles": [],
      "output": ".bundled",
      "expose": true
    }
  }

Public folder parameters

  • publicFolder: All files and folders specified in this path will be exposed as static files.

    • Default: [String] "public".

  • favicon: Location of your favicon file.

    • generator-roosevelt default: [String] "images/favicon.ico".
    • Bare Roosevelt default (when an app is created without the generator): [String] none. Can also be set to null to use no favicon.

  • staticsSymlinksToPublic: Array of folders from staticsRoot to make symlinks to in your public folder, formatted as either "linkName: linkTarget" (whitespace optional) or simply "linkName" if the link target has the same name as the desired link name.

    • Default: [Array] of [Strings] 
      [
  "css: .build/css",
  "images",
  "js: .build/js"
]

  • versionedPublic: If set to true, Roosevelt will prepend your app's version number from package.json to your public folder. Versioning your public folder is useful for resetting your users' browser cache when you release a new version.

    • Default: [Boolean] false.

  • alwaysHostPublic: By default in production mode Roosevelt will not expose the public folder. It's recommended instead that you host the public folder yourself directly through another web server, such as Apache or nginx. However, if you wish to override this behavior and have Roosevelt host your public folder even in production mode, then set this setting to true.

    • Default: [Boolean] false.

Events

Roosevelt also provides a series of events you can attach code to by passing a function to the desired event as a parameter to Roosevelt's constructor like so:

require('roosevelt')({
  onServerStart: function(app) { /* do something */ }
});

Event list

  • onServerInit(app): Fired when the server begins starting, prior to any actions taken by Roosevelt.
  • onServerStart(app): Fired when the server starts.
  • onReqStart(req, res, next): Fired at the beginning of each new request.
    • req: The request object created by Express.
    • res: The response object created by Express.
    • next: Callback to continue with the request. Must be called to continue the request.
  • onReqBeforeRoute(req, res, next): Fired just before executing the controller.
    • req: The request object created by Express.
    • res: The response object created by Express.
    • next: Callback to continue with the request. Must be called to continue the request.
  • onReqAfterRoute(req, res): Fired after the request ends.

Making controller files

Controller files are just standard Express routes. A route is the term Express uses for URL endpoints, such as http://yoursite/blog or http://yoursite/about.

To make a new controller, just make a new file in the controllers directory. For example:

module.exports = function(app) { // app is the Express app created by Roosevelt

  // standard Express route
  app.route('/about').get(function(req, res) {

    // load a data model
    var model = require('models/dataModel');

    // render a Teddy template and pass it the model
    res.render('about', model);
  });
};

Sometimes it is also useful to separate controller logic from your routing. This can be done by creating a reusable controller module.

An example would be creating a reusable controller for "404 Not Found" pages:

// reusable controller "notFound.js"
module.exports = function(app, req, res) {
  var model = { content: 'Cannot find this page' };
  res.status(404);
  res.render('404', model);
}

Reusable controller modules differ from standard controller modules in that they accept req and res arguments in addition to app. They are meant to be called from within routes rather than define new routes.

This allows them to be called at will in any other controller's route when needed:

// import the "notFound" controller logic previously defined
var throw404 = require('controllers/notFound');

module.exports = function(app) {
  app.route('/whatever').get(function(req, res) {

    // test some logic that could fail
    // thus triggering the need for the 404 controller
    if (something) {

      // logic didn't fail
      // so just render the page normally
      var model = require('models/dataModel');
      res.render('whatever', model);
    }
    else {

      // logic failed
      // so throw the 404 by executing your reusable controller
      throw404(app, req, res);
    }
  });
};

Making model files

Since the above example requires a model file named dataModel, you will need to make that too. To do that, place a file named dataModel.js in mvc/models.

Here's a simple example dataModel.js data model:

module.exports = {some: 'data'};

Making view files

Views by default are Teddy templates. See the Teddy documentation for information about how to author Teddy templates.

You can also use different templating engines by tweaking Roosevelt's parameters (see above parameter documentation).

Express variables exposed by Roosevelt

Roosevelt supplies several variables to Express that you may find handy. Access them using app.get('variableName').

Express variable Description
express The express module.
viewEngine e.g. teddy by default Any view engine(s) you define will be exposed as an Express variable. For instance, the default view engine is teddy. So by default app.get('teddy') will return the teddy module.
formidable The formidable module. Used for handling multipart forms.
appName The name of your app derived from package.json. Uses "Roosevelt Express" if no name is supplied.
appVersion The version number of your app derived from package.json.
appDir The directory the main module is in.
package The contents of package.json.
staticsRoot Full path on the file system to where your app's statics folder is located.
publicFolder Full path on the file system to where your app's public folder is located.
cssPath Full path on the file system to where your app's CSS source files are located.
jsPath Full path on the file system to where your app's JS source files are located.
cssCompiledOutput Full path on the file system to where your app's minified CSS files are located.
jsCompiledOutput Full path on the file system to where your app's minified JS files are located.
jsBundledOutput Full path on the file system to where your app's bundled JS files are located.
modelsPath Full path on the file system to where your app's models folder is located.
viewsPath Full path on the file system to where your app's views folder is located.
controllersPath Full path on the file system to where your app's controllers folder is located.
params The params you sent to Roosevelt.
port Port Roosevelt is running on.
flags Command line flags sent to Roosevelt.

Additionally the Roosevelt constructor returns the following object:

Roosevelt object members Description
expressApp The Express app created by Roosevelt.
httpServer The http server created by Roosevelt. httpServer is also available as a direct child of app, e.g. app.httpServer.
httpsServer The https server created by Roosevelt. httpsServer is also available as a direct child of app, e.g. app.httpsServer.
initServer Starts the HTML validator, sets up some middleware, runs the CSS and JS preprocessors, and maps routes, but does not start the HTTP server. Call this method manually first instead of startServer if you need to setup the Express app, but still need to do additional setup before the HTTP server is started. This method is automatically called by startServer once per instance if it has not yet already been called.
startServer Calls the listen method of http, https, or both (depending on your configuration) to start the web server with Roosevelt's config.

Express middleware and other configurations automatically provided by Roosevelt

In addition to exposing a number of variables to Express and providing the MVC interface outlined above, Roosevelt also:

  • Includes the compression middleware.
  • Includes the cookie-parser middleware.
  • Disables x-powered-by and etag.
  • Logs HTTP requests to the console using morgan, specifically morgan('combined').
  • Includes the body-parser middleware with bodyParser.json and bodyParser.urlencoded({extended: true}).
  • Includes the method-override middleware.

Warning: Roosevelt is beta software!

Not many apps have been written using Roosevelt yet, so it's entirely possible that there will be some significant bugs.

You should not use Roosevelt in production yet unless you're willing to devote some time to fixing any bugs you might find.

Contributing to Roosevelt

To contribute back to Roosevelt, fork this repo and clone it to your computer.

To run the unit tests on your code changes, run this command:

npm t

If you want to hack on the CLI tool which generates new Roosevelt apps, see generator-roosevelt.

Help wanted!

There is plenty of opportunity to help improve Roosevelt if you're interested in lending a hand. If you'd like to help, take a look at the open issues and submit a pull request!

Documentation for previous versions of Roosevelt