| 40 | | The default value of this parameter is set to `on`, so you have to specifically set it to `off` to disable it. It is set to `off` in the development environment to allow live modifications of the configuration. |
|---|
| 41 | | |
|---|
| 42 | | This means that if you decide to add caching to one of your apps, you will not be able to see the effect of it in the development environment with the default configuration. The boost given by HTML caching is only perceptible in the production environment - or in any other environment where `cache: on`. |
|---|
| 43 | | |
|---|
| 44 | | One other cache parameter can be changed in the `settings.yml` file: The default cache lifetime, i.e. the number of seconds after which a cached file is overwritten and the page processed again. The default `default_cache_lifetime` is set to one day, or 86400 seconds. |
|---|
| | 40 | The default value of this parameter is set to `off`, so you have to specifically set it to `on` to enable it. |
|---|
| | 41 | |
|---|
| | 42 | It is set to `off` by default in the development environment. This means that if you decide to add caching to one of your apps, you will not be able to see the effect of it in the development environment with the default configuration. |
|---|
| | 43 | |
|---|
| | 44 | Consequently, the boost given by HTML caching is only perceptible in the production environment - or in any other environment where `cache: on`. |
|---|
| | 45 | |
|---|
| | 46 | One other cache parameter can be changed in the `settings.yml` file: The default cache lifetime i.e., the number of seconds after which a cached file is overwritten and the page processed again. The default `default_cache_lifetime` is set to one day, or 86400 seconds. |
|---|
