49992b3a26
Migrate from pip-install-e + setuptools to a uv workspace with a
committed uv.lock for deterministic deps. Switch both members to
hatchling, and move package sources into nested standard layout
(l4d2host/l4d2host/, l4d2web/l4d2web/) so builds work from a
read-only source tree — setuptools wrote egg-info to source under
the old layout, which broke uv sync on the root-owned /opt/left4me/src.
Local dev install: `pip install -e ./l4d2host -e ./l4d2web` -> `uv sync`.
.envrc switches from `layout python python3.13` to `use uv`. Python
pinned to 3.13 via .python-version.
l4d2web now declares its cross-dep on l4d2host explicitly via
[tool.uv.sources] (workspace = true). l4d2web/alembic.ini and
l4d2web/alembic/ stay at the project root (standard alembic layout).
Test fixes:
- tests/__init__.py added to both test dirs so pytest doesn't shadow
l4d2host as a namespace package via outer-dir walk.
- 3 CWD-relative paths in tests (l4d2web/static/css/{tokens,layout}.css
and js/sse.js) anchored to Path(__file__) so they survive layout
changes.
- Two test_install.py tests now monkeypatch HOME to tmp_path so they
stop silently mutating ~/.steam/sdk32 on every run.
628 tests pass under sandboxed `uv run pytest`.
Per docs/superpowers/plans/2026-05-15-uv-workspace-execution.md;
prereq for the ckn-bw bundle's uv-sync action (queued).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
# 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 (`../`):
|
|
|
|
```bash
|
|
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`:
|
|
|
|
```bash
|
|
LEFT4ME_ADMIN_PASSWORD='change-me' flask create-user <username> --admin
|
|
```
|