Unable to configure the helm chart appropriately for preexisting empty postgres db about helm HOT 5 CLOSED

I went ahead and created my own nextcloud manifest instead of using this helm chart and everything works. Not sure whats up here but since I'm not using the helm chart anymore I'm going to close out the issue.

from helm.

Can you check that the values in the config.php file match your credentials? They are only set once at the start so they might not be up-to-date

from helm.

I've gone and deleted the persistent volume that I'm managing outside of this and started from scratch. I can see the proper values in the install page on the nextcloud web page after it starts up. The password I enter fails there too. I'm copying it from the same password vault I use for testing with the psql command. Still, during initial startup or when I use the web install it just fails to connect to the DB.

from helm.

I did notice this about the config.php file though and it seems off. Unclear where the newline is coming from but my env variable doesn't seem to have one. :

',  
'dbpassword' => '$MYPASSWORD  
',

Alas, even if I manually fix this and restart apache2 with apache2 graceful or apache2 restart the service still comes back up and greets me with the install screen and no password works to configure the DB on the web installer either.

from helm.

To be explicit here. I'm running my own postgres server and not using the option to use the bitnami subchart. The IP and domain names both work if I use psql client directly installed with apt on the image. In my testing I pull directly from the env variables. I also try those variables on the web installer and no dice.

Also, I never run my helm commands with the set flag as suggested because I figure thats taken care of with the custom values file. Also figure since the env variables are set and correct I shouldn't need the flag in addition. Let me know if that is not true.

from helm.