Enterprise deployment

FLEET Mira Enterprise is functionally based on Pro and uses PostgreSQL instead of a local SQLite file. The application supports Windows 10/11, Windows Server 20xx, and RDP, Citrix, or comparable terminal-server environments. Basic and Pro remain separate and continue to require a local Windows 10/11 console session and local SQLite database.

The complete client/server and all-in-one terminal-server procedures are in the administrator installation guide. Remaining work is prioritised under Enterprise open items.

Installation packages

The Enterprise build creates two separate packages:

• FLEET-Mira-Enterprise-<Version>-Setup-x64.exe installs the application and Enterprise installation marker;
• FLEET-Mira-PostgreSQL-Server-<Version>-Setup-x64.exe embeds the official PostgreSQL Windows installer and provisions a local service, the empty mira database, and the mira_app login.

Run the PostgreSQL Server setup as administrator on the intended Windows Server. The wizard asks for the port, PostgreSQL administrator password, and a password of at least twelve characters for mira_app. Secrets are passed to subprocesses only through temporary ACL-protected option files, never as process arguments, and are deleted after installation.

For a reproducible build:

.\scripts\build_enterprise_release.ps1 `
  -PostgreSQLInstaller C:\Install\postgresql-windows-x64.exe

The input must be a verified official PostgreSQL x64 installer. The resulting server package is standalone.

First application start

Enterprise opens the PostgreSQL connection wizard on first start. Enter:

1. server name or IP address;
2. port, normally 5432;
3. database mira;
4. user mira_app;
5. password and the required SSL mode.

Test connection verifies the server version, database, and user. If the database is empty, the wizard creates the current Mira schema transactionally. A non-empty foreign database is rejected. After successful validation, Enterprise stores the settings below %PROGRAMDATA%\eh-systemhaus\FLEET Mira Enterprise; Windows DPAPI protects the password.

For a remote database server, configure the firewall, listen_addresses, pg_hba.conf, DNS, and TLS according to customer policy. verify-full with a trusted server certificate chain is recommended for production networks.

Migrating SQLite to PostgreSQL

Open Enterprise → Migrate SQLite database. The wizard:

1. opens the source read-only;
2. runs PRAGMA quick_check and counts tables and rows;
3. requires explicit confirmation before replacing the PostgreSQL Mira schema;
4. rebuilds tables, keys, and indexes and copies data in one PostgreSQL transaction;
5. records the source path, SHA-256 digest, time, and object counts.

PostgreSQL is rolled back on failure and the SQLite source remains unchanged. Restart the application after a successful migration.

Operations and backup

The Basic/Pro SQLite snapshot and login restore functions are disabled in Enterprise. Back up PostgreSQL with operational PostgreSQL tools such as pg_dump and pg_restore and a monitored server-side backup policy. Application archives and external document stores must be protected separately according to their retention policies.