All-in-one installer could warn if existing postgres install needs additional config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Wishlist
|
Stephane Wirtel (OpenERP) |
Bug Description
The GTK client of OpenERP uses Postgres as database engine for its server setup in a all in one installation setup. But the connection needs a user with superadmin privileges to create a new db to start using the resident OpenERP GTK client. This calls for either configuration of existing postgres DB for openERP database instances or a new postgres installation in case the resident user doesn't have Postgres installed. But in my case there was no configuration step for existing postgres DB (I had one installed) in installation process. All the settings and connection to DB was possible only after contacting the support team, as the team suggested that i manually create a superadmin user named as openpg in my postgres for which i had to check the config file open-erp.conf which was configured in conf file which was part of installer. Here there is no wizard provided between GTK and postgres by the installer.
Changed in openobject-server: | |
status: | New → Triaged |
Indeed, if postgres is already installed the current all-in-one installer does not warn that you need to setup the proper access rights in postgres. In fact it assumes that another all-in-one was previously installed and the user knows how this works.
We could add a warning message during installation if we don't install postgres, so that the user verifies that the configuration is correct.
Assigning to Stephane who has rewritten the all-in-one installer already (maybe it's already supported)