- docs/: GitHub Pages site (landing page, docs, live click-through demo)
served straight from /docs, no build step.
- web-demo/: source for the demo (a copy of web/ with its API layer mocked
in-memory) — see web-demo/README.md to rebuild docs/demo after a change.
- web/src/lib/auth.tsx: signOut() no longer clears the whole query cache;
wiping ["auth","setup-status"] forced it to refetch and re-armed
`loading`, stranding the user on a loading/failed screen instead of the
Login page. Only non-auth queries are dropped now.
- .gitignore: exclude web-demo/node_modules and web-demo/dist (build output,
already published as docs/demo).
- Drop PRODUCT.md (internal planning brief, not meant for the public repo).
- README: link the new docs/demo site.
The old screenshots (prod-cluster, 3 nodes, 16 guests) predated Cluster &
SDN, AI Assistant, Bulk Operations, Webhooks, and the accent-color/look
presets added since — none of it showed up in the README. Recaptured every
fleet-data screenshot (dashboard, inventory, topology, storage, backups,
HA, firewall, connections) against a richer fleet: 3 connections (two
clusters, one standalone host), 6 nodes, 26 VMs/LXCs, Ceph + NFS storage.
settings-appearance also refreshed (now shows the amber/rose/teal accents).
setup.png is untouched — it's fleet-data-independent and regenerating it
would mean resetting a real admin account.
Updated the screenshots section caption to match the new fleet size.
- .gitignore/.dockerignore: cover Go build artifacts, env files, logs,
editor/OS cruft, and local runtime data (sqlite db/secret, config.yaml).
- README: add a Screenshots section (captured against a mock Proxmox
cluster) and a Deploying a release build section.
- LICENSE: MIT.
Deployable binaries:
- cmd/ferrum: -version flag with build-time version/commit/date via
-ldflags; -log-file flag (Windows services don't capture stdout/stderr
the way systemd does); native Windows Service Control Manager support
(service_windows.go) so ferrum.exe manages its own start/stop lifecycle
under a Windows service, same graceful-shutdown path SIGTERM already used
on Linux.
- packaging/systemd/ferrum.service: hardened systemd unit.
- scripts/build.sh, build.ps1: cross-compile linux/windows/darwin x
amd64/arm64, package as .tar.gz/.zip with an install script and
checksums.txt.
- scripts/linux/install.sh, uninstall.sh: create a dedicated system user,
install the binary, seed /etc/ferrum/config.yaml, enable + start the
systemd service.
- scripts/get.sh: one-line curl-pipeable installer (get.docker.com style)
that resolves the latest release, verifies its checksum, and hands off
to install.sh.
- scripts/windows/install-service.ps1, uninstall-service.ps1: register/
remove the self-managing Windows service.
- .github/workflows/release.yml: publish all platform archives + checksums
as GitHub Release assets on a vX.Y.Z tag push.
- .github/workflows/ci.yml: go vet/build/test, frontend lint/test/build,
and shell-script syntax checks on push/PR.
Anand