Jesse Hitch

Also wanted to note we added a `nextcloud.trustedDomains` parameter to this helm chart in `5.4.0`: https://github.com/nextcloud/helm/releases/tag/nextcloud-5.4.0

Since it's taking a bit for my PR to be merged upstream, I'll try to spend some time on this later today to get it ready for merge _without_ the...

I've removed the encryption key setting for now, so this could still be merged, but I haven't tested this, so it should still wait another week or two while I...

No, I just was just really busy before. Let me take a look at the code now and see what's left to be done here :)

gonna take a peak locally and push up some changes as https://github.com/nextcloud/docker/pull/2151 was merged so we now have encryption as well :)

This should be ready for review now :) Unless #480 gets merged first, then I need to update this PR again.

Sounds good to me :)

As discussed in #480, I will refactor this to use the new config file format and then we can review and merge.

Actually, in the interest of resolving https://github.com/nextcloud/helm/issues/477, should I just go ahead and add the following to the values? ```yaml nextcloud: objectStore: s3: enabled: true # ignored if nextcloud.objectstore.s3.existingSecret is...

> How about adding the other missing configs (especially https://github.com/nextcloud/docker/blob/master/.config/upgrade-disable-web.config.php) and checking if the other ones are up-to-date? Sure, why not :)