ts server

View and set the settings that belong to one server in the deployment.

Usage

ts servers [--role=ROLE]
ts server <name>
ts server <name> <property>
ts server <name> <property> <value>

Description

A Turbo Server deployment can be several machines, each running a different set of roles — controller, hub, application, portal. ts servers lists them; --role narrows to one kind.

ts server <name> prints one machine and all of its settings. Naming a property gets that one value; naming a property and a value sets it.

These are per-machine settings, distinct from the global ones in ts settings. Where the two overlap in subject, the per-server value is the specific one — so a setting applied here affects that machine only, and the rest of the deployment keeps whatever the global setting says.

Every change is recorded in the audit log with the machine and property named.

Options

Flag	Description	Default/Values	Notes
--role	Show only servers with this role.	Controller, Hub, Application, Portal	ts servers only.

Examples

# Every machine
ts servers

# Just the application servers
ts servers --role=Application

# One machine and everything about it
ts server build01

# Read one setting
ts server build01 ssl-hsts

# Change it
ts server build01 ssl-hsts true

Exit Codes

0 on success. -4 when no account is signed in. -5 when the account is not a Server Administrator. -6 when no server has that name. -1 when the property is not a known setting, or the value is not valid for it — the message lists what is accepted.

Related Commands

• ts settings — Deployment-wide settings.
• ts status — Whether a server is actually answering.