Installing Ignition 8.1.22 on Linux via Homebrew

Ignition
1

Hello, community.

Previously I've shared news about Ignition via Homebrew for macOS, and today I'd like to announce Ignition for Linux via Homebrew.

Why Homebrew?

Because this all started when I was running macOS on my now ten-year old MacBook Air, and since I switched to Ubuntu 22.10 I had a way to tweak and test Ignition via my Homebrew Tap (coatl-dev/coatl-dev).

To learn more about Homebrew for Linux, visit the official site.

How do I install Ignition on Linux via Homebrew?

As easy as

  1. Install Homebrew

    /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

  2. Tap coatl-dev

    brew tap coatl-dev/coatl-dev

  3. Install ignition

    $ brew install ignition
==> Fetching coatl-dev/coatl-dev/ignition
==> Downloading https://files.inductiveautomation.com/release/ia/8.1.22/20221101-1006/Ignition-linux-x86-64-8.1.22.zip
######################################################################## 100.0%
==> Installing ignition from coatl-dev/coatl-dev
==> /home/linuxbrew/.linuxbrew/Cellar/ignition/8.1.22/bin/ignition checkruntimes
==> /home/linuxbrew/.linuxbrew/Cellar/ignition/8.1.22/bin/ignition runupgrader
==> Caveats
The data and logs folders have been symlinked to:
  data: /home/linuxbrew/.linuxbrew/etc/ignition
  logs: /home/linuxbrew/.linuxbrew/var/ignition
==> Summary
🍺  /home/linuxbrew/.linuxbrew/Cellar/ignition/8.1.22: 1,414 files, 1.5GB, built in 36 seconds
==> Running `brew cleanup ignition`...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see `man brew`).

  4. Start ignition

    $ ignition start
Starting Ignition-Gateway...
Waiting for Ignition-Gateway......
running: PID:157428

  5. Open your browser and go to http://localhost:8088 and provision your Gateway

Updating ignition on Linux via Homebrew

Usually when Inductive Automation releases a new version for Ignition I make the changes to the Formula and have it ready the same day or within a day, but if I'm not quick enough feel free to create a Pull Request.

But this is what I recommend:

  1. Run brew update && brew outdated
  2. If there's an update for ignition, run ignition stop
  3. Then brew upgrade ignition
  4. Finally, ignition start

You can also pin your ignition by running brew pin ignition, and unpin it whenever you're ready to upgrade.

$ brew pin ignition
$ brew list --pinned
ignition

Final comments

Thanks for reading.

3 Likes