Technical Specifications

Welcome to the Moranda wiki!

Development Environment

Using StandardJS coding convention and its associated linter / formatter for atom.

Atom packages for StandardJS:

• Standard-formatter
• Base Linter
• StandardJS plugin for Base Linter

Notes:

Look into node-inspector

Look into Gulp ... Cons

Things I would want in my task runner:

• Watch
  • nodemon
• LiveReload for browser development
• Linting (maybe using StandardJS)
• minifying static front-end assets
• Zipping (using Gzip?)
• Bundling like static assets (not necessary right now)
  • Note that concatenation === Bundling
• Spriting Images
• Unit Testing
• continuous development (not having to recompile code when making changes to codebase) ... Done through Watch?

Need different tasks for whether I'm in development or in production (i.e. I wouldnt want bundling / minification during dev)

NodeJS Best Practices

Make use of the different Heroku environments

Continuous Integration

Have an integration flow, potentially using Travis or CodeShip, or Circle.

• Heroku Codeship Setup

Logging

Look into Winston for logging

npm install --save winston

let logger = require('winston')

logger.info('east coast clear as day')
logger.error('west coast not looking so hot')

Asset Caching

Static asset caching is something we might want in the future but for now is unimportant.

Heroku Buildbacks

Gulp Buildpack