No description

Find a file

mwiegand ead4bd1aa4 feat(scripts): add scripts/dev-server.py for local UI smoke Codifies the local-smoke setup so future inspection of the l4d2web UI on macOS is reproducible without a real deploy. Sets the production-equivalent env vars the systemd unit normally gets from /etc/left4me/*.env: - SECRET_KEY (dev placeholder) - DATABASE_URL → .tmp/dev-server/l4d2web.db (gitignored) - LEFT4ME_ROOT → .tmp/dev-server (so overlay-mkdir doesn't try /var/lib/left4me, which is read-only on macOS dev) - SESSION_COOKIE_SECURE=0 so cookies survive http://127.0.0.1 - JOB_WORKER_ENABLED=false so the background worker doesn't shell out to the sudo-requiring production l4d2ctl Runs alembic upgrade head. On first run, auto-seeds: - admin user 'dev' / 'devdevdev' (password chosen to satisfy the ≥8 char policy in l4d2web/auth.py:validate_new_password) - one blueprint with example srccfg content (exercises the highlighter + autocomplete) - one script overlay with bash (exercises the bash highlighter) - one files overlay with a test.cfg (exercises the files-editor modal + language dropdown) - one server linked to the blueprint (exercises the server detail page rendering, though deploy actions still fail) Starts Flask with --debug so code + template changes auto-reload. Stub l4d2ctl for server-deploy actions is deliberately out of scope; documented in the script's docstring. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-05-17 00:04:11 +02:00
deploy	deploy/journalctl: anchor server log to current unit start	2026-05-15 23:04:53 +02:00
docs	fix(editor): capture-phase keydown + popup leak + cache warmup	2026-05-16 20:49:23 +02:00
examples/script-overlays	feat(l4d2-web): seed example script overlays from examples/script-overlays/	2026-05-08 18:41:08 +02:00
l4d2host	refactor(repo): uv workspace + hatchling + layout restructure	2026-05-15 22:04:29 +02:00
l4d2web	feat(blueprint): strip create-modal to name-only	2026-05-17 00:03:57 +02:00
scripts	feat(scripts): add scripts/dev-server.py for local UI smoke	2026-05-17 00:04:11 +02:00
.envrc	chore(envrc): switch direnv from `use uv` to `layout uv`	2026-05-16 13:20:16 +02:00
.gitignore	chore(gitignore): ignore .tmp/ scratch directory	2026-05-16 11:53:14 +02:00
.python-version	refactor(repo): uv workspace + hatchling + layout restructure	2026-05-15 22:04:29 +02:00
AGENTS.md	docs(e2e): note Claude Code sandbox blocks Chromium Mach-port IPC	2026-05-16 22:07:15 +02:00
pyproject.toml	test(e2e): scaffold Playwright + live-server fixture	2026-05-16 21:00:45 +02:00
README.md	refactor(repo): uv workspace + hatchling + layout restructure	2026-05-15 22:04:29 +02:00
uv.lock	test(e2e): scaffold Playwright + live-server fixture	2026-05-16 21:00:45 +02:00

README.md

left4me

left4me is a local L4D2 server management platform with two planned components:

l4d2host + l4d2ctl (host library + CLI)
l4d2-web-app (Flask web app for users, blueprints, servers, jobs, and logs)

Status

Implementation plans remain the source of truth for architecture and task sequencing:

docs/superpowers/plans/2026-04-22-l4d2-host-lib-v1.md
docs/superpowers/plans/2026-04-23-l4d2-web-app-v1.md

Locked v1 Decisions

Naming is strictly l4d2 (not l4d).
Host library and web app are separate components.
Host CLI write commands are fixed to:
- install
- initialize <name> -f <spec.yaml>
- start <name>
- stop <name>
- delete <name>
Host CLI read commands are available for the web/host boundary:
- status <name> --json
- logs <name> --lines <n> --follow/--no-follow
The web app calls host operations through l4d2ctl, not direct l4d2host imports.
Deployment uses /var/lib/left4me for runtime state, /opt/left4me for repository contents and the virtualenv, /etc/left4me for environment files, and global units under /usr/local/lib/systemd/system.
Overlay handling is directory-based; the web app populates each overlay (workshop downloads, managed-global refresh).
No lock manager, no rollback, no preflight checks in host library.
CLI propagates subprocess failures via stderr and return code.
delete on missing instance is no-op success.
Blueprint model (web app):
- user-private in v1
- servers are live-linked to blueprint
- no per-server overrides
- delete blueprint blocked when linked servers exist
- blueprint changes apply on next action
- server can reassign blueprint anytime

Planned Repository Layout

l4d2host/
l4d2web/
deploy/
docs/superpowers/plans/

Deployment

See deploy/README.md for the Linux test deployment contract, including the runtime user, target filesystem layout, systemd units, privileged helpers, sudoers rules, admin bootstrap, and overlay reference rules.

Local development

This repo is a uv workspace (l4d2host + l4d2web as members) with a committed uv.lock and a .python-version pinning Python 3.13 (matching the Debian Trixie production target).

One-time prereq: install uv (macOS: brew install uv; Linux: curl -LsSf https://astral.sh/uv/install.sh | sh — uv is not yet in Debian stable's apt).

direnv allow once per fresh checkout (and after any .envrc change). .envrc uses use uv, which runs uv sync and activates .venv/ on cd.
Without direnv: uv sync at the repo root creates .venv/, installs both workspace members editable, and pulls in dev deps (pytest) from the lockfile.
Tests: uv run pytest (or just pytest once the venv is on PATH).

Tech Stack (planned)

Python 3.13+ (workspace uses uv + hatchling)
Typer, PyYAML, pytest
Flask, SQLAlchemy, Alembic
HTMX (vendored locally), custom CSS, SSE
systemd units, kernel overlayfs (mounted via the left4me-overlay privileged helper), steamcmd

Recommended Implementation Order

Implement l4d2host plan first.
Implement l4d2web plan second.
Keep tests green task-by-task (TDD flow from plans).
Keep commits small and aligned with plan tasks.

Contributing Notes

Follow plan task order unless explicitly re-planned.
Keep contracts above unchanged unless the user asks to change them.
Update plan docs when scope or behavior changes.