Read-only file explorers (server detail page, read-only overlay) used to omit the hover-action panel entirely and make the filename itself the download link. Editable overlays did the opposite: hover-action panel with download + delete, filename-click opens the editor. Unify both surfaces around the editable pattern: always emit the hover-action span when any action applies. Gate the download button on download_supported only (now visible on all surfaces). Keep delete + folder actions (+file, +folder, zip) gated on files_overlay, since read-only surfaces never offer those. In read-only mode, the filename becomes a plain <span> — the hover ⬇ is the single download affordance, matching editable mode's filename-click ≠ hover-download split. Prefactor for the files-overlay.js rewrite (docs/superpowers/plans/ 2026-05-17-files-overlay-rewrite.md). No JS changes; files-overlay.js doesn't run on read-only surfaces (manager-element guard at line 23-24). Verified: pytest stayed at 573/1/3 (URL substrings still appear in the rendered HTML even though they moved out of the filename anchor into the hover-action span). Direct Jinja render confirmed all four branches: read-only downloadable file (new hover ⬇, plain <span> filename), broken read-only symlink (no hover panel — correct, can't download dangling links), read-only download_supported=False (no hover panel, plain <span>), editable mode (byte-identical to before). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| alembic | ||
| l4d2web | ||
| scripts | ||
| tests | ||
| alembic.ini | ||
| pyproject.toml | ||
| README.md | ||
l4d2-web-app
Flask web app for managing L4D2 servers through user-private blueprints.
Key v1 behaviors
- Local username/password login; no public signup
- Admin-managed overlay catalog
- Private blueprints per user
- Server creation from blueprints (live-linked; no per-server blueprint overrides)
- Async job model with persisted command logs in
job_logs - Desired vs actual state model
- Live logs for jobs and servers via SSE endpoints
- Host operations go through
l4d2ctlvia a local host command runner, not directl4d2hostimports
Frontend constraints
- Server-rendered templates (Jinja)
- Vendored HTMX (
static/vendor/htmx.min.js) - Custom CSS only
- Tokenized, consistent link and accent colors
Development
From the workspace root (../):
uv sync # creates .venv, installs l4d2host + l4d2web editable, plus dev deps
uv run pytest l4d2web/tests -q
Configuration
The web app reads these settings from the environment:
DATABASE_URL: SQLAlchemy database URL, for examplesqlite:////var/lib/left4me/left4me.db.SECRET_KEY: Flask secret key used for sessions and CSRF-sensitive state.JOB_WORKER_THREADS: number of background job worker threads.
In the systemd deployment, environment is loaded from /etc/left4me/host.env and /etc/left4me/web.env.
Admin Bootstrap
Create the first admin account with the Flask CLI. Provide the password through LEFT4ME_ADMIN_PASSWORD:
LEFT4ME_ADMIN_PASSWORD='change-me' flask create-user <username> --admin