Skip to main content
FireFlo is delivered as a signed release tarball. You are sent a download link; everything needed to install the gateway is inside it, and the host needs no build tools and no source code.

​
Check it before you unpack it

1

Confirm the download is intact

Expect fireflo-<version>-linux-x86_64.tar.gz: OK. Anything else means the file did not arrive whole — download it again rather than unpacking it.
2

Confirm it came from us

Check the fingerprint, not just that it says “Good signature”. A signature is only worth the key it was checked against, so gpg --verify must name:
Any other fingerprint means stop and ask us before installing. Do this even when the checksum passed.
A checksum served from the same place as the tarball proves the transfer worked and nothing more. Anyone able to replace the file can replace the checksum beside it. Only the signature says who built it.If your release came without a .asc file, ask us for one before installing on anything that will carry customer traffic.
3

Unpack

​
What is inside

Read MANIFEST first. It names the version and the platform the binary was compiled for, and it is the fastest way to confirm you were sent what you expected.
No Java is required. The gateway carries its own runtime, and so do the operator commands — fireflo db migrate, fireflo license activate and the rest all run from the same executable. You do not need a JDK on this host to run FireFlo, only to build it from source, which you are not doing.
The binary is compiled for one architecture. A tarball named linux-x86_64 will not run on an arm64 host. The installer refuses a binary this machine cannot execute rather than installing it and failing at first start, but it is quicker to check the filename against uname -m first.

​
Install

The gateway and the control panel are separate installs and both are run from this directory.
1

Prepare the host, if it is a bare one

The installer does not install PostgreSQL, RabbitMQ or Node — it adds the PostgreSQL client and no server. On a host that has none of them, run setup.sh first and create a database.Skip this if those services already run, here or elsewhere.
2

Check the host

Changes nothing. Reports whether this host has what it needs — and on a release like this one it will tell you Java is not required.
3

Install the gateway

--from ./gateway names the executable in this tarball. Everything the installer asks and everything it refuses is on Install in one command.
4

Install the control panel

Only if your release included a panel/ directory. See Control panel.
5

Activate the licence

The key goes in the environment and never on the command line, so it does not land in your shell history or in ps. Full detail, including activation without internet access, is on Licensing.

​
Upgrading later

Later releases arrive the same way: verify, unpack, then point update at the new tarball.
update never touches your configuration directory, and keeps the previous version so a rollback is one command. See Upgrading.

​
Building from source instead

If you hold a source licence you can build the gateway yourself and install what you built — the installer takes either packaging. That path is By hand; this page is the one to follow if you were sent a tarball.

​
Something wrong with the release

If the signature does not verify, if MANIFEST names a version you did not expect, or if the download will not check out, stop and contact us rather than installing it: support@fireflo.au.