[BUG] Setting the PQ database environment variable does not take effect

[harveyff]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hi guys, thanks for your great work.

I am deploying nextcloud on k8s. I followed the official example and specified

POSTGRES_HOST
POSTGRES_USER
POSTGRES_DB
POSTGRES_PASSWORD

as environment variables, but it does not seem to take effect. It seems that the default is SQLite database when initialized. Does it not support these environment variables?

Expected Behavior

I expect to use the external PQ database I specify by default when initializing

Steps To Reproduce

   env:
            - name: POSTGRES_PASSWORD
              value: "{{ .Values.postgres.password }}"
            - name: POSTGRES_DB
              value: "{{ .Values.postgres.databases.nextcloud }}"
            - name: POSTGRES_USER
              value: "{{ .Values.postgres.username }}"
            - name: POSTGRES_HOST
              value: "{{ .Values.postgres.host }}"

Environment

- OS:Ubuntu 22.04
- How docker service was installed:

CPU architecture

x86-64

Docker creation

env:
            - name: POSTGRES_PASSWORD
              value: "{{ .Values.postgres.password }}"
            - name: POSTGRES_DB
              value: "{{ .Values.postgres.databases.nextcloud }}"
            - name: POSTGRES_USER
              value: "{{ .Values.postgres.username }}"
            - name: POSTGRES_HOST
              value: "{{ .Values.postgres.host }}"

Container logs

Environment variables are not effective

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[j0nnymoe]

This isn't a bug, these env's don't work on our container. If they did, they would be listed in our readme.

[harveyff]

This isn't a bug, these env's don't work on our container. If they did, they would be listed in our readme.

Thanks for your reply. Well, I didn't read the document carefully.

Can I know why it is not supported? The official image user permissions are a problem. I have to use our image.

But the inability to use an external database by default is a problem, because I want to deploy it to our application market and let many users click to install it. If I can use those environment variables, I will be very grateful.

[j0nnymoe]

External database work fine with our container. We just expect the end user to configure it via the nextcloud setup wizard.

[harveyff]

External database work fine with our container. We just expect the end user to configure it via the nextcloud setup wizard.

OK, I understand. Thanks for your reply. The plain text setting is indeed possible.

I mean, it can be like the official image. If the DB environment variables are preset, the init page will hide the database elements. This is more automated.

[aptalca]

You can also feed it a config file with all that info in if you want it to be set up without the wizard. But then again how often do you set up Nextcloud? It's one of those things that's technically possible but not worth the dev time considering the minimal and likely one time effort and time savings.