Cryptoman: Created page with "'''.ini file:''' When either the OT Server (transaction.exe), or the OT command-line test client (testwallet.exe) starts up, it tries to read from the ini file. The '''locati..."

2013-06-12T13:48:09Z

Created page with "'''.ini file:''' When either the OT Server (transaction.exe), or the OT command-line test client (testwallet.exe) starts up, it tries to read from the ini file. The '''locati..."

New page

'''.ini file:'''

When either the OT Server (transaction.exe), or the OT command-line test client (testwallet.exe) starts up, it tries to read from the ini file. The '''location of the ini file''' is subject to change but for now, it is: <code>C:\ot.ini</code> (Windows systems) <code>~/.ot_ini</code> (Non-Windows)

If the ini file fails opening, then OT will assuming the data_folder path is: <code>./data_folder</code>

The ini file currently only stores the DEFAULT PATHS for the data_folder. Here's the ini file on my system (located at <code>~/.ot_ini</code>):

<pre>
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Open-Transactions ini file

[paths]
client_path=/Users/au/Projects/Open-Transactions/testwallet/data_folder
server_path=/Users/au/Projects/Open-Transactions/transaction/data_folder
</pre>
(You don't ''have'' to use the .ini file, it's just a convenience. You'll otherwise have to provide these paths explicitly, whenever you start OT.)

'''Eventually the ini file will store all sorts of things. Suggestions?'''

-----

'''Config Files'''

While the ini files are per-user, the config files are per-application. When Open-Transactions starts up, the server and client will each try to read from their respective config files.

The config file is located relative to the data_folder location. When OT starts up, the initial data_folder path is read either A. from your ini file, or B. passed in on the command line, or C. set by a call to OT_API_Init(const char * szPath).

Continuing the above example, this "main path" aka "data_folder path" would be: <code>/Users/au/Projects/Open-Transactions/testwallet/data_folder</code>

From there, an OT client will assume that its configuration file is named "ot_client.cfg", and that it can be found in that folder, but ONE LEVEL UP. That is, <code>/Users/au/Projects/Open-Transactions/testwallet/data_folder/../ot_client.cfg</code> (Meaning, it's actually looking here: <code>/Users/au/Projects/Open-Transactions/testwallet/ot_client.cfg</code>)

For the OT server, the config file would similarly be located at: <code>/Users/au/Projects/Open-Transactions/transaction/data_folder/../ot_server.cfg</code> aka: <code>/Users/au/Projects/Open-Transactions/transaction/ot_server.cfg</code>

(The location is one level up, SO THAT you can swap out your data_folder indiscriminately, yet without losing your config file each time.)

Here are the contents of my ot_client.cfg file (located at <code>Open-Transactions/testwallet/ot_client.cfg</code>):

<pre>
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Open-Transactions client-side config file.

[logging]
logfile_path=/Users/au/Projects/Open-Transactions/testwallet/ot.log
log_level=3
</pre>
'''LOGFILE'''

If the above <code>logfile_path</code> is set (as above), then the OT API will log to that file. Otherwise all of the logs are outputted to stderr.

(OT no longer logs to stdout, in preparation for upcoming command-line utilities. )

The <code>log_level</code> ranges from -1 (no output) to 5 (very verbose / debugging). Use 5 to see many logs. 2 or 3 should be plenty high enough for most people, with 0 and 1 preferred.

'''What kinds of values would YOU like to see in the config file? Let me know!'''

Config files - Revision history

Cryptoman: Created page with "'''.ini file:''' When either the OT Server (transaction.exe), or the OT command-line test client (testwallet.exe) starts up, it tries to read from the ini file. The '''locati..."