Backend Configuration
The EZY WMS backend (ezy-wms-backend/Service) is configured through two mechanisms:
-
appsettings.json— The main .NET configuration file controlling host settings, logging, database connections, JWT secrets, session management, licensing, SMTP, and background service parameters. -
Service/config/folder — A set of YAML files that define business behavior, data handling, and UI surface area. These files are reloaded at service startup.
Configuration Files
Section titled “Configuration Files”| File | Purpose |
|---|---|
appsettings.json | .NET host, logging, database, JWT, sessions, licensing, SMTP, background services |
config/Configurations.yaml | Mandatory. Core business options, data filters, warehouse mappings, SAP B1 connection details |
config/CustomFields.yaml | Extra item and document fields exposed in the UI |
config/Item.yaml | Editable item metadata definitions |
config/Package.yaml | Package label, barcode, and metadata configuration |
config/ExternalCommands.yaml | XML/JSON exports triggered by events or manual buttons |
config/PickingPostProcessing.yaml | Custom .NET processors that run after picking operations |
Defaults and Initialization
Section titled “Defaults and Initialization”The Service/init/ folder contains default copies of all configuration files. These defaults are used to seed the Service/config/ folder on first run. During deployment, place your environment-specific overrides in Service/config/ — the init folder is not modified.
Conventions
Section titled “Conventions”- Reload on startup: All YAML configuration files are parsed when the service starts. Configuration changes require a service restart.
- Case sensitivity: YAML is case-sensitive. Property names and enum values must match their definitions exactly.
- No credentials in version control: Never commit real database passwords, API keys, SMTP credentials, or SAP B1 logons to the repository. Use environment variables or secure deployment practices to inject them at runtime.