Dear Tryton group,

I just discovered Tryton and was quite surprised not to have heard
about it before. After using the demo, it seems to be very potent, and
I would like to use it for my virtual assistance business.
However: I am not particularly experienced with database handling, so
I am uncertain on how to install it and make it work.
I am trying to make it fly on Slackware 13.37. I have done the
following:
* Installed Trytond and Tryton as described on 
http://www.tryton.org/downloads.html
- except that I used Pip instead of easy_install, which should not
make a difference.
* Installed PostgreSQL following the instructions from
http://slackbuilds.org/repository/13.37/system/postgresql/ and
creating the relevant user data as mentioned.
I am not sure I did the database part correctly, though.
* Looking at http://code.google.com/p/tryton/wiki/SetupAndStart, I add
the Postgres user. Now, when I start Trytond, it outputs:
~ $ trytond
[Thu May 26 12:19:58 2011] INFO:server:using default configuration
[Thu May 26 12:19:58 2011] INFO:server:initialising distributed
objects services
[Thu May 26 12:19:58 2011] DEBUG:psycopg2:installed. Logging using
Python logging module
[Thu May 26 12:19:58 2011] INFO:modules:ir:registering classes
[Thu May 26 12:19:58 2011] INFO:modules:res:registering classes
[Thu May 26 12:19:58 2011] INFO:modules:test:registering classes
[Thu May 26 12:19:58 2011] INFO:modules:webdav:registering classes
[Thu May 26 12:19:58 2011] INFO:modules:workflow:registering classes
[Thu May 26 12:19:58 2011] INFO:server:starting NetRPC protocol, port
8070
[Thu May 26 12:19:58 2011] INFO:server:waiting for connections...
[Thu May 26 12:20:24 2011] INFO:database:connect to "template1"
[Thu May 26 12:20:27 2011] INFO:database:connect to "template1"

If I call postgres, it tells me that it does not know where to find a
server config file.
Also, I don't seem to have a config file at /etc/trytond.conf

I may be confusing myself, but I hope that you will take the time to
send me some pointers.

Sincerely,
Morten

-- 
[email protected] mailing list

Reply via email to