Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opt-in BUILDOUT_SKIP_PG_USER_CHECK #63 #64

Merged
merged 1 commit into from
Oct 14, 2015
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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