Installation and Deployment
๐ฅ๏ธ Desktopโ
Install the native License Center build for Windows or Linux and launch it. On first launch, choose whether this desktop stores its own data or connects to an existing server. The selection can later be changed under Settings ยท Client preferences.
After installing an upgrade, close and reopen the desktop app. The version at the bottom of the sidebar reflects the installed desktop build. The desktop loads its bundled interface directly and retires older offline UI caches on startup; your saved data and connection settings are preserved.
Standalone desktop data location
Standalone desktop data is stored under
%APPDATA%\ImpleoTV\LicenseCenter on Windows,
$XDG_CONFIG_HOME/impleotv/license-center (normally
~/.config/impleotv/license-center) on Linux, and
~/Library/Application Support/ImpleoTV/LicenseCenter on macOS. The generated
local master key is protected with Windows DPAPI on Windows.
๐ง Server deploymentโ
License Center server builds run without a desktop window and expose the console and REST API over HTTP. Production deployments should place the server behind an HTTPS reverse proxy and set its public URL to the externally visible HTTPS URL.
The server requires either LICENSE_CENTER_MASTER_KEY or
LICENSE_CENTER_MASTER_KEY_FILE. The key must decode to 32 bytes and must be
backed up together with the database.
Important server settings include:
| Variable | Purpose |
|---|---|
LICENSE_CENTER_DATA_DIR | Database, node ID, and local application data |
LICENSE_CENTER_HOST / LICENSE_CENTER_PORT | HTTP bind address and port |
LICENSE_CENTER_PUBLIC_URL | Public URL used for external links and webhooks |
LICENSE_CENTER_MASTER_KEY | Base64-encoded 32-byte encryption key |
LICENSE_CENTER_SECURE_COOKIES | Requires HTTPS refresh cookies when enabled |
LICENSE_CENTER_ALLOWED_ORIGINS | Explicit origins for remote clients |
Do not expose a production server directly over unencrypted HTTP. Terminate TLS at the ingress or reverse proxy and enable secure cookies.
For a native desktop connecting to this server, include its Wails origin in
LICENSE_CENTER_ALLOWED_ORIGINS: wails://localhost for Linux and
http://wails.localhost for Windows. During make dev, also allow the Vite
origin (normally http://localhost:9245).
๐ณ Dockerโ
The supplied Docker deployment persists /data, runs as a non-root user, and
provides /healthz and /readyz endpoints. Set a strong master key in the
deployment environment before starting the container.
โ๏ธ Docker Compose configurationโ
Before starting the supplied Docker Compose deployment, copy .env.example to
.env beside docker-compose.yml and set the required values. Docker Compose
reads this file when it resolves the deployment settings.
| Argument | Required | Explanation |
|---|---|---|
LICENSE_CENTER_MASTER_KEY | Yes | Base64-encoded 32-byte key used to encrypt managed secrets. Generate it with openssl rand -base64 32, keep it secret, and back it up with the database. Changing or losing it makes existing encrypted signing keys unusable. |
LICENSE_CENTER_PUBLIC_URL | Yes | Externally visible HTTPS URL, for example https://licenses.example.com. It is used for links, callbacks, and webhook URLs. Do not use the container's internal address. |
LICENSE_CENTER_SECURE_COOKIES | No | Keep true for production HTTPS deployments so refresh cookies are sent only over secure connections. |
LICENSE_CENTER_BIND_ADDRESS | No | Host interface on which Docker publishes the service. The default, 127.0.0.1, restricts access to the host so a local reverse proxy can provide HTTPS. |
LICENSE_CENTER_PORT | No | Host port published for the service. The default is 8080; the container continues to listen on port 8080. |
LICENSE_CENTER_ALLOWED_ORIGINS | No | Comma-separated additional origins allowed to call the server. Add wails://localhost for Linux desktop clients or http://wails.localhost for Windows desktop clients. Leave empty for browser access from the public URL only. |
LICENSE_CENTER_SESSION_MAX_DURATION | No | Maximum total lifetime of a sign-in. The default is 30d; values accept h, m, or d. |
LICENSE_CENTER_SESSION_IDLE_TIMEOUT | No | Time without activity before a user must sign in again. The default is 7d; values accept h, m, or d. |
LICENSE_CENTER_COMPANY_ICON_PROVIDER_URL | No | Base URL for the company icon service. Keep the default or replace it with an approved self-hosted provider. |
LICENSE_CENTER_IMAGE | No | Docker image name and tag. If omitted, Compose uses impleotv/license-center:local. |
Restrict access to .env because it contains the master key. Then start the
deployment with docker compose up -d --build.
๐ฆ Debian and Ubuntu packageโ
For a remote Debian or Ubuntu server, install Docker Engine and Docker Compose
v2 first. Download the .deb matching the desired License Center release, copy
it to the server, and run:
sudo apt install ./license-center_1.2.3_all.deb
sudo license-centerctl configure
The configuration command asks for the externally visible HTTPS URL and the
local reverse-proxy port. Accepting the default publishes License Center only at
http://127.0.0.1:6000; configure the existing reverse proxy to use that
address as its upstream. Port 8080 remains internal to the container.
For unattended configuration, pass the values explicitly:
sudo license-centerctl configure \
--public-url https://licenses.example.com \
--proxy-port 6000 \
--non-interactive
Use license-centerctl status, logs --follow, restart, stop, and start
for operations. Configuration and the generated master key are stored under
/etc/license-center with root-only permissions. Back up that directory
together with the license-center-data Docker volume. Upgrades and package
removal preserve both; intentionally deleting the master key makes encrypted
data in an existing volume unusable.
๐ Browser and PWAโ
Open the public server URL in a current browser. The application shell can be installed as a PWA from Settings ยท Client preferences. Authenticated API responses and mutations are not stored in the application cache. Device notifications require HTTPS in production. Android can enable them from the notification bell in the browser or installed PWA. On iPhone and iPad, add the PWA to the Home Screen first, open it there, and then enable notifications from the bell. Administrators receive alerts for access requests, order activity, license issuance, and successful license email delivery.
Continue with First run after the application opens.