Replication

Significant Change in Iguana 6.3: Automatic Push to Remote Git Repository

One of the most important new features being worked on in Iguana 6.3 is the ability to automatically push the internal GIT repository—which manages all your interface code and configuration inside Iguana—to a remote Git repository. This can be any standard Git platform, such as GitHub, GitLab, Bitbucket, or even a self-hosted Git server.

This capability represents a significant advancement for several reasons. First, it greatly enhances visibility and collaboration. Previously, all versioning was managed internally within the Iguana server. Now, with the automatic push feature, your code and configuration changes become visible in any standard Git platform. This increased transparency makes it far easier for teams to review changes, audit history.

Second, disaster recovery and backups are now much simpler and more robust. By replicating your configuration to a remote Git repository, the plan is to make it easy and reliable to restore your Iguana environment on a backup server or a new instance. This process reduces the number of manual steps involved, minimizes the risk of errors, and helps ensure minimal downtime in disaster recovery scenarios.

For example, consider an environment where you operate both a production Iguana server and a standby backup server. With automatic push enabled, all configuration changes and scripts are continuously synchronized with your remote Git repository. If you ever need to bring the backup server online, you can simply pull the latest updates from the remote repository—eliminating the hassle of searching for exports, transferring files manually, or risking missed updates.

In summary, this change brings your Iguana implementation in line with best practices from the wider software development ecosystem. By increasing visibility, improving manageability, and boosting resilience, the automatic push to a remote Git repository is a major step forward for configuration management and operational robustness