Bulk snooze: Snooze... and Wake on the ticked alerts, with undo that puts back each alert's earlier snooze exactly. Alert rules are judged for a server right after its agent reports, instead of at the next 15-minute pass; only that server's rule findings change, and the check is serialized with the pass so neither overwrites the other's state. Photos on server and device notes: up to 12 each, shrunk in the browser, accepted by their own bytes (JPEG/PNG/GIF/WebP, 4 MB), kept in the database and removed with the server or device. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
16 lines
653 B
SQL
16 lines
653 B
SQL
CREATE TABLE `note_photos` (
|
|
`id` integer PRIMARY KEY AUTOINCREMENT NOT NULL,
|
|
`server_id` integer,
|
|
`device_id` integer,
|
|
`content_type` text NOT NULL,
|
|
`data` blob NOT NULL,
|
|
`size` integer NOT NULL,
|
|
`caption` text,
|
|
`created_by` text,
|
|
`created_at` text NOT NULL,
|
|
FOREIGN KEY (`server_id`) REFERENCES `servers`(`id`) ON UPDATE no action ON DELETE cascade,
|
|
FOREIGN KEY (`device_id`) REFERENCES `network_devices`(`id`) ON UPDATE no action ON DELETE cascade
|
|
);
|
|
--> statement-breakpoint
|
|
CREATE INDEX `note_photos_server_idx` ON `note_photos` (`server_id`);--> statement-breakpoint
|
|
CREATE INDEX `note_photos_device_idx` ON `note_photos` (`device_id`); |