ideaplexus issueshttps://gitlab.com/groups/ideaplexus/-/issues2022-05-31T10:23:51Zhttps://gitlab.com/ideaplexus/matomo/-/issues/7Increase memory in config.ini.php2022-05-31T10:23:51ZMarcelIncrease memory in config.ini.phpIm currently haunted by errors like these:
```
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1098907648 bytes) in /opt/bitnami/matomo/core/Common.php on line 1151
PHP Fatal error: Allowed memory ...Im currently haunted by errors like these:
```
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1098907648 bytes) in /opt/bitnami/matomo/core/Common.php on line 1151
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1098907648 bytes) in /opt/bitnami/matomo/core/Common.php on line 1151
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1098907648 bytes) in /opt/bitnami/matomo/core/Common.php on line 1151
PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 1098907648 bytes) in /opt/bitnami/matomo/core/Common.php on line 1151
[Mon May 09 07:36:43.426952 2022] [core:notice] [pid 1] AH00051: child pid 169 exit signal Segmentation fault (11), possible coredump in /opt/bitnami/apache
[Mon May 09 07:36:43.427278 2022] [core:notice] [pid 1] AH00051: child pid 212 exit signal Segmentation fault (11), possible coredump in /opt/bitnami/apache
[Mon May 09 07:36:43.437458 2022] [mpm_prefork:notice] [pid 1] AH00169: caught SIGTERM, shutting down
```
which is solved by increasing the memory limit like so:
```
$ echo "memory_limit = 512M" >> /bitnami/matomo/config/config.ini.php
```
it would be nice if we can have a `config.ini.php` startup script, but bear in mind that matomo makes changes to this file as well, so it shouldn't be overwritten on each startup which makes it a more difficult problem.https://gitlab.com/ideaplexus/matomo/-/issues/2Persistent Volume for `config.ini.php`2022-05-31T10:23:52ZTina BurschkaPersistent Volume for `config.ini.php`Currently on each startup, a new `config.ini.php` is generated and every pod has its own config file.
This will lead to issues with a replicationCount > 1. The best solution is a PV(C) that supports ReadWriteMany.
In this case we can use...Currently on each startup, a new `config.ini.php` is generated and every pod has its own config file.
This will lead to issues with a replicationCount > 1. The best solution is a PV(C) that supports ReadWriteMany.
In this case we can use the `MATOMO_SKIP_BOOTSTRAP` on each instance and use an init container with a specific init sequence to check if the config exists and if not, initialize the bootstrap process.Version 4.xTina BurschkaTina Burschkahttps://gitlab.com/ideaplexus/matomo/-/issues/1Modification of the `config.ini.php`2022-05-31T10:23:52ZTina BurschkaModification of the `config.ini.php`In the current state, we need to modify the `config.ini.php` to enable Reverse Proxy configuration, which is mandatory in kubernetes.
```
[General]
proxy_client_headers[] = HTTP_X_FORWARDED_FOR
proxy_host_headers[] = HTTP_X_FORWARDED_HO...In the current state, we need to modify the `config.ini.php` to enable Reverse Proxy configuration, which is mandatory in kubernetes.
```
[General]
proxy_client_headers[] = HTTP_X_FORWARDED_FOR
proxy_host_headers[] = HTTP_X_FORWARDED_HOST
```
also, if TLS is enabled, the following parameters should be set as well:
```
[General]
assume_secure_protocol = 1
force_ssl = 1
```
This requires a custom startup script. Best way i see is to create a configmap with the helm generated content.Version 4.xTina BurschkaTina Burschka