Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Custom installation requires Iguana version 10.1.91 or above.

There may be instances where you need to customize your Iguana installation, for example:

  • You need to install multiple Iguana instances on a single server;

  • You want to embed Iguana within an install of your own application; or

  • You simply want to change the location of your log directory.

There are a few key ideas to understand and implement depending on your customization needs:

 Iguana runs as a single executable

Under windows and linux Iguana ships as a single executable. It has all its resources for HTML, Javascript etc. all built into one executable.

In fact for windows the ‘installer’ that you see is really just the Iguana executable running in a different mode. By renaming the file to be iguana_setup.exe and running it, it will run in its installer mode.

Updating Iguana is very straightforward because of this architecture.

See How is Iguana X packaged? The Key Components

 Using an iguana.ini file allows you to customize where the configuration data goes

See Create an iguana.ini file for custom installation for setting your Iguana instance directory (working directory) and service details.

 Using Configuration Files we can specify configurations like web port and log directory

Note: You’ll need to have started the service at least once before making any configuration changes to Iguana.

See Web Configuration File and Change the Log Directory.

 Use iguana --service install to register the service

This will work as a systemd service for Linux and as a windows service for windows.

At present IguanaX doesn’t have any licensing. So the above should be enough information to script out using IguanaX on platforms like Docker.

  • No labels