ttyd serves a single-file xterm.js UI styled with the LotusGuild TDS (web_template base.css). Sessions live in a dedicated tmux server unit (devdesk-tmux.service), so restarting or upgrading the web unit never stops Claude. Each named session maps to a project directory. A Claude SessionStart hook records the conversation ID, so after a reboot the session resumes that exact conversation. - bin/devdesk: attach / new / ls / end / pick, with an fzf picker - ttyd requires a credential that NPM injects; origin check enabled - debian/: dh 13 with --no-stop-on-upgrade for the tmux unit, bundled sha256-verified ttyd 1.7.7, lintian overrides, man page - CI: lint, test, build, smoke-test, artifact; v* tags publish to the Gitea apt registry and create a release Refs: tinker ticket 887531976 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Deploying DevDesk (CT 126 · dev.lotusguild.org)
1. Install the package
Add the Gitea apt repository once:
curl -fsSL https://code.lotusguild.org/api/packages/LotusGuild/debian/repository.key \
-o /etc/apt/keyrings/gitea-LotusGuild.asc
echo "deb [signed-by=/etc/apt/keyrings/gitea-LotusGuild.asc] https://code.lotusguild.org/api/packages/LotusGuild/debian bookworm main" \
> /etc/apt/sources.list.d/lotusguild.list
apt update && apt install devdesk
On install, /etc/devdesk/secret.env is generated, devdesk-tmux.service and devdesk.service are enabled and started, and ttyd listens on :7681. Requests without the credential get a 401.
2. Nginx Proxy Manager (CT 139)
- Proxy host:
dev.lotusguild.org→http://10.10.10.58:7681.- Websockets Support on.
- SSL: the existing wildcard
*.lotusguild.orgcertificate, with Force SSL.
- Advanced tab: paste
npm-advanced.conf, replacing__DEVDESK_BASIC__with the output of:. /etc/devdesk/secret.env && printf '%s' "$DEVDESK_CREDENTIAL" | base64 -w0 - Why the credential matters: ttyd only checks the credential, so anything on the LAN that bypasses NPM is refused. If you rotate it, delete
secret.env, rundpkg-reconfigure devdesk, update NPM, thensystemctl restart devdesk.
3. Authelia (CT 167)
Add these to access_control.rules in /etc/authelia/configuration.yml, above any broader *.lotusguild.org rule:
- domain: dev.lotusguild.org
policy: two_factor
subject: ['user:jared']
- domain: dev.lotusguild.org
policy: deny
Then run authelia validate-config --config /etc/authelia/configuration.yml && systemctl restart authelia.
4. DNS
- Cloudflare: add a CNAME
dev→ apex, DNS-only (grey cloud). - Pi-hole: add
"10.10.10.27 dev.lotusguild.org"todns.hostsinpve-infra/containers/163-pihole/etc/pihole/pihole.toml. A push auto-deploys it, and LAN clients then reach NPM directly instead of hairpinning.
5. Optional hardening
Enable the Proxmox firewall on CT 126 (firewall=1 on net0) and allow tcp/7681 only from 10.10.10.27. The same rule suits code-server on :8680.
Operations
| Task | Command |
|---|---|
| Sessions | devdesk ls |
| Attach over SSH | devdesk attach <name> (or devdesk pick) |
| End a session | devdesk end <name> (or [x] in the Claude window's exit menu) |
| Restart the web side (safe) | systemctl restart devdesk |
| Stop every session | systemctl stop devdesk-tmux |
| Logs | journalctl -u devdesk -u devdesk-tmux |
| UI-only update | replace /usr/share/devdesk/index.html (ttyd re-reads it per request) |