Settings
Four tabs of server-wide configuration — the machine's name and clock, who may sign in over SSH, how memory is allocated, and how updates and restarts happen.
Settings is where the server itself is configured, as opposed to anything hosted on it. Four sections, one screen:
Server
The machine's name, its timezone, and keeping its clock correct.
Access & security
The SSH port, whether root may sign in, and passwords versus keys.
Memory
Swap, and how much memory Redis is allowed.
Updates & restart
Security patches, scheduled restarts, and restarting now.
Settings has no landing page of its own — opening it takes you to Server.
How saving works
Every section is a form with its own save button, and nothing is applied until you press it. While a section has unsaved edits the panel shows You have unsaved changes with a Discard button next to save, and leaving the page asks you to confirm first.
Sections do not share a save. Editing the server name and then switching to Memory discards the name.
Changes that could lock you out or interrupt service ask for confirmation a second time, in a dialog that spells out the consequence — moving the SSH port, turning off swap that is in use, restarting the server.
The tab badges
Two of the tabs can carry a badge:
- Access & security — Needs attention when root is allowed to sign in with a password. That is the account automated attacks try first, so it is surfaced from wherever you are in Settings.
- Updates & restart — Restart needed when an installed patch requires a restart to take effect.
Permissions
The whole screen is one permission, setting. With view you see every
section and every value but no controls, and the panel says so: "You can see
these settings but not change them." Changing anything needs Setting ·
Manage.