Postgres env

[sebastienbeau]

Hi Stéphane

I see that you face the same issue as me ;) :
bcc6246

I think the best option is to pass to the container the postgres variable directly in the confd, so when you enter in the container psql work

PGHOST
PGPORT
PGUSER
PGPASSWORD
PGDATABASE

And simply removing the variable
DB_HOST
DB_PORT
DB_USER
DB_PASSWORD
DB_NAME

So we always have the postgres variable set.

In our case we have done this hack in our image (based on your)

https://github.com/akretion/odoo-docker/blob/master/bin/ak-entrypoint.sh#L10

I will be happy to remove this hack if we can directly use postgres var in confd

[sebastienbeau]

@sbidoul

[sbidoul]

Yes that would be nice.

Concerns are backward compatibility and the fact that DB_NAME may contain a comma-separated list of database names.

I had other priorities, so for we set both DB_* and PG* environment variables in the deployments.