Frank
e7eaba4457
Two real bugs found on the first production deploy: - /admin/ 404'd: file_server looked for /srv/homepage/admin/ (a dir), but the page is admin.html. Add '@admin rewrite * /admin.html' so the /admin/ path serves admin.html. - The pages used relative refs (style.css, app.js, services.json, status.json), which from /admin/ resolved to /admin/... (404). Add <base href="/"> so all refs resolve to the site root on both pages. - status.json was written 0600 (root); the checker now chmods it 0644 so Caddy can serve it regardless of its user.
31 lines
1007 B
Bash
31 lines
1007 B
Bash
#!/usr/bin/env bats
|
|
# Seam: the homepage site block in dankclaw/Caddyfile. It must carry a root
|
|
# basicauth hash and a distinct /admin/-scoped admin hash (Q18/Q19), and serve
|
|
# /srv/homepage. caddy is not on the dev box, so the tests assert the
|
|
# structure statically; the deploy renders the two real hashes from the .env.
|
|
|
|
load helpers
|
|
|
|
setup() {
|
|
CADDY="$REPO_ROOT/dankclaw/Caddyfile"
|
|
}
|
|
|
|
@test "the homepage has a root hash and a distinct admin hash (Q18/Q38)" {
|
|
grep -q "REPLACE_WITH_HASH" "$CADDY"
|
|
grep -q "REPLACE_WITH_ADMIN_HASH" "$CADDY"
|
|
}
|
|
|
|
@test "the admin basicauth is scoped to /admin/ (Q19)" {
|
|
grep -qE "@admin[[:space:]]+path[[:space:]]+/admin/" "$CADDY"
|
|
grep -qE "basicauth[[:space:]]+@admin" "$CADDY"
|
|
}
|
|
|
|
@test "the homepage serves /srv/homepage" {
|
|
grep -q "root \* /srv/homepage" "$CADDY"
|
|
grep -q "file_server" "$CADDY"
|
|
}
|
|
|
|
@test "the /admin/ path is rewritten to admin.html" {
|
|
grep -qE "@admin[[:space:]]+rewrite[[:space:]]+\*[[:space:]]+/admin.html" "$CADDY"
|
|
}
|