Configure your local SMTP server or use one of the available providers.
These values are copied to settings when the server starts and can be managed from the administration console. We recommend you remove these values after they are copied to settings. If server detects difference between these options and settings, it shows a warning in the log on server start.
Password security allows you to disable constraints to which passwords must conform to.
Disabling password security can be useful for development environments as it removes the need for complex passwords. Password security should be enabled on production environments to avoid security incidents
Log filtering rules by level and name (log-level:log-namespace). Please note that level (LOG_LEVEL) is applied before filter and it affects the final output!
Leave unset for production.
Log warnings, errors, panic, fatals. Everything from auth and workflow is logged.
See more examples and documentation here: https://github.com/moul/zapfilter
The MinIO integration allows you to replace local storage with cloud storage. When configured,
STORAGE_PATH is not needed.
Provisioning allows you to configure a Corteza instance when deployed. It occurs automatically after the Corteza server starts.
We recommend you to keep provisioning enabled as it simplifies version updates by updating the database and updating settings.
If you’re doing local development or some debugging, you can disable this.
These parameters help in the development and testing process. When you are deploying to production, these should be disabled to improve performance and reduce storage usage.
You should configure external services such as Sentry or ELK to keep track of logs and error reports.
You can configure these options to defer API execution until another external (HTTP) service is up and running.
[ TIP ]
Delaying API execution can come in handy in complex setups where execution order is important.