History

mwiegand 058acb9c5c feat(files-overlay): recursive directory delete + fix nested-file save misroute Two related fixes to the overlay file manager, found in the same session. 1. Nested-file save was silently moving the file (fix). The Filename input is pre-filled with the full relative path (intentional: phone-friendly move-via-edit when drag-and-drop isn't an option). The save handler compared it against the basename only, so every save of a file in a subfolder built newPath = parent + "/" + editedFilename and re-routed the file into a doubly-nested path (e.g. cfg/tick60.cfg -> cfg/cfg/tick60.cfg). All three sites in editor.js now compare against relPath. Two e2e tests pin both directions: save-without- edit leaves the file untouched, edit-the-path performs the intended move. 2. Recursive directory delete + visible 409 errors (feature). GET /files/delete_preview enumerates what a recursive delete would remove (files + dirs + symlinks, capped at 500 entries, followlinks=False). POST /files/delete accepts an optional recursive=1 form param that uses shutil.rmtree (default still refuses non-empty dirs, preserving the historical safety guard). The delete confirm modal now opens an inline preview for non-empty folders, with a scrollable list and a count summary. The error handler falls back to r.rawText so the server's text bodies (like "directory is not empty") finally surface to the user instead of "HTTP 409". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-20 19:49:45 +02:00
..
alembic	feat(l4d2-web): add command_history table for RCON console transcript	2026-05-14 21:26:56 +02:00
l4d2web	feat(files-overlay): recursive directory delete + fix nested-file save misroute	2026-05-20 19:49:45 +02:00
scripts	docs(editor): document vocab argument shape on rankVocab	2026-05-17 18:38:01 +02:00
tests	feat(files-overlay): recursive directory delete + fix nested-file save misroute	2026-05-20 19:49:45 +02:00
alembic.ini	chore(l4d2): flatten component layout	2026-05-05 23:47:06 +02:00
pyproject.toml	refactor(repo): uv workspace + hatchling + layout restructure	2026-05-15 22:04:29 +02:00
README.md	refactor(repo): uv workspace + hatchling + layout restructure	2026-05-15 22:04:29 +02:00

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 l4d2ctl via a local host command runner, not direct l4d2host imports

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 example sqlite:////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