Node Configuration¶
Node Configuration covers settings that apply to one Emakin agent node rather than the whole farm. Use it when you need to control execution mode, override configuration values, or protect sensitive local configuration.
Node configuration applies only to the local node and does not automatically affect remote nodes.
Execution Modes¶
The preserved documentation describes three execution modes:
- Full Mode: web server plus background-job processing
- Web Server Mode: web pages and API endpoints only
- Agent Mode: background-job processing only
For command-level behavior, see Command Line Interface.
Configuration Precedence¶
Emakin uses layered configuration. The preserved order of precedence is:
<installdir>/appsettings.json<installdir>/Configuration/Data/appsettings.json- environment variables prefixed with
AK_ <installdir>/Configuration/Data/protectedsettings.json
Environment Variable Overrides¶
Environment variables starting with AK_ override JSON settings. Nested settings use double underscores.
Examples preserved from the existing page:
1 2 | |
1 | |
Command-Line Overrides¶
Command-line arguments override all other configuration layers.
Example:
1 | |
Protected Settings¶
Sensitive values can be encrypted into protectedsettings.json instead of being stored in plain text.
Warning: The preserved documentation states that encrypted settings are write-only. If
protectedsettings.jsonis lost, the stored values cannot be read back.
Example using setconfig:
1 | |
Encryption Key Storage Location¶
The preserved documentation states that encryption keys are stored in the agent user’s home directory by default. In containers, this can fail silently if the user cannot write there.
Recommended preserved example:
1 | |
Mount this location to persistent storage in Docker or Kubernetes when protected settings must survive container restarts.