<commit_before># Configuration

Since version 0.6.0 we are moving away from environment-specific config files and introducing environment variables-enhanced configuration system via `.env` files (see below). For that reason you will notice that the entire root `/config` directory is now gone.


## Default config

[Default config](https://github.com/projectshift/shift-boiler/blob/master/boiler/config.py#L33) is now always applied to your app first before any other config to give you a set of sensible defaults that you can override by running your app with a minimal focused config.

This is a great improvement that allows us to significantly simplify config inheritance, since now your configs do not have to extend from default base config and after eliminating root `/config` we do not have to use multiple inheritance which always caused issues that where tricky to debug (what config is this setting coming from?). Everything is much more straightforward now:

  * First we apply default config
  * Then you custom config is applied on top of that

In addition every config now follows a clear inheritance from the base configs provided by boiler. here is an example of minimal application config:

```python<commit_msg>Update config.md<commit_after># Configuration

Since version 0.6.0 we are moving away from environment-specific config files and introducing environment variables-enhanced configuration system via `.env` files (see below). For that reason you will notice that the entire root `/config` directory is now gone.


## Default config

[Default config](https://github.com/projectshift/shift-boiler/blob/master/boiler/config.py#L33) is now always applied to your app first before any other config to give you a set of sensible defaults that you can override by running your app with a minimal focused config.

This is a great improvement that allows us to significantly simplify config inheritance, since now your configs do not have to extend from default base config and after eliminating root `/config` we do not have to use multiple inheritance which always caused issues that where tricky to debug (what config is this setting coming from?). Everything is much more straightforward now:

  * First we apply default config
  * Then you custom config is applied on top of that

In addition every config now follows a clear inheritance from the base configs provided by boiler. Here is an example of minimal application config:

```python
{'fraction_non_alphanumeric': 0.04425497360941941, 'fraction_numerical': 0.004060089321965083, 'mean_word_length': 4.716937354988399, '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': '2075477', 'n_tokens_mistral': 560, 'n_tokens_neox': 531, 'n_words': 354}