Making the backend recognize different environments

But we are not yet done and need to refrain from opening our app just yet.

What's the problem?

Until now, we only used the database when running the specs. Now we have another client for the web service (and the underlying database), and this is the frontend application. We probably don't want our specs to wipe out the data we add through the application. We can circumvent this problem by using the different environments we created for db-migrate. Each environment has its own database setup, and this way we can keep things neatly separated – our specs work with one database setup, and the application with another one.

We need to add a helper script that detects the current environment when executing our code. Place this into src/backend/env.js:

'use strict';
(function() {
  var env;

  if (process.env.KW_ENV) {
    env = process.env.KW_ENV...