Requirements

This page lists what you need before you install. Read it, then go to the install procedure for your platform.

Supported hosts

BareBones Ticketing runs on one host. There are two install shapes.

Where this has been installed and checked

Two hosts have a full clean-install run against this build: Windows Server 2019, from a clean default installation, and Rocky Linux 9.7, from a clean minimal installation. If you have a free choice of host, choose one of those — they are the paths we have walked end to end.

Every other supported host has also been installed against this build: each from a fresh minimal OS installation, through to the product serving its first-time setup page. Ubuntu Server 24.04.4 additionally has a deeper run recorded against an earlier build — Compose install, database bootstrap, HTTPS setup, restart continuity, and backup and restore all covered.

Support covers the whole supported list, not only the two we have walked, where your edition carries a support entitlement. See Editions.

One pairing is worth knowing about: Windows Server 2019 with the product-managed local PostgreSQL 18. The PostgreSQL 18 Windows installer's published tested-platform list names Windows Server 2022 and 2025, so the 2019 pairing rests on our own clean-install acceptance run rather than on the database distribution's published matrix. It is the pairing whose evidence is ours alone.

Database

• PostgreSQL is the only database BareBones Ticketing supports.
• Windows local mode installs PostgreSQL server version 18.4-2 and its command-line tools. It does not install pgAdmin or StackBuilder.
• Linux bundled mode runs the postgres:18 image. Both platforms run PostgreSQL 18, so the bundled database is the same major version whichever platform you install on. External mode is the exception — match your backup and restore commands to the version that server actually runs.
• External mode connects to a PostgreSQL database that already exists. You create that database; the installer does not.

See PostgreSQL for what setup does to the database.

Network name and HTTPS

• One stable DNS name or approved host address.
• HTTPS for setup and for all administration afterwards. There is no supported plain-HTTP setup path.
• Inbound TCP port 8443. This is the package default on both platforms.
• Accurate host clock. Authentication, approvals, SLA records, and licence calls depend on it.

BareBones Ticketing does not create DNS records, obtain public certificates, configure Linux firewalls, or configure an external reverse proxy. The Windows installer creates one inbound firewall rule for TCP 8443 and nothing else. The rule has two names: its internal name is BareBonesTicketing-HTTPS, and its display name is BareBones Ticketing HTTPS. Windows Defender Firewall (wf.msc) and the default Get-NetFirewallRule output show the display name.

Storage and continuity

Four sets of data must survive a host failure. Back them up together — they are only consistent with each other.

Back up the whole key ring folder, not the key XML files inside it. The managed HTTPS certificate .pfx lives in a subfolder of that same folder. Copying only the key XML loses the certificate without reporting an error.

The Windows install directory holds an administrator-only local-database maintenance credential that cannot be recovered from anywhere else. Treat it as secret-bearing and back it up with the rest of the set. The Linux .env is secret-bearing in the same way.

Changing a configured attachment path or key-ring path does not move the existing files. You move them. The product does not create folders, set permissions, mount network shares, or migrate data.

Named owners

Before you install, name a person for each of these:

• PostgreSQL administration
• DNS, firewall, and reverse proxy
• Certificates
• Storage and backup/restore
• The first System Administrator account
• Accepting the Product License Agreement on behalf of the organization

Outside the 1.0 baseline

These are not supported. The list is factual, not a roadmap.

Internet Information Services (IIS) is not in this list, deliberately. The Windows package runs as a Windows Service under Kestrel and does not require or use IIS. That is different from IIS hosting being an unsupported topology, and the product documentation does not make the stronger claim — so neither does this page.

The package

You install from a customer package supplied by the vendor: the application files, a manifest, integrity evidence, the legal material, and the procedure for that exact version.

Get the package from your Finlay.works customer area. Downloads are listed there against an active licence, filtered to the editions that licence is eligible for. Check the version and SHA-256 against what you intended to install. Do not substitute a source checkout, an internal build, a review bundle, or a container image pulled from a registry.

Next step

Go to the install procedure for your platform:

• Windows Server
• Linux Docker Compose

Related pages

• PostgreSQL
• HTTPS and hostnames