feat: new approach to multi domain

[TurtIeSocks]

A new, and much better approach to multi domain management

• Makes use of the NODE_CONFIG_ENV env variable to determine which local.json files to load
• Loads default.json => local.json => local-{NODE_CONFIG_ENV}.json
• You set all of your base defaults in local.json still, then set things that are unique to those domains, such geoJsonFilename or authentication strategies in each of the domain specifics jsons
• For now this is opt in, but when 2.0 is released, this will be the only option. multiDomains array in the config will be removed!
• The NODE_CONFIG_ENV var names should not contain / or .
• Gives access to customize the entire config per domain, not just the map object
• Docker is less elegant... example coming soon.
• More info to come

SEE README

File System

// config folder
local.json
local-map_2.json
local-map_3.json

New PM2 ecosystem.config.js Example

module.exports = {
  apps: [
    {
      name: 'ReactMap',
      script: 'ReactMap.js',
      instances: 1,
      autorestart: true,
      exec_mode: 'fork',
      max_memory_restart: '2G',
    },
    {
      name: 'ReactMap_2',
      script: 'ReactMap.js',
      instances: 1,
      autorestart: true,
      exec_mode: 'fork',
      max_memory_restart: '2G',
      env: {
        NODE_CONFIG_ENV: 'map_2',
      },
    },
    {
      name: 'ReactMap_3',
      script: 'ReactMap.js',
      instances: 1,
      autorestart: true,
      exec_mode: 'fork',
      max_memory_restart: '2G',
      env: {
        NODE_CONFIG_ENV: 'map_3',
      },
    },
  ],
}

[github-actions]

🎉 This PR is included in version 1.30.0-develop.20 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀