Port presets: Windows client, Windows server and Debian / Ubuntu

Ready-made presets for what each OS has open out of the box. They are added once
to installs that already have presets (same-name presets untouched, emptied list
stays empty); a test checks no port is given two names across presets.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-11-16 23:39:29 +01:00
1 parent 06ac120a1d
commit 94288afcbd
4 files changed
+100 -10

No files matched your search

+1 -1
View File
@@ -413,7 +413,7 @@ records them; it can't check or change them.
#### `port_presets`
A named list of ports ("Remote access": SSH, RDP, VNC). A port in any preset is named wherever it is shown, can be scanned for on many servers at once, and can have its name written onto the servers where it is open (`server_ports.label`). The ready-made ones are written once, into an empty table (flag `_internal:portPresetsSeeded` in `settings`), and are ordinary rows after that.
A named list of ports ("Remote access": SSH, RDP, VNC). A port in any preset is named wherever it is shown, can be scanned for on many servers at once, and can have its name written onto the servers where it is open (`server_ports.label`). The ready-made ones are written once, into an empty table (flag `_internal:portPresetsSeeded` in `settings`), and are ordinary rows after that. The operating-system ones (*Windows client*, *Windows server*, *Debian / Ubuntu*) came later, with their own flag (`_internal:portPresetsOsSeeded`): once, into a table already in use they are added unless a preset of that name exists, and an emptied table stays empty.
| Column | Type | Notes |
|---|---|---|