Packaging the Ignition code

Hi everyone,

We're currently working on a proof of concept (POC) where we aim to develop an application using Ignition, specifically focusing on custom modules, Perspective, and other features like Alarms and the SQL Bridge module.

The goal is to build an application that can be easily reused and deployed across different labs as separate entities. Essentially, we need a solution that works across multiple locations with unique configurations.

Since the UI is developed in Perspective, and there are custom modules for various workflows, we're exploring the possibility of packaging the entire application into a single executable file (either a .exe or .dmg).

While there are resources available on how to create Gateway backups (.gwbk), I haven't found much information on packaging the application as a single installable unit.

Dockerising is not an option as there are restrictions about using Dockers in our labs

Has anyone worked on similar requirements? Any insights on how to approach creating such packages would be greatly appreciated.

I would wait until 8.3 is previewed next week to see what options it gives you. I think the ability to change everything about the gateway config will be much better in that version.

As far as the current 8.1 version, there is no option to put everything in a package like you are describing. The big issue is there are still important configuration in a SQL Lite database in the install folder.

I don't really think anything in 8.3 will help with this ask.

Docker is really the closest approximation to this I can think of.

1 Like

One alternative you could use would be to follow other installers and while you could package the Ignition installer inside your installer, you could then call a silent install of Ignition followed up by your installer moving the necessary backup to a temporary directory, and then using gwcmd to restore it.

Another would be to use the zip file version to put Ignition where you want it, but you'd be on your own making sure it's installed properly, set as a service to auto-start, etc.

For creating my own installers in Windows, I use the free InnoSetup, and I've heard of others using NSIS as well. If you need cross-platform, I don't ahve any suggestions, but I know there's paid software to build installers for all the OSs.

1 Like