Skip to content

Deploy A New Instance

Open from Servers -> host row -> Add QLDS Instance to <host>.

Prerequisite: Add A Host

Host limit: each host can have a maximum of 4 instances. If a host already has 4, deploy the new instance to a different host or remove an existing one first.

Default Preset Behavior

When the add new QLDS instance form opens, config is preloaded from the default preset.

  • Default preset is a built-in baseline template — it cannot be modified or deleted.
  • Modify the preloaded values freely before deploying; those changes only affect this instance.
  • To save a customized starting point, use Save As New to create your own preset.

Preset details: Presets And Default Config

Basic Info Block

Required fields:

  • Instance Name
  • Host Server
  • Port
  • Server Hostname (this is auto-synced with sv_hostname value)

Optional toggle:

99k LAN Rate controls LAN-rate profile for the instance. Changing this later from the actions menu triggers reconfigure/restart. Reference: Instance Actions Menu

Main Tabs In Deploy Form

Config editing details live here: Edit Configs, Plugins, And Factories

The deploy form uses the same file manager as Edit Config. Before creating the instance you can add custom .cfg or .txt config files, create subfolders with .ent entity override files, stage plugin file changes, choose checked plugins, and select the .factories files that should be deployed.

Create Instance

  1. Review fields and tabs.
  2. Click Create Instance.
  3. Wait until status leaves transitional states and reaches running/healthy state.

What Happens To Config After Deploy

QLSM deploys QLDS instance and pushes the full selected file snapshot to that instance: configs, checked plugins, plugin files, checked factories, and factory file contents.

  • Later edits affect only that instance.
  • Other instances are unchanged.
  • Default preset files remain unchanged.

Next pages: