Skip to content

Commit

Permalink
opt-in ENABLE_POSTGRES_USER for Docker usage anybox#63
Browse files Browse the repository at this point in the history
This new env var enables to skip the postgres user check. This can be handy when linking to some default Postgres containers.
See anybox#63
  • Loading branch information
rvalyi committed Oct 13, 2015
1 parent 449dc8c commit c650d77
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 1 deletion.
3 changes: 2 additions & 1 deletion anybox/recipe/odoo/runtime/session.py
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,8 @@ def open(self, db=None, with_demo=False):
cr.close()

startup.check_root_user()
startup.check_postgres_user()
if not os.environ.get('ENABLE_POSTGRES_USER'):
startup.check_postgres_user()
openerp.netsvc.init_logger()

saved_without_demo = config['without_demo']
Expand Down
8 changes: 8 additions & 0 deletions doc/scripts.rst
Original file line number Diff line number Diff line change
Expand Up @@ -248,6 +248,14 @@ object is available for interacting with your odoo application and database.
Keep in mind that ``bpython`` requires more system dependencies installed than
plain ``odoo``.

Note that Odoo forbids using the ``postgres`` user to connect to the database.
But in some containerized environments (Docker), using ``postgres`` can be
both safe and handy. In such case you would need to patch the Odoo server as
of today. But for the interactives sessions of this buildout recipe, you can
set the environment variable ENABLE_POSTGRES_USER=1 before opening the console
to disable the default ``check_postgres_user()`` guard and enable the postgres
user.

Writing Odoo Scripts
~~~~~~~~~~~~~~~~~~~~

Expand Down

0 comments on commit c650d77

Please sign in to comment.