History

mwiegand 4d045e578d feat(files): migrate create-new-file JS flow to URL-addressable modal Step 6/12 of docs/superpowers/plans/2026-05-17-files-overlay-rewrite.md. Two changes in editor.js: 1. The "new-file" registered handler now opens the URL-addressable modal at GET /overlays/<id>/files/new?at=<folder> via window.modals.openRouted, replacing the call to openEditorTextNew. The legacy openEditorTextNew function stays in this file for now — it's no longer reachable from a user action; Step 9 deletes it alongside the rest of the legacy dialog block. 2. routedSaveClicked gains an is_new branch. When the textarea's data-rel-path is empty, the save composes the new file's path from data-at-folder (set by the /files/new route) + the user-typed filename and POSTs {path, content} to /files/save. The /save endpoint creates the file when it doesn't exist; 409 means a file at that path already exists and the user picks a different name (alert + modal stays open so the form value is preserved). The legacy slash-in-filename guard from openEditorTextNew's legacy save path is deliberately not carried over — the plan permits typing "sub/foo.txt" in the filename input to create a nested file via /save, matching the route's path semantics. Verified live on /overlays/2 in Chromium: * Click "+ new file" on overlay root → URL becomes ?modal=%2Foverlays%2F2%2Ffiles%2Fnew%3Fat%3D * Routed modal opens with empty data-rel-path, empty data-at-folder, empty filename input, save button labeled "Create", no Delete or Download buttons, title "…new file" * No console errors * pytest still 578 passed, 1 skipped, 3 deselected (no Python or test changes in Step 6) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-17 16:05:55 +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): migrate create-new-file JS flow to URL-addressable modal	2026-05-17 16:05:55 +02:00
scripts	fix(editor-v2): fix cm6 to rows-derived height, eliminate layout shift	2026-05-17 10:27:28 +02:00
tests	feat(files): add GET /overlays/<id>/files/new + extend editor template	2026-05-17 16:03:01 +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