<commit_before># APIcast parameters

APIcast v2 has a number of parameters configured as environment variables that can modify the behavior of the gateway. The following reference provides descriptions of these parameters.

Note that when deploying APIcast v2 with OpenShift, some of thee parameters can be configured via OpenShift template parameters. The latter can be consulted directly in the [template](https://raw.githubusercontent.com/3scale/apicast/v2/openshift/apicast-template.yml).
 
- `APICAST_CUSTOM_CONFIG`
 
 Defines the name of the Lua module that implements custom logic overriding the existing APIcast logic. Find more information about custom config in [the documentation](/doc/custom-config.md).

- `APICAST_LOG_FILE`  
 **Default:** _stderr_
 
 Defines the file that will store the OpenResty error log. It is used by `bin/apicast` in the `error_log` directive. Refer to [NGINX documentation](http://nginx.org/en/docs/ngx_core_module.html#error_log) for more information. The file path  can be either absolute, or relative to the prefix directory (`apicast` by default) 

- `APICAST_LOG_LEVEL`  
 **Values:** debug | info | notice | warn | error | crit | alert | emerg
 **Default:** warn
 
 Specifies the log level for the OpenResty logs.

- `APICAST_MISSING_CONFIGURATION`  
 **Values:** log | exit  
 **Default:** log
 
 Used to define what APIcast should do when the configuration is missing at the initialization time. By default (_"log"_), the gateway will start successfully, and print an error message notifying of missing configuration. If set to _"exit"_, the gateway will fail to start.

- `APICAST_MODULE`  
 **Default:** "apicast"
 
 Specifies the name of the main Lua module that implements the API gateway logic. Custom modules can override the functionality of the default `apicast.lua` module. See [an example](/examples/custom-module) of how to use modules.

- `APICAST_PATH_ROUTING_ENABLED`  
 **Values:**
 - `true` or `1` for _true_
 - `false`, `0` or empty for _false_
 
 When this parameter is set to _true_, the gateway will use path-based routing instead of the default host-based routing. Learn more about the path routing mode in [the documentation](/doc/path-routing.md).

- `APICAST_RELOAD_CONFIG`  
 **Values:**
 - `true` or `1` for _true_
 - `false`, `0` or empty for _false_
 
 When this parameter is set to _true_ the configuration will be reloaded on every request. This is useful for development and testing, however it is highly discouraged to use it in production environment.

- `APICAST_REQUEST_LOGS`<commit_msg>Remove the links to other documents until they are created<commit_after># APIcast parameters

APIcast v2 has a number of parameters configured as environment variables that can modify the behavior of the gateway. The following reference provides descriptions of these parameters.

Note that when deploying APIcast v2 with OpenShift, some of thee parameters can be configured via OpenShift template parameters. The latter can be consulted directly in the [template](https://raw.githubusercontent.com/3scale/apicast/v2/openshift/apicast-template.yml).
 
- `APICAST_CUSTOM_CONFIG`
 
 Defines the name of the Lua module that implements custom logic overriding the existing APIcast logic.

- `APICAST_LOG_FILE`  
 **Default:** _stderr_
 
 Defines the file that will store the OpenResty error log. It is used by `bin/apicast` in the `error_log` directive. Refer to [NGINX documentation](http://nginx.org/en/docs/ngx_core_module.html#error_log) for more information. The file path  can be either absolute, or relative to the prefix directory (`apicast` by default) 

- `APICAST_LOG_LEVEL`  
 **Values:** debug | info | notice | warn | error | crit | alert | emerg
 **Default:** warn
 
 Specifies the log level for the OpenResty logs.

- `APICAST_MISSING_CONFIGURATION`  
 **Values:** log | exit  
 **Default:** log
 
 Used to define what APIcast should do when the configuration is missing at the initialization time. By default (_"log"_), the gateway will start successfully, and print an error message notifying of missing configuration. If set to _"exit"_, the gateway will fail to start.

- `APICAST_MODULE`  
 **Default:** "apicast"
 
 Specifies the name of the main Lua module that implements the API gateway logic. Custom modules can override the functionality of the default `apicast.lua` module. See [an example](/examples/custom-module) of how to use modules.

- `APICAST_PATH_ROUTING_ENABLED`  
 **Values:**
 - `true` or `1` for _true_
 - `false`, `0` or empty for _false_
 
 When this parameter is set to _true_, the gateway will use path-based routing instead of the default host-based routing.

- `APICAST_RELOAD_CONFIG`  
 **Values:**
 - `true` or `1` for _true_
 - `false`, `0` or empty for _false_
 
 When this parameter is set to _true_ the configuration will be reloaded on every request. This is useful for development and testing, however it is highly discouraged to use it in production environment.

- `APICAST_REQUEST_LOGS`
{'fraction_non_alphanumeric': 0.07586344579756438, 'fraction_numerical': 0.003194250349371132, 'mean_word_length': 4.475409836065574, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4180017', 'n_tokens_mistral': 1418, 'n_tokens_neox': 1349, 'n_words': 635}