Linux Support

Connexion v26 introduces a Linux deployment path for Connexion, Gateway, and Remote Agents. This page focuses on what Linux support means operationally: how Connexion is installed, configured, started, verified, and maintained on Linux.

Linux support is intended for service/runtime deployments, automation, containers, and server workloads. Windows desktop UI surfaces that depend on WPF remain Windows-only.

Supported deployment model

Server-side Connexion components run as Linux services.
Debian/Ubuntu package installation is the first Linux package-manager target.
The package lays down product files, while the Connexion configuration wizard owns database, service, certificate, and licensing setup.
Mutable runtime state lives outside the package payload, under Linux data/config/log locations.

Install Connexion on Linux

The expected first-release operator flow is a local Debian package install followed by the Connexion configuration wizard.

sudo apt install ./connexion_<version>_amd64.deb
sudo connexion --wizard

Package install example

Configuration wizard example

CLI wizard walkthrough

The package installation and product configuration steps are intentionally separate:

The package installs the published Connexion payload under /opt/connexion/<version>.
The package installs a /usr/bin/connexion launcher.
The package does not create or start the Connexion service by itself.
The package does not configure licensing, databases, certificates, or service accounts.
The explicit configuration step is sudo connexion --wizard.

Configuration wizard flow

The Linux configuration wizard should guide the operator through the same major setup decisions as other v26 install paths.

Launch the wizard with sudo connexion --wizard.
Select an existing SQL Server or PostgreSQL database, or choose the automatic PostgreSQL install path when supported.
Configure service identity, data paths, certificates, ports, and licensing.
Review the install plan before applying host changes.
Start the service and verify health, logs, and metrics.

Automatic PostgreSQL install

v26 replaces the old LocalDB bootstrap path with PostgreSQL-backed setup. On Linux, the automatic PostgreSQL path uses the host package manager where supported.

Debian/Ubuntu: apt-based install through the PostgreSQL package repository.
Fedora 43 and newer: dnf package-default install path.
Other rpm-family distributions may be added after the first Linux package path is stable.

Automatic PostgreSQL installation is an install-time action. After setup completes, Connexion is configured as a normal PostgreSQL-backed deployment.

Verify the installation

After the wizard applies the configuration, operators should verify the service, logs, and configured endpoints.

systemctl status connexion
sudo journalctl -u connexion -n 100 --no-pager
sudo connexion --status

Service running example

Windows UI connected to a Linux-hosted Connexion service

The exact service names and status commands may change as the Linux package and wizard are finalized. Keep this section aligned with the released package.

Recent service logs are most useful when troubleshooting startup failures. For normal verification, the service status capture is enough; use journalctl output when support needs the exact startup or error details.

Future repository and scripted installs

The first Linux package path is expected to start with a downloadable .deb package. Repository-based installation, such as adding a Connexion apt repository and running apt install connexion, is planned as a future expansion after local package install and upgrade behavior is validated.

The same packaging direction may also expand to scripted Windows installs. Future Windows options may include package-manager installation through tools such as winget and Chocolatey, alongside the existing Windows installer path.

Current limitations

Desktop UI configuration surfaces remain Windows-only.
Legacy x86 execution groups are not part of the v26 Linux runtime model.
Custom plugins that depend on Windows-only APIs must be migrated before they can run on Linux.
Repository-hosted apt installation and rpm-family package support coming soon.