Specifying custom settings in Config Files for Development
Why would one specify custom config file settings for development?
While developing on either the client side or the server side you might want to specify custom settings in the .config files for the client side and the server side.
For instance, you can change the DebugLevel, the IP Address/Port of your development PetraServerConsole instance, etc. You can find other examples here that speed up the development/debugging/testing turnaround.
Location of auto-generated configuration files - don't edit those
- The PetraClient application picks up its configuration file from the
\etc\Client.config file
. - The PetraServerConsole application picks up its configuration file from the
\etc\Server.config file
.
However, these files get overwritten when nant startPetraServer
or nant startPetraClient
are run!!!
To avoid loosing your changes to these files you need to make the changes to the appropriate .config file in the template of that file!
Location of template configuration files
The folder \inc\template\etc\
contains one file for the client configuration, Client.config
and several config files for the server configuration, named Server-mysql.config
, Server-postgresql.config
and Server-sqlite.config
. Determine the correct server .config file by choosing the one that relates to the RDBMS you are currently using for development.
Creating custom .config files
- Follow the instructions here to create your custom .config files that contain your changes.
- Then run
nant initConfigFiles
- Then run
nant startPetraServer
and/ornant startPetraClient
to start the appropriate application with the .config file changes applied.