mhoennigandClaude Opus 5.5
d3b32f7fc9
One program, three modes: `local` (as before), `server` on a host such as a Hostsharing Managed Webspace, reading Werkator and Gitea itself and accepting reports, and `relay` on each Linux machine with coding agents, posting the state of Claude Code and Codex every five seconds — the connection goes out, nothing has to reach in. The server creates an access token on its first start (0600, `token` prints it). Browsers enter it with a key button and keep it as cookie, relays send it as bearer header only, so no other site can make a logged-in browser post reports. Without it the page shows invented demo data. A silent relay turns stale after 30 s and its open sessions end after 120 s; the last reports survive a restart in relays.json. `runtimeBundle` packs a jlink JRE (Temurin 21), the jars and a launcher; `init server|relay` writes the systemd user unit with an optional EnvironmentFile for tokens, and for the server the .htaccess proxy and maintenance page of Werkator's Hostsharing setup. Version 0.2.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
13 lines
458 B
Desktop File
13 lines
458 B
Desktop File
# systemd user unit: cp to ~/.config/systemd/user/, then
|
|
# systemctl --user daemon-reload && systemctl --user enable --now werkregie-dashboard
|
|
[Unit]
|
|
Description=Werkregie-Dashboard (localhost)
|
|
|
|
[Service]
|
|
ExecStart=%h/Projekte/werkregie/dashboard/build/install/werkregie-dashboard/bin/werkregie-dashboard local
|
|
# EnvironmentFile=%h/.config/werkregie/tokens.env # e.g. WERKREGIE_TOKEN_HOSTSHARING=…
|
|
Restart=on-failure
|
|
|
|
[Install]
|
|
WantedBy=default.target
|