Summary

Iguana configurations (e.g. logs, iguana dashboard ports) are stored in IguanaConfigurations.xml located in Iguana Working Directory
Most of Iguana configurations can be updated via Iguana Dashboard except some specific configurations such as Log directory path, Iguana dashboard port
Moreover, IguanaConfiguretion.xml can used for Iguana auto installation and deployment

Where to Find Configurations

The IguanaConfiguration.xml is located in Iguana Working Directory → IguanaConfiguraitonRepo folder

This Setting can be changed within Iguana Dashboard. However ,If you are running two instances of iguana in the same machine this will result in a port conflict which will prevent Iguana from starting, because by default both iguana instance are set to use Port 6543.
To change the port manually open your IguanaConfiguration.xml in a text editor and look for a “web_config” tag ,
Under the “web_config” tag you can see a setting “port” . There you change from the default 6543 to any port based on your requirements.

By default Iguana will store logs inside the working directory under the logs folder .
If you would want Iguana to generate and store log file in a different directory you can use the steps below to change the configuration.
Simply, open your IguanaConfiguration.xml in a text editor and look for a “log_config” tag ,
Look for log_directory , and change the directory path.
However you will also need to change the index_directory path , which should be inside whichever directory your logs will be stored. For example if your log_directory path is “C:\Program Files\Iguana\Logs” then your log_index must be “C:\Program Files\Iguana\Logs\index”.

Always Commit After Making IguanaConfiguration.xml Change

Since the configuration xml in IguanaConfigurationRepo has been changed, it is a good practice to make any commitment in order for IguanaConfigurationRepo to push the changes into the IguanaMainRepo.
If you do not make any commit in Iguana after editing in the IguanaConfiguration.xml Iguana will not force the changes to the Main repo which means both IguanaConfigurationRepo and IguanaMainRepo will be out of sync, which can lead to Errors on Iguana startup, In order to fix the errors Iguana config will have to be rebuild using the IguanaMainRepo. Since the changes were not pushed into the main repo your Iguana will revert back to your previous settings and you will end up loosing all the changes that were made.