2 Commits

Include renames

Author	SHA1	Message	Date
bobbanandClaude Sonnet 5	fea20456e4	Add a Windows agent (PowerShell) ... Reports a Windows machine the way the Linux agent does, replacing the "planned" stub in agent/windows: scheduled tasks plus hostname, IPv4 addresses, CPU model/cores/current load, memory, every fixed disk, and TCP/UDP listening ports with the owning process (which feed the Ports card, localhost-only listeners included). Scripts (plain ASCII by design -- they are downloaded as text and Windows PowerShell 5.1 reads BOM-less files as ANSI): - report-tasks.ps1: collects and POSTs to /api/agent/report. Works in Windows PowerShell 5.1 and PowerShell 7. -DryRun prints the JSON. Microsoft's own \Microsoft\ tasks (hundreds) are left out unless INCLUDE_MICROSOFT_TASKS is set. Triggers are turned into readable text ("Weekly on Mon, Wed at 03:00", "At logon", "..., repeating every 15 min"). Self-signed certificates work via API_INSECURE on both PowerShell versions (they need different mechanisms). - install.ps1: elevated only; downloads the agent to ProgramData, writes agent.json with permissions locked to SYSTEM and Administrators *before* the token goes in, and registers a SYSTEM scheduled task (every 15 min plus at startup with a 2 min delay). Reinstalling replaces the task. - uninstall.ps1: removes the task and only the files the agent installed. Server: accepts schedule_type "windows_task"; a server can be registered as Windows (Add a server has an operating system choice); an agent's reported os_type ("linux"/"windows", anything else ignored) corrects the stored one. The Servers page shows the right install and uninstall command for each OS (Windows PowerShell 5.1 one-liners, with a self-signed variant and a note about PowerShell 7), and Windows tasks are labelled "Windows scheduled tasks". The Linux commands are unchanged. Verified on this Windows machine, in both PowerShell 5.1 and 7: - Real dry runs found and fixed bugs before anything shipped: tasks and ports came out as one nested item (return , $out wrapped twice), integer keys in an ordered dictionary index by position (wrong weekday names), and generic "Trigger" labels. - End to end against the real agent-report router: HTTP, self-signed HTTPS refused by default and accepted with API_INSECURE, wrong token gives a clear one-line error and exit 1, and Swedish letters plus a euro sign survive JSON -> UTF-8 -> HTTP -> SQLite. - 35 checks on trigger/action/duration descriptions, 20 on the installer's building blocks (task parts built but not registered, credentials file content and ACL, download over HTTP and self-signed HTTPS), 18 on the server rules, and the generated one-liners run through PowerShell's parser. The documented one-liners were run through iex and stop at the administrator check without changing anything. - Found that PowerShell 7 ignores the ServicePointManager certificate override, so the installer's own download now uses -SkipCertificateCheck there. NOT verified: the elevated install itself. Registering a SYSTEM scheduled task needs elevation and changes the machine, so it was not run: the task registration, that the repeating trigger really runs indefinitely, and the agent running as SYSTEM under Task Scheduler have not been exercised. Windows 10 / Server 2016 or newer is assumed; older is untested. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-27 00:09:00 +02:00
bobbanandClaude Sonnet 5	9712d611a6	Add Servers & Tasks module ported from Schedule Task Manager ... Ports cron/systemd task tracking across Debian/Raspbian servers, including the Linux push agent (install/report/uninstall scripts, rebranded from "schedule-task-manager-agent" to "homelab-manager-agent") and the manual-task-entry flow for things an agent can't see (Docker jobs, backups). The schema (servers/scheduled_tasks tables) was already in place from the foundation pass, so this is mostly a straight port of the original's services/routes. Deliberate change from the original: server/token management (which mints agent credentials) is now admin-only rather than open to any logged-in user, and manual task CRUD is gated to operator+ — consistent with how Secrets, IPAM, and DNS already split "configure credentials" from "everyday edits" across roles. All mutations are audit-logged. - server/src/services/tokens.ts, taskSync.ts: ported near-verbatim (agent token hashing, the agent-sync-marks-missing-as-stale-not-deleted logic). - server/src/routes/servers.ts, tasks.ts, agentReport.ts: same contract as the original (agent auth is a per-server bearer token, independent of the session-based requireAuth used everywhere else). - web: a single Servers & Tasks page (filter bar, task table grouped by server/schedule type, manual task form, and an admin-only server management panel with token reveal + copyable install/uninstall commands), replacing the original's two separate pages/apps. Verified: full build passes; a scripted HTTP test against a running server covers unauthenticated access, role gating at each tier (admin-only server mgmt, operator+ task mgmt), agent bearer-token auth (valid/invalid/rotated), manual-vs-agent task edit protection, stale-marking on re-sync, and cascade delete — 22/22 checks passing. Real agent installation on an actual Debian/Raspbian host still needs to be tried on the user's network. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-14 23:16:58 +02:00