Re: [Health] Health Digest, Vol 43, Issue 19

[Christopher R. Kasangaki]

Dear Roberto,


Thanks a lot.
I seem to have come out of the config file problem for now and progressed to
Issue4265. That is where I am now and struggling.

Kindly let me know if you know how to resolve that one.

Cheers

Chris Kasangaki

> On February 21, 2015 at 12:20 PM Roberto Novaes
> <address@hidden> wrote:
> 
> 
> Dear Chris Kasangaki,
> 
> This is an example of a trytond config file that I use for Gnu Health 2.8
> 
> [database]
> uri = postgresql://gnuhealth:address@hidden:5432
> path = /opt/trytond_files
> 
> [jsonrpc]
> listen = *:8000
> 
> 
> [session]
> timeout = 60000
> super_pwd = joCLvw5kls/IU:
> 
> On the example above, the user and the password for the PostgreSQL database
> are gnuhealth, and it is running on localhost at port 5432 (standard for
> PostgreSQL, as you probably know). The path points to the directory that
> store tryton user files, and the owner of the trytond process must have
> permissions to read and write on this directory.
> 
> O the jsonrpc I am telling the trytond process to listen connections from
> any IP to port 8000.
> 
> Finally, on session, I use a large timeout for development (no recommended
> for production). The password for the trytond is generated using the
> commands described on Tryton documentation:
> 
> python -c 'import getpass,crypt,random,string; print
> crypt.crypt(getpass.getpass(),
> "".join(random.sample(string.ascii_letters + string.digits, 8)))'
> 
> 
> Remember that in order to trytond processe use the config file (you can
> name it whatever you want, and store it wherever you like) you must create
> an environment variable like this:
> TRYTOND_CONFIG=/my_path_to_config_file/trytond.config, for example. You can
> also start the trytond processes with -c option with the path of config
> file.
> 
> Hope it helps.
> 
> Sicerely,
> 
> Roberto Novaes
> Sílex Sistemas
> Belo Horizonte - Minas Gerais - Brazil
> www.silexsistemas.com.br