Deploy services independently by changed paths
This commit is contained in:
1 parent
2277a2e9ac
commit
1ba47e4d22
18 files changed
+1462
-894
No files matched your search
+20
-33
@@ -1,8 +1,9 @@
|
||||
#!/usr/bin/env bats
|
||||
# Seam: target reachability and deployment flow integrity.
|
||||
# These tests assert the deployment contract of the unified repo:
|
||||
# - a deploy.sh exists and accepts <dankclaw|dankserver> and --dry-run
|
||||
# - deploy.sh covers both the podman stack and the LLM fleet services
|
||||
# These tests assert the service-scoped deployment contract:
|
||||
# - deploy.sh accepts a target, optional service scope, and --dry-run
|
||||
# - deploy-remote.sh owns per-service handlers and deployment state
|
||||
# - no host-wide inference restart is hidden in the dispatcher
|
||||
# - every host referenced in the repo is reachable over SSH (dank@host)
|
||||
# - the local git remote is configured before deploy is attempted
|
||||
# Reachability tests are SKIPPED when the target is unreachable so the suite
|
||||
@@ -38,44 +39,30 @@ load helpers
|
||||
# Regression: the Caddyfile render step in deploy.sh must survive a bcrypt
|
||||
# hash (which contains '/' characters). Reproduce the sed expression with a
|
||||
# slash-bearing hash and confirm the placeholder is replaced.
|
||||
@test "deploy.sh reloads Caddy after rendering (hot reload, not just container start)" {
|
||||
# The caddy container often survives 'up -d' (a Caddyfile change is a
|
||||
# bind-mount content change, not a container config change). Without an
|
||||
# explicit reload, a rendered fix can sit on disk while Caddy serves the
|
||||
# stale in-memory config.
|
||||
grep -q 'caddy reload' "$REPO_ROOT/scripts/deploy.sh"
|
||||
@test "scoped remote runner owns Caddy reload and safe fallback" {
|
||||
# Caddy is handled only when selected by the planner. A failed reload may
|
||||
# restart Caddy, but must not restart the whole compose project.
|
||||
grep -q 'caddy reload' "$REPO_ROOT/scripts/deploy-remote.sh"
|
||||
grep -q 'podman restart caddy' "$REPO_ROOT/scripts/deploy-remote.sh"
|
||||
! grep -qE 'podman-compose.*(up|restart).*\$\(' "$REPO_ROOT/scripts/deploy-remote.sh"
|
||||
}
|
||||
|
||||
@test "deploy.sh restarts caddy when the reload cannot be applied" {
|
||||
# If the running config has the admin API disabled (or the API is down),
|
||||
# 'caddy reload' can never apply the new file -- the fix cannot be
|
||||
# delivered over the API it is meant to enable. The fallback is a
|
||||
# container restart, which always reads the file.
|
||||
grep -q 'podman restart caddy' "$REPO_ROOT/scripts/deploy.sh"
|
||||
@test "remote runner has separate handlers for both inference services" {
|
||||
grep -q 'deploy_llm_large' "$REPO_ROOT/scripts/deploy-remote.sh"
|
||||
grep -q 'deploy_llm_small' "$REPO_ROOT/scripts/deploy-remote.sh"
|
||||
}
|
||||
|
||||
# The unified deploy.sh must manage the LLM fleet services on both hosts:
|
||||
# frank-default-small (dankserver) and frank-default-large (dankclaw). A
|
||||
# deploy that only restarts the podman stack leaves the LLM units pointing
|
||||
# at the retired vllmScripts checkout.
|
||||
@test "deploy.sh restarts the LLM services on both targets" {
|
||||
grep -q 'frank-default-small' "$REPO_ROOT/scripts/deploy.sh"
|
||||
grep -q 'frank-default-large' "$REPO_ROOT/scripts/deploy.sh"
|
||||
@test "inference restarts are absent from the top-level dispatcher" {
|
||||
! grep -qE 'systemctl .*restart (frank-default-small|frank-default-large)' "$REPO_ROOT/scripts/deploy.sh"
|
||||
}
|
||||
|
||||
@test "deploy.sh health-checks both LLM endpoints (both on :7770, by host)" {
|
||||
# 2026-08-22: frank-default-large moved from :52625 to :7770 on
|
||||
# dankclaw. Both LLM services now listen on :7770, distinguished by
|
||||
# host (dankserver vs dankclaw).
|
||||
grep -qE '^LLM_HEALTH\[dankserver\]="http://127\.0\.0\.1:7770/health"' "$REPO_ROOT/scripts/deploy.sh"
|
||||
grep -qE '^LLM_HEALTH\[dankclaw\]="http://127\.0\.0\.1:7770/health"' "$REPO_ROOT/scripts/deploy.sh"
|
||||
@test "remote runner health-checks an inference endpoint" {
|
||||
grep -q '127.0.0.1:7770/health' "$REPO_ROOT/scripts/deploy-remote.sh"
|
||||
}
|
||||
|
||||
@test "deploy.sh pulls on the merged checkout on both targets" {
|
||||
# Both targets run the whole stack (podman + LLM) from one checkout.
|
||||
local count
|
||||
count=$(grep -c '/home/dank/serverAppConfigs' "$REPO_ROOT/scripts/deploy.sh")
|
||||
[ "$count" -ge 2 ]
|
||||
@test "deploy.sh pulls the merged checkout on the target" {
|
||||
grep -q 'git pull --ff-only origin main' "$REPO_ROOT/scripts/deploy.sh"
|
||||
grep -q '/home/dank/serverAppConfigs' "$REPO_ROOT/scripts/deploy.sh"
|
||||
}
|
||||
|
||||
@test "deploy.sh Caddyfile render survives a slash-bearing bcrypt hash" {
|
||||
|
||||
Reference in new issue
Block a user