properties-gen v1.1.2

properties-gen

CLI that generates properties files for a given environment.

Motivation

You need to build your application for different targets, so you have a base configuration file with default values and want to override specific ones for the rest of the targets.

This way you dont need to define every dynamic value by using environment variables.

Features

• extends from base file
• parse env variables
• output configuatio as JSON or JS files

Installation

Locally in your project.

$ npm install -D properties-gen

or globally

$ npm install -g properties-gen

Install with yarn

$ yarn i properties-gen --save-dev

command line options

Usage: properties-gen [options] [command]

Options:
  -h, --help          display help for command

Commands:
  init                Generates default config file
  generate [options]  Generates environment properties files
  help [command]      display help for command

Options for generate command:

Usage: properties-gen generate [options]

Generates environment properties files

Options:
  -f, --file [pathToFile]  Specify configuration file
  -h, --help               display help for command

Usage

Configuration

Generate the initial configuration file

$ npx properties-gen init

This will create a properties.config.json file in your root directory, notice you can define as many properties files as you need (groups in the configurationGroups array), usually we just need client, server or both.

{
  "configurationGroups": [
    {
      "inputFolder": "config/server/",
      "inputFileNamePattern": "env.{{envTargetKey}}.json",
      "outputFile": "environment/env.server.js",
      "extendsFromBase": true,
      "fileBaseName": "base.json"
    },
    {
      "inputFolder": "config/client/",
      "inputFileNamePattern": "env.{{envTargetKey}}.json",
      "outputFile": "environment/env.client.js",
      "extendsFromBase": true,
      "fileBaseName": "base.json"
    }
  ],
  "envTargetKey": "NODE_ENV",
  "defaultEnvTargetValue": "dev"
}

Define your configuration files

For each configuration group, create the folder that contains the base.json (if extendsFromBase is true) and as many env.{ENV}.json files as you need, for example:

config/server/base.json

{
  "isProduction": false,
  "someKey": "someValue",
  "msHost": "http://localhost:3010/",
  "db": {
    "someSecret": "{{SECRET}}"
  }
}

Overrite and extend values for the rest of environments.

config/server/env.dev.json

{
  "msHost": "http://api.dev.myapp.com"
}

config/server/env.prod.json

{
  "isProduction": true,
  "msHost": "https://api.myapp.com/"
}

Generate environment files

npx properties-gen generate

This command will take the current environment to generate the properties file in the location defined on outputFile. Notice NODE_ENV is the default key for the environments but you can override this value by setting a different one in envTargetKey like COUNTRY or TENANT.

Example:

NODE_ENV=prod SECRET=mySecret npx properties-gen generate

output: environment/env.server.js

module.exports = {
  isProduction: true,
  someKey: 'someValue',
  msHost: 'https://api.myapp.com/',
  db: {
    someSecret: 'mySecret',
  },
}

Tip: use npx properties-gen init to create the configuration file, then install properties-gen as a development dependency in your project and finally chain the properties-gen generate command before the start|dev|build command, so properties are generated before running the project.

Tip: you may want to add the output file to .gitignore as is not meant to be tracked

Package script example using NextJs

package.json

{
  "name": "myApp",
  "scripts": {
    "config": "properties-gen generate",
    "dev": "npm run config && next dev",
    "build": "npm run config && next build",
    "start": "next start"
  }
}