Server settings
Identity, provider metadata, firewall, build concurrency, and backup retention for a server.
Server Settings has four tabs: General, Firewalls, Build Server, and Backups.
General
Section titled “General”Identity
Section titled “Identity”Name and environment (Production, Staging, etc.) help people identify the server in the dashboard. Changing either does not rename or reconfigure the machine at its cloud provider.
Provider
Section titled “Provider”Shows the provider (or Custom for an unmanaged machine), the provider-side server ID, and the region or datacenter. For a custom server these fields are informational only; Serversinc does not use them to reach the machine.
Network
Section titled “Network”IPv4 and IPv6 addresses are masked by default. Click Reveal to show them. These are reported addresses, not editable labels — change the machine’s network configuration at the provider, not here.
Danger zone
Section titled “Danger zone”Disconnecting doesn’t delete backups. To keep using the machine without Serversinc, remove the agent.
Firewalls
Section titled “Firewalls”The firewall is off by default. Turning it on blocks all incoming traffic except ports you explicitly open.
Click Add port to allow traffic on a specific port. With the firewall off, the open-ports list has no effect.
Build Server
Section titled “Build Server”Toggle Build server to run builds for applications on this server instead of their configured deploy server. Use this to keep build load off a server that also serves production traffic.
Max concurrent builds caps how many builds run on this server at once. Builds beyond the limit queue and wait for a slot to free up. The limit applies to the whole server, not per application.
Lower this on smaller servers to avoid builds competing for CPU and memory with running containers.
Backups
Section titled “Backups”Set retention by age (Retention period), count (Maximum backups to keep), or both. Leave a field blank for no limit. A backup is pruned only when it is past every limit you set. The 3 most recent completed backup runs and any locked backup are always kept.
See Schedules and retention for how pruning works.