On 19/07/13 10:13 -0600, Mark Hayden (local) wrote: > On Fri, 2013-07-19 at 17:33 +0200, Cédric Krier wrote: > > > > # Configure the database connection > > > > ## Note: Only databases owned by db_user will be displayed in the > > > > connection > > > > dialog > > > > ## of the Tryton client. db_user must have create permission for new > > > > databases > > > > ## to be able to use automatic database creation with the Tryton client. > > > > #db_host = False > > > > #db_port = False > > > > #db_user = False > > > > #db_password = False > > > > > > I am pretty sure the above four DB_* parameters are NOT optional, even > > > for local databases. I do not know the default values for these if they > > > are optional. So, to be safe I would suggest you explicitly supply them > > > as such: > > > > > > db_host = 127.0.0.1 # the hostname localhost should work here too--if it > > > doesn't you'd have bigger problems ;-) > > > db_port = 5432 > > > > Only if you want to use TCP socket. > > That makes sense. How about username and password? Axel's file had > "peer" for auth method in pg_hba for "local" (unix socket) connections > which would get the user name from the OS--presumably the user account > running the trytond process. If no user name or password are supplied > in the Tryton config would that be the assumed setup?
The user that is running trytond. > In that case I > would guess that without any DB settings in the Tryton config file that > a person could handle this by making sure trytond is running under a > user account with the same name as the database owner in PostgreSQL. Yes. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgppMqHW6pbGl.pgp
Description: PGP signature
