Home

Table of Contents

• Overview
• [Getting started with BlueOak Server](Getting Started)
• Services
  • Creating services
  • Included Services
    • Config
    • Logger
    • Cache
    • Monitor
• Handlers
  • Express
  • Swagger
• Middleware
  • Included Middleware
    • CORS
    • CSRF
    • Body parser
    • Session
    • Monitor
    • express-static
• Configuration
  • SSL
  • Clustering
• Writing Tests
• Advanced Topics
  • Launching
  • Error handling
  • Crash dumps
• [Project Structure](Project Structure)

Overview

The goal of BlueOak server is to embody in executable code the philosophy and strategies we've uncovered while build custom mobile backends in Node.js. Using BlueOak server we've improved our ability to develop high-quality code quickly, to deploy with ease and confidence, and to decrease the complexity of the running system.

One of the key advantages of using BlueOak server when creating a custom API, is that the same swagger specs are used to generate documentation (using swagger-ui), to expose the API to the network, and to validate requests.