bobbanandClaude Sonnet 5
236b1da0dc
Summarizes every server's agent-reported listening ports in one cross-server table (grouped by protocol+port, addresses merged, loopback-only flagged) - previously this only existed per-server on each server's own detail page. Adds a second table for ports this app has no way to see on its own: manually-recorded openings on a router, edge firewall, or cloud security group, each with a label, external port/protocol, an optional link to a tracked server (with its own internal port when NAT changes it) or a freeform destination, a free-text source, and a comment. Viewer-readable; adding/editing/deleting needs operator or admin. The agent-port grouping logic (dedupe by protocol+port, detect loopback-only sockets) was shared with the existing per-server Ports card via a new agentPorts.ts service instead of duplicating it. Verified with a real HTTP-level test: a genuine Express app with the actual routers, a scratch SQLite DB, and forged admin/viewer sessions, covering grouping correctness, the server-name join, input validation, and role enforcement - the real dev DB was confirmed untouched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
15 lines
493 B
SQL
15 lines
493 B
SQL
CREATE TABLE `port_forwards` (
|
|
`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
|
|
`label` text NOT NULL,
|
|
`external_port` integer NOT NULL,
|
|
`protocol` text DEFAULT 'tcp' NOT NULL,
|
|
`server_id` integer,
|
|
`destination` text,
|
|
`internal_port` integer,
|
|
`source` text,
|
|
`comment` text,
|
|
`created_at` text DEFAULT (current_timestamp) NOT NULL,
|
|
`updated_at` text DEFAULT (current_timestamp) NOT NULL,
|
|
FOREIGN KEY (`server_id`) REFERENCES `servers`(`id`) ON UPDATE no action ON DELETE set null
|
|
);
|