Overview & Installation
What is the Floating Server V2?
The Floating Server is LicenseSpring’s self-hosted licensing platform, providing the core features of the cloud platform locally. Version 2 introduces improved setup, configuration, and management workflows to make deployment, provisioning, and administration easier. This document focuses on v2, detailing installation, configuration, and best practices for running the Floating Server in your environment.
Key Highlights & Compatibility
Supported Platforms
Windows and Linux
Supported SDKs (initial)
C++, .NET, Java, Python, Go, node.js
Database Support
SQLite (dev/test), PostgreSQL (prod)-Production RecommendationPostgreSQL
Provisioning Options
Certificates or YubiKey tokens
Installation Options
Run Floating Server v2 with PostgreSQL and Docker
Create a shared network:
docker network create fsnetStart PostgreSQL:
docker run -d \
--name fs-postgres \
--network fsnet \
-e POSTGRES_USER=fsuser \
-e POSTGRES_PASSWORD=fspassword \
-e POSTGRES_DB=fsdb \
-v pgdata:/var/lib/postgresql/data \
-p 5432:5432 \
postgres:16change the setting as needed.
Modify Floating Server config file:
Pull the Floating Server v2 image:
Docker image variants
Floating Server v2.5.0 is available in two variants:
Standard Debian image:
v2.5.0orlatestDistroless non-root image:
v2.5.0-distrolessorlatest-distrolessThe Distroless image contains fewer runtime components and is recommended for new deployments. The standard Debian image remains available as a compatibility and rollback option during the initial rollout.
To use the Distroless image:
Run Floating Server v2
Mount the config file and the certs (certificates and private key generated in provisioning) folder from provisioning:
In this sample, we have assumed the config file is located in ./config and certificates and private key in ./certs.
Verify
Floating Server API:
http://localhost:8080Postgres: available at
fs-postgres:5432inside the Docker network
Docker Compose
The steps mentioned above are all included in the following docker compose file. Place this file in the directory with folders config and certs (config containing default.yaml and certs containing all the certificates and private key generated in provisioning), and then run:
Make any needed adjustments.
Last updated
Was this helpful?