s2m-env-config v0.0.1

Configurations

Simple tool to store and build configs for modules

Development

Common data

All common configurations, such as AWS system access keys, are stored in the src/basic.js file. They can be used in other custom configurations.

Custom configs

Configs for each service (module) are stored in the corresponding folder by module name (module name without spaces).

The configuration of the service (module) for each individual stand should be stored in a separate file by the name of the stand.

Configs for local development should be stored in the local.js file.

How build configs for particular module and stand

1. clone project
2. open console in the project directory
3. exec comman npm i
4. exec comman npm run build -- -module {module-name} -stand {stand-name} where - {module-name}: name of the service (module) for which we want to build the config, without brackets - {stand-name}: name of the stand for which we want config will be use, without brackets, or use local for local development
5. if config for pointed stand and module not found - there are will error shown in the console
6. if config was found - there are will be created file config/default.json
7. copy created folder config to the root of the module directory
8. done