Core Corteza services are configured via the environment (
It allows a quick deploy to another platform, along with fine-tuning the system’s behaviour and enabled features.
.envfile affects three levels:
Implicit Docker Compose configuration,
variable substitution in Docker configuration,
When you are using Docker Compose, you must explicitly reference the environment file for each service in the
You can use variables defined in the
Connection to data store backend
Configure your local SMTP server or use one of the available providers
Connection to Corredor
Events and scheduler
Object (file) storage
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.
Data store (database) upgrade
Delay system startup
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.