You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since Odoo 8.0 is a bit... complicated about the connection variables, I suggest we could "normalize" the connection parameter to set the --db_* argument ANDPG* env variables to make sure all the situations are covered.
Current Priorities
--db_host, then PGHOST, ... (then localhost or /run/postgresql)
--db_port, then PGPORT, ... (5432)
--db_user, then LOGNAME, then die
--db_password, then PGPASSWORD
During a backup on Odoo 8.0, it's a bit different...
--db_host, then PGHOST, ... (then localhost or /run/postgresql)
--db_port, then PGPORT, ... (5432)
--db_user, then LOGNAME, then die
PGPASSWORD, then --db_password, then none
The text was updated successfully, but these errors were encountered:
We've finally been bitten by this kind of things (see a3d207f). I'm closing this as we now only use the --db* arguments in the Docker file but we have opened a task to clarify and fix these issues upstream.
Since Odoo 8.0 is a bit... complicated about the connection variables, I suggest we could "normalize" the connection parameter to set the
--db_*
argument ANDPG*
env variables to make sure all the situations are covered.Current Priorities
--db_host
, thenPGHOST
, ... (then localhost or /run/postgresql)--db_port
, thenPGPORT
, ... (5432)--db_user
, thenLOGNAME
, then die--db_password
, thenPGPASSWORD
During a backup on Odoo 8.0, it's a bit different...
--db_host
, thenPGHOST
, ... (then localhost or /run/postgresql)--db_port
, thenPGPORT
, ... (5432)--db_user
, thenLOGNAME
, then diePGPASSWORD
, then--db_password
, then noneThe text was updated successfully, but these errors were encountered: