API Server
Provisioning
Provisioning is step after server is started and API becomes available.
It allows you to directly influence how a fresh Corteza instance is configured on first run.
This entire process can be disabled by setting env. variables PROVISION_MIGRATE_DATABASE
and PROVISION_CONFIGURATION
to false
.
Type | Default value | Description |
---|---|---|
|
||
|
|
Controls if database migration (creation of tables, changes of schema between versions) should be done before each service is started. It’s recommended to keep this setting on. Disabling it on a running server prevents migration between version udpates |
|
||
|
|
Runs various auto-setup procedures and creates resources: - creates default permission rules and roles - default channels are created - default applications are created - compose resources (namespaces, modules, charts,…) - settings auto-discovery |
Type | Default value | Description |
---|---|---|
|
||
|
||
|
|
Is OAuth2 enabled or disabled OAuth2 flow redirection URL. |
|
||
|
||
|
searches env-variables ( |
|
|
||
|
||
|
|
generated 64 char long string if missing. Is session cookie "secure" flag used (if yes, cookie can only be access over HTTPS). |
|
||
|
||
|
|
If HTTPS is used for external auth redirection url, value is set to true. |
|
||
|
||
|
Where the frontend SPA is located. Serves as base for generating other |
|
|
||
|
||
|
Where the frontend SPA is located, the password reset form. Where the frontend SPA is located, password email confirmation page. |
|
|
||
|
||
|
|
|
|
||
|
||
|
Where the frontend SPA is located. User will be redirected here on successful external authentication.
Auto discovery uses |
|
|
||
|
||
|
Email address used for sending auth emails (password reset, email confirmation) Name used for sending auth emails (password reset, email confirmation) |
|
|
||
|
||
|
Corteza Team (to-be-configured) Is internal auth enabled? Enable this to allow users to use all (enabled) internal features (sign-up, log in….) |
|
|
||
|
||
|
|
|
|
||
|
||
|
|
Is internal sign-up enabled? Enable this to allow users to register if you do not have external authentication providers. |
|
||
|
||
|
|
Is email confirmation required for internal sign-ups?
Enabled on auto-discovery if server has email capabilities ( |
|
||
|
||
|
|
Is password reset enabled for internal account?
Auto-discovery enables this if server has email capabilities ( |
Type | Default value | Description |
---|---|---|
|
||
|
Registers all given providers on start.
Provide a list of space delimited provider pairs ( The provider is auto-discovered only if it does not exist (match by name). Also, make sure that your redirect URL ( |
|
|
||
|
Sets value for This should be set to: |
Type | Default value | Description |
---|---|---|
|
||
|
Github’s app credentials: |
|
|
||
|
Facebook’s app credentials: |
|
|
||
|
Google’s app credentials: |
|
|
||
|
LinkedIn’s app credentials: |
|
|
||
|
OIDC provider settings |
Server options
Type | Default value | Description |
---|---|---|
|
||
|
|
Enable/disable Corredor integration |
|
||
|
|
Hostname and port of the Corredor gRPC server |
|
||
|
|
Log communication with Corredor |
|
||
|
|
Max delay for backoff on connection |
|
||
|
Instructions passed to Corredor on every call - where Corteza API is located. |
|
|
||
|
Instructions passed to Corredor on every call - where Corteza API is located. |
|
|
||
|
Instructions passed to Corredor on every call - where Corteza API is located. |
|
|
||
|
|
Database connection string <username>:<password>@(<host>:<port>)/<dbname>?collation=utf8mb4_general_ci |
|
||
|
|
Log SQL queries |
|
||
|
|
Max number of connection retries |
|
||
|
|
How long do we wait between retries |
|
||
|
|
For how long do we try to connect |
|
||
|
|
Network to use for gRPC |
|
||
|
|
Where do we listen for gRPC connections |
|
||
|
|
Max delay for backoff on connection |
|
||
|
|
Log gRPC communication |
|
||
|
|
IP & port for HTTP server |
|
||
|
|
Log requests |
|
||
|
|
Log responses |
|
||
|
|
Enable /version route |
|
||
|
|
Enable /debug route |
|
||
|
|
Enable (prometheus) metrics |
|
||
|
|
Name for metrics endpoint |
|
||
|
|
Username for metrics endpoint |
|
||
|
|
Password for metrics endpoint |
|
||
|
Report panic to Sentry |
|
|
||
|
|
Allow insecure (invalid, expired TSL/SSL cert) |
|
||
|
|
Default timeout for clients |
|
||
|
|
Secret used for signing JWT tokens |
|
||
|
|
Expiration time |
|
||
|
|
Output (log) interval for monitoring |
|
||
|
|
Migrate database (if needed) on server start |
|
||
|
|
Import configuration (only on empty database) on server start |
|
||
|
Set to enable Sentry client |
|
|
||
|
|
Print out debugging information |
|
||
|
|
Attach stacktraces |
|
||
|
Sample rate for event submission (0.0 - 1.0, defaults to 1.0) |
|
|
||
|
Maximum number of breadcrumbs |
|
|
||
|
Set reported Server name |
|
|
||
|
|
Set reported Release |
|
||
|
Set reported distribution |
|
|
||
|
Set reported environment |
|
|
||
|
|
|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
|
Where do we store uploaded files |
|
||
|
||
|
||
|
|
|
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
|
Delaying API execution
With WAIT_FOR*
Delaying API execution, waiting for external (HTTP) services.
This might aid you in complex setup where another service should be running and accessible before Corteza is ready.
Type | Default value | Description |
---|---|---|
|
||
|
|
Delays API startup for the amount of time specified (10s, 2m…). This delay happens before service (WAIT_FOR_SERVICES) probing. |
|
||
|
|
Show temporary status web page. |
|
||
|
Space delimited list of hosts and/or URLs to probe.
Host format: Services are probed in parallel. |
|
|
||
|
|
Max time for each service probe. |
|
||
|
|
Timeout for each service probe. |
|
||
|
|
Interval between service probes. |