The five-minute version: download, run, point it at a folder of documents, share the link. Here’s roughly the shape of it —
Full walkthrough with screenshots lands here shortly.
Per-platform setup for Linux (x86-64), Raspberry Pi (ARM64), and Windows — including running AckMan as a background service so it stays up after a reboot.
Ports, document directories, branding, and how acknowledgements are recorded and stored. Sensible defaults, with knobs when you need them.
Run AckMan behind the office firewall on a spare box or a Raspberry Pi. Covers local networking, reverse proxies, and keeping everything inside your four walls.
Stand it up on a cloud VM for distributed and remote teams — TLS, domains, and access basics so people can ack from anywhere.
How to drop in handbooks, memos, and training files, group them, and decide which ones require an acknowledgement versus a plain read.
The good part: see who opened what and who ack’d it, filter by document or person, and export the records for HR, training, or audits.
Locking things down, keeping the acknowledgement log safe, and backing up your records so the receipts survive a hardware hiccup.
The questions everyone asks: file types supported, how many people it scales to, what counts as an “ack,” and whether Doc ever sleeps. (He doesn’t.)
The GitHub repo goes public soon — watch it there for the full guide and release notes.
