Deploy Ignition
This article refers to Platform v3.4.0. The current Platform version is v3.4.0.
Overview
Ignition and Ignition Edge gateways deployed across remote industrial locations such as substations, field stations, and production plants often require on-site installation and configuration, making deployments costly and time-consuming.
Barbara eliminates the need for on-site visits. From the Barbara Panel, you can deploy Ignition to any registered edge node, regardless of its physical location. Configuration can be fully automated using the Bootstrap mechanism: on first startup, the container downloads a pre-built gateway backup (.gwbk) from a specified URL and restores it automatically.
In this tutorial, you will create a gateway backup, publish it through OneDrive, deploy Ignition to a remote edge node directly from the Barbara Panel, and then keep that gateway configured from the application settings instead of the Designer. In less than 15 minutes, you'll have a fully configured Ignition or Ignition Edge gateway running at the edge.
Prepare the configuration package
A .gwbk file is a configuration package that captures the state of an Ignition gateway. The Bootstrap mechanism downloads one on first start and restores it, so the gateway comes up with projects, tags and connections already in place.
Restoring a backup is not required to deploy Ignition. Leave BOOTSTRAP off and the gateway starts clean, ready to be configured from Application Config as described later in this article. This tutorial restores the Inductive Automation demo backup so you have something to look at straight away, and because it shows the mechanism you would use to roll out your own configuration across a fleet.
1) Download the demo .gwbk
Download the demo gateway backup from the Ignition Exchange (a free Inductive Automation account is required).
Ignition 8 Demo Projects on the Ignition Exchange
Ignition 8 Demo Projects on the Ignition Exchange
After signing in, click Download and save the ZIP package.
Extract the file Ignition Demo VM_Ignition-backup.gwbk (approximately 149 MB) from the downloaded ZIP archive.
The .gwbk major version must match the Ignition version being deployed.
The demo package from Ignition Exchange targets Ignition 8.1, so you must deploy the Ignition 8.1 application from the Barbara Marketplace. If the versions do not match, the restore operation will fail.
Inductive Automation also provides this backup on their Extra Materials page.
2) Host the .gwbk on a reachable URL
The Bootstrap mechanism downloads the gateway backup from the URL you set as SOURCE_URL. The application supports OneDrive and SharePoint, HTTP/HTTPS direct links, Google Drive, and SMB/CIFS network shares. This tutorial uses OneDrive.
- Upload
Ignition Demo VM_Ignition-backup.gwbkto OneDrive or to a SharePoint document library. - Open Share on the file and create a link that anyone in your organization can open.
- Copy that link and use it as
SOURCE_URL, exactly as OneDrive gives it to you.
The link is one of these two forms, and both work as they are:
https://1drv.ms/u/s!<SHARE_ID>
https://<tenant>-my.sharepoint.com/:u:/g/personal/<user>/<SHARE_ID>
There is no URL to rewrite: Barbara follows the share link to the file itself.
For a file on SharePoint or OneDrive for Business that is not shared openly, set ONEDRIVE_ACCESS_TOKEN to an OAuth2 access token and Barbara fetches it through the Microsoft Graph API.
Google Drive also works, but its share link is a view URL, not a download URL. Take the file ID from between /d/ and /view and build https://drive.usercontent.google.com/download?id=<FILE_ID>&export=download&confirm=t. The confirm=t matters: without it Google's antivirus page intercepts large files and the download arrives a few kilobytes long.
For SMB/CIFS network shares, set SMB_USER, SMB_PASS and SMB_DOMAIN. The username is required.
Add Ignition to your Library
If the edition you want is not yet in your Library, add it from the Barbara Marketplace:

Ignition
Ignition is a full-featured SCADA platform for unlimited industrial deployments, acting as the central hub for plant-wide data, visualization, and IT/OT integration.

Ignition Edge
A lightweight edition of the Ignition platform for edge nodes, field devices, and remote sites, bringing local SCADA, IIoT, and data acquisition to the source of the data.
For the complete process, see Add a Marketplace app to your Library.
Deploy Ignition
Open the Node Details page for the target edge node in the Barbara Panel. The node must be registered and ACTIVATED before applications can be deployed to it. If your Nodes List is empty, follow one of the install paths first.

Node Details for the remote node
Click Deploy to open the installation wizard.
1) Command settings
Select the application you want to deploy (Ignition or Ignition Edge) and the version, then click Next. The remaining steps are identical for both editions.

Selecting the Ignition application
2) App secrets
In this step, you'll configure the gateway and define how the initial backup is restored during deployment.
The step has one tab per service: ignition_standard (or ignition_edge), ignition_init, and ignition_config.
On the gateway tab, set ACCEPT_IGNITION_EULA to Y; the gateway will not start without it. Leave IGNITION_ACTIVATION_TOKEN empty to run in 2-hour trial mode, which is enough for this tutorial. The demo project is large, so set GATEWAY_MAX_MEMORY to 2048. Keep the defaults for everything else.
On the ignition_init tab, enable the restore that defines this deployment: set BOOTSTRAP to True and SOURCE_URL to the OneDrive share link of your .gwbk. On first start, the gateway downloads that file and applies it automatically, so it comes up with your projects, tags, and connections already in place.
The same tab carries two optional settings worth knowing about. MQTT_TRANSMISSION adds the MQTT Transmission module so the gateway can publish tags over Sparkplug. IGNITION_SECRETS holds the passwords the gateway needs, kept out of its configuration, as described under Secrets.

BOOTSTRAP and SOURCE_URL configured
BOOTSTRAP applies the backup only on the first deployment when no gateway data exists. Subsequent restarts do not re-apply it.
To push an updated backup to an existing gateway, use OVERRIDE_BACKUP=true instead. It applies the .gwbk on every deploy, but only when the remote file has changed.
Every configuration variable and its default value is documented in the application's technical notes on the Barbara Marketplace.
3) Compose config
The Compose config step defines the persistent volumes and the host ports Ignition exposes. For this tutorial, you can keep all the default values.
There are two volumes: one for the gateway data and one, VOLUME_IGNITION_CONFIG_STATE, that records which settings Barbara already applied to the gateway. Among the ports, IGNITION_GAN_SSL_PORT (8060) is the Gateway Network port, needed to pair two gateways for redundancy or to connect this one to another gateway.

Default port mapping
Only the ports of the protocols you actively use need to be reachable from the network. If your deployment does not use BACnet or DNP3, those ports can stay unchanged without impact.
Leave a port empty and it is not opened on the device at all. The gateway still listens on it internally, and other applications on the same device can still reach it, so emptying the ports you do not use is the safer default.
4) App config
The editor opens already filled with the Ignition template: the sections you can declare, each one empty. This is where you configure the gateway without opening the Designer, and you can come back to it at any time after the deployment.
Leave the template as it is for now and click Send App. Barbara deploys the application to the remote node, and the Application Config section below covers what to put in each part once the gateway is running.

The App config step
Wait for the gateway to start
The node now performs the deployment autonomously. Ignition starts, downloads the .gwbk from the configured URL, and restores the gateway configuration. The process typically takes 3–5 minutes.
You can monitor the deployment from the workload card in the Barbara Panel. When the workload card turns green (Started), the gateway is ready.

Workload started
Open the Gateway UI using the Ignition Gateway UI link in the workload card URLs panel, or navigate directly to http://<NODE_IP>:8088.

The workload URLs panel
If you try to open the UI while the restore is still in progress, you'll see the standard Ignition startup page.

The Ignition startup splash
Open a demo project
The gateway is now online and running with the configuration restored from your backup. As noted earlier, the Ignition Gateway UI link in the workload card provides direct access to the UI without requiring knowledge of the node's network address or workload port.
Direct access to the Gateway UI requires your computer to have network connectivity to the edge node. If the node is located on a different network, connect through Barbara's VPN first.
See Configure the VPN for setup instructions.
Log in with admin / password, the default credentials of the Ignition demo backup.

Ignition Gateway login
In the Gateway UI, locate Perspective in the left sidebar and click Launch. A list of the sessions restored from your .gwbk appears. Select Oil and Gas (or any other project) and click Launch to open its HMI in the browser.

Perspective Session Launcher

Oil and Gas demo HMI
The demo backup includes database connections that reference MySQL instances not deployed as part of this tutorial. As a result, some connections appear as Faulted in the Gateway UI. This does not affect the Perspective demo projects.
To clear the warnings, deploy MySQL and phpMyAdmin from the Barbara Marketplace and import the corresponding demo datasets.
Configure the gateway from Application Config
The gateway is running with everything your backup carried. Anything you add from here, such as a new device connection or a link to a central gateway, would normally be entered by hand in the Designer on that gateway, and would be lost the next time you rebuild the node from a backup.
Application Config removes that step. You declare what the gateway should have in a JSON document in the Barbara Panel, and the configuration service that ships with the application keeps the gateway matching it, on this node and on every other node you deploy the same document to.
Open the workload in the Barbara Panel and edit App Config. The mechanism itself is the same one every Barbara workload uses, described in Application configuration types.
Example
{
"ignition": {
"system": {
"debugLevel": "info",
"applyMode": "enforce",
"reconcileIntervalSeconds": 300
},
"gateways": ["http://gateway:8088"],
"opcuaDevices": [
{
"name": "PLC_Line1",
"driver": "ModbusTcp",
"hostname": "10.20.0.5",
"port": 502
}
],
"opcConnections": [
{
"name": "central-opcua",
"endpointUrl": "opc.tcp://10.20.0.50:62541",
"securityPolicy": "Basic256Sha256",
"securityMode": "SignAndEncrypt",
"authenticationType": "USERNAME",
"username": "barbara",
"password": "secret.centralOpcuaPassword"
}
],
"gatewayNetworkOutgoing": [
{
"name": "central-hub",
"host": "hub.plant.example.com",
"port": 8060,
"useSSL": true
}
]
}
}
gatewaysis the gateway this configuration applies to. Keep the default entry unless you renamed the service.opcuaDevicesare the field devices the gateway polls.driveris the Ignition driver name, for exampleModbusTcp.opcConnectionsare OPC UA servers the gateway reads from. Apasswordhere is never a literal: it names a secret, as described below.gatewayNetworkOutgoingdeclares a link to another Ignition gateway. WithuseSSLset totrue, Barbara establishes the certificate trust at both ends while the application starts, so you do not approve anything by hand.
What you can declare
| Section | What it configures |
|---|---|
system | How Barbara applies the rest: log level, apply mode, and how often it checks. |
gateways | The gateway this configuration applies to. |
opcuaDevices | Device connections, one per field device. |
opcConnections | Connections to other OPC UA servers. |
opcuaServer | The gateway's own OPC UA server. |
tagProviders | Tag providers, including one that mirrors the tags of another gateway over the Gateway Network. |
gatewayNetwork | The Gateway Network security settings of this gateway. |
gatewayNetworkOutgoing | Links this gateway opens to other gateways. |
gatewayNetworkIncoming | Connections from other gateways that this one accepts. |
mqttServers, mqttServerSets, mqttTransmitters | Sparkplug publishing, when MQTT Transmission is switched on. |
On Ignition there are three more: databaseConnections, historianProviders and storeAndForwardEngines. Ignition Edge has no database support, so it does not accept them.
Every section, every field and its default value is documented in the application's technical notes on the Barbara Marketplace.
Secrets
A password never goes into Application Config as a literal. Instead you give the passwords once, at install time, in the IGNITION_SECRETS setting of the ignition_init tab, as the base64 of a JSON object of name to value:
{"centralOpcuaPassword": "the-real-password"}
Then refer to each one from Application Config as secret.<name>, exactly as central-opcua does in the example above. The value is stored in the gateway's own secret store, and the gateway configuration only ever holds the reference.
How your changes are applied
Barbara checks the gateway against your document every few minutes, and again as soon as you edit it, so a change typically lands within a minute or two.
With applyMode set to enforce, Barbara corrects anything that drifts away from what you declared, including changes made by hand in the Designer. Set it to plan to see what Barbara would change, written to the application log, without touching the gateway.
Barbara only manages what you declare. Resources you created yourself and never named in the document are left alone.
Set up a redundant pair
A single gateway is a single point of failure. The same application can also run as a redundant pair: two nodes, one serving and one standing by, where the standby takes over automatically if the first stops responding.
There is no separate application for this. You deploy this one twice, once on each node, and choose the role in the installation form:
| On the main node | On the standby node |
|---|---|
Redundancy role: Master | Redundancy role: Backup |
| Redundancy pair secret: a phrase of your own, at least 24 characters | Redundancy pair secret: exactly the same phrase |
| Address of the other node: the standby's address | Address of the other node: the main node's address |
| Gateway name of the backup node: the name you will give the standby | — |
The two gateways find each other over the Gateway Network, on the port you set as Gateway Network port (8060 by default), exchange certificates and pair themselves. It takes about half a minute, and the application log tells you when the pair is protected.
Both nodes can keep the same Application Config document, so the pair is configured once and stays consistent through a failover.
Installation order, what to do when the encrypted link between the two nodes does not come up on first install, and when it is reasonable to run that link unencrypted on a closed plant network, are all covered in the application's technical notes on the Barbara Marketplace.
This section describes a pair of two independently deployed nodes. To run a high-availability pair inside a single Barbara cluster, with one address in front of both gateways, use Deploy Ignition for Cluster instead.
Summary
You have successfully deployed an Ignition gateway to a remote edge node without requiring physical access to the device. Barbara delivered the application, restored the gateway backup, and brought the system online with its projects and configuration already in place.
Because the configuration is packaged in a .gwbk file, the same workflow scales from a single site to hundreds of nodes. Prepare the backup once, then deploy it consistently across your fleet from the Barbara Panel.
When you need to roll out an updated configuration, set OVERRIDE_BACKUP=true and provide the new backup URL. Barbara automatically detects changes and applies each backup only once, making repeated deployments safe and predictable.
For everything that changes more often than a backup does, use Application Config: declare the device connections, OPC UA connections and Gateway Network links once and Barbara keeps every gateway matching them, with no Designer session and no new .gwbk.
To add high availability, continue with Deploy Ignition for Cluster.