Phase 2b: serve static frontends in place from repo dist

The Caddyfile generator now emits static-frontend routes that root directly at
<source>/<build.outputs[0]> (e.g. /data/repos/castle/app/dist) instead of a copy
under ~/.castle/artifacts/content. Removes _copy_app_static and the central
content-dir staging entirely; rebuilds are live without a copy step.

- caddyfile.py: manifest-driven static routes (castle-app at /, others at /<name>)
- ReactViteHandler.install just builds in place (no copy); uninstall is a no-op
- is_active(static frontend) = repo dist exists
- test isolation updated for the generator's config use

Dashboard + power-graph-app verified serving from repo dist; 168 tests pass.
This commit is contained in:
2026-06-13 18:16:09 -07:00
parent 2953aea548
commit 482524bfe5
6 changed files with 86 additions and 84 deletions

View File

@@ -34,14 +34,21 @@ class TestIsActive:
config = load_config(castle_root)
assert lifecycle.is_active("does-not-exist", config) is False
def test_static_frontend_checks_content_dir(self, castle_root: Path, tmp_path: Path) -> None:
def test_static_frontend_active_when_dist_built(self, castle_root: Path, tmp_path: Path) -> None:
from castle_core.manifest import BuildSpec
config = load_config(castle_root)
repo = tmp_path / "fe"
config.programs["fe"] = config.programs["test-tool"].model_copy(
update={"id": "fe", "behavior": "frontend", "source": "/tmp/fe"}
update={
"id": "fe",
"behavior": "frontend",
"source": str(repo),
"build": BuildSpec(commands=[["pnpm", "build"]], outputs=["dist"]),
}
)
content = tmp_path / "content"
(content / "fe").mkdir(parents=True)
with patch.object(lifecycle, "CONTENT_DIR", content):
assert lifecycle.is_active("fe", config) is True
with patch.object(lifecycle, "CONTENT_DIR", tmp_path / "empty"):
assert lifecycle.is_active("fe", config) is False
# No dist yet → inactive
assert lifecycle.is_active("fe", config) is False
# Built dist → served in place → active
(repo / "dist").mkdir(parents=True)
assert lifecycle.is_active("fe", config) is True