Falcon Client and Falcon Server configs work in the same way.
Falcon Client configuration can be found in the
client/config directory and Falcon Server's config is found in
The config is set up use
Each of the config files is merged to create your applications configuration.
The order in which the config files are merged is:
default.json contains shared config that can be committed to your repository (not passwords and API keys).
The name of this file depends on the config
NODE_CONFIG_ENV. For your
production environment it would be
production.json and would only be loaded on that env. For this reason this file should contain environment specific config.
This file is not committed to your repository. It can contain sensitive data such as API keys and passwords you're using for your application locally.
This file has the highest priority and should be used to map config to environment variables (set on your Node environment). These mapping can be used for sensitive data such as passwords that you wouldn't want committed to your repository.
If you're using Falcon Cloud you can set env variables using the dcloud CLI tool.
If an environment variable such as an API secret key needs to be encrypted you simply need to use the
--secret flag when setting it.