Default php settings in container seem to be insufficient for maintenace:repair to run

[nextcloud]

Default php settings in container seem to be insufficient for maintenace:repair to run

[somerandow]

I found that to work around this, you can specify the phpConfigs in your values yaml:
For example, I use:

nextcloud:
  phpConfigs:
    wojoinc-xyz.ini: |-
      upload_max_filesize=16G
      post_max_size=16G
      apc.enable_cli=1
      memory_limit=1024M

Note: The only quirk with this is that due to where the file gets created (/usr/local/etc/php/conf.d) you need to name the file to something alphabetically after 'n' or it will be overridden by the nextcloud.ini file which is also created in this folder.
Seems like these files are processed alphabetically by php, with later files taking precedence when overriding values: https://serverfault.com/a/806530

[Routhinator]

Oof, came back to running Nextcloud again after a couple of years and ended up back on my own issue haha. They should have used the numbering system for nextcloud.ini (IE 00-nextcloud.ini) based on the override order.

Testing this solution and will close this if it works.

[tvories]

@Routhinator which chart version?

[Routhinator]

2.5.15. apparently it's a new bug with Nextcloud 20+

I managed to workaround it by passing:

-d memory_limit=-1

[Routhinator]

This did work and solved the issue. Would be good to make this a part of the standard chart configs as the default 512M in the apache container is fairly small, however this works and is already exposed. Cheers @somerandow