ericrisco/rsc-harness / skills/deployment
deployment
VerifiedUse when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is `coolify`, `vercel`, `railway`, `render`), NOT the Dockerfile alone (that is `docker`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 16.4 KB |
| evals/README.md | markdown | 2.7 KB |
| evals/cases.yaml | config | 5.7 KB |
| references/coolify.md | markdown | 14.3 KB |
| references/dockerfiles-by-stack.md | markdown | 10.6 KB |
| references/github-actions.md | markdown | 8.9 KB |
| references/hosting-targets.md | markdown | 15.4 KB |
| scripts/verify.shexecutable | script | 6.3 KB |
scripts/verify.sh
View on GitHub#!/usr/bin/env bash
# verify.sh — deployment gate. Run inside YOUR project; CI runs the same file (parity).
#
# Usage:
# bash scripts/verify.sh
#
# Checks (each skips with a yellow warning if its tool is missing — never fails on absence):
# 1. discover Dockerfiles / compose / workflows (no artifacts -> exit 0)
# 2. hadolint each Dockerfile
# 3. actionlint .github/workflows
# 4. trivy config (Dockerfile/compose/IaC misconfig)
# 5. docker build smoke (skippable: SKIP_DOCKER_BUILD=1)
# 6. trivy image (only if step 5 built an image)
# 7. hosting config lint (vercel.json JSON validity — detect-or-skip)
# 8. summary; exit non-zero only on a real failure
#
# Hosting targets (Vercel / Hetzner+Coolify / …) are documented in
# references/hosting-targets.md. Most are config-light: there is nothing to lint for a
# Hetzner box or a Coolify resource (state lives in the platform, not the repo). The one
# repo-local artifact worth a sanity check is vercel.json, and only if it exists.
#
# Env: SKIP_DOCKER_BUILD=1 to skip the build smoke; NO_COLOR=1 to disable color.
#
# Portability: runs on stock macOS bash 3.2 (no `mapfile`, no bash-4 features) and
# on CI's bash 5 — that local<->CI parity is the whole point. Arrays are populated
# without `mapfile` and always pre-initialised so `set -u` can't abort on an empty
# array under bash 3.2.
set -euo pipefail
have() { command -v "$1" >/dev/null 2>&1; }
# bash 3.2 aborts on `"${arr[@]}"` when arr is empty *and* unset under `set -u`.
# Initialise every array up front and guard expansions with `${arr[@]+...}` so an
# empty array is never an unbound-variable error. Never use `mapfile` (bash 4+).
DOCKERFILES=()
if [[ -n "${NO_COLOR:-}" ]]; then YEL=""; GRN=""; RED=""; RST=""
else YEL=$'\033[33m'; GRN=$'\033[32m'; RED=$'\033[31m'; RST=$'\033[0m'; fi
warn() { printf '%s[skip]%s %s\n' "$YEL" "$RST" "$*"; }
ok() { printf '%s[ ok ]%s %s\n' "$GRN" "$RST" "$*"; }
fail() { printf '%s[fail]%s %s\n' "$RED" "$RST" "$*"; }
FAILED=0
BUILT_IMAGE=""
SMOKE_TAG="verify-smoke:local"
# 1. discover
# Parenthesize the `-name ... -o -name ...` group so the path filter (-not -path)
# applies to BOTH name patterns — otherwise the second pattern matches vendored or
# example Dockerfiles and we'd smoke-build the wrong one. Read results with a while
# loop (bash-3.2-safe; no `mapfile`). NUL-delimited so paths with spaces survive.
while IFS= read -r -d '' df; do
DOCKERFILES+=("$df")
done < <(find . \
\( -path '*/node_modules/*' -o -path '*/vendor/*' -o -path '*/.git/*' \
-o -path '*/examples/*' -o -path '*/example/*' -o -path '*/testdata/*' \) -prune \
-o \( -name 'Dockerfile' -o -name 'Dockerfile.*' \) -type f -print0 2>/dev/null)
WORKFLOWS_DIR=".github/workflows"
HAVE_WORKFLOWS=0; [[ -d "$WORKFLOWS_DIR" ]] && HAVE_WORKFLOWS=1
COMPOSE=$(find . -maxdepth 2 \( -name 'compose*.y*ml' -o -name 'docker-compose*.y*ml' \) 2>/dev/null | head -n1 || true)
if [[ ${#DOCKERFILES[@]} -eq 0 && $HAVE_WORKFLOWS -eq 0 && -z "$COMPOSE" ]]; then
printf 'No Dockerfiles, compose files, or workflows found — nothing to gate.\n'; exit 0
fi
# 2. hadolint
if [[ ${#DOCKERFILES[@]} -eq 0 ]]; then
warn "no Dockerfile found — skipping Dockerfile lint"
elif have hadolint; then
# `${arr[@]+"${arr[@]}"}` guards the expansion so an empty array is safe under
# `set -u` on bash 3.2 (we already know it's non-empty here, but stay consistent).
for df in ${DOCKERFILES[@]+"${DOCKERFILES[@]}"}; do
if hadolint --failure-threshold warning "$df"; then ok "hadolint $df"
else fail "hadolint $df"; FAILED=1; fi
done
else warn "hadolint not installed — skipping Dockerfile lint"; fi
# 3. actionlint
if [[ $HAVE_WORKFLOWS -eq 1 ]]; then
if have actionlint; then
if actionlint; then ok "actionlint"; else fail "actionlint"; FAILED=1; fi
else warn "actionlint not installed — skipping workflow lint"; fi
fi
# 4. trivy config
if have trivy; then
if trivy config --exit-code 1 --severity HIGH,CRITICAL .; then ok "trivy config"
else fail "trivy config"; FAILED=1; fi
else warn "trivy not installed — skipping config/image scan"; fi
# 5. docker build smoke
if [[ -n "${SKIP_DOCKER_BUILD:-}" ]]; then
warn "SKIP_DOCKER_BUILD set — skipping build smoke"
elif have docker && [[ ${#DOCKERFILES[@]} -gt 0 ]]; then
DF="${DOCKERFILES[0]}"
if DOCKER_BUILDKIT=1 docker build --pull -t "$SMOKE_TAG" -f "$DF" "$(dirname "$DF")"; then
ok "docker build $DF"; BUILT_IMAGE="$SMOKE_TAG"
else fail "docker build $DF"; FAILED=1; fi
else warn "docker not available or no Dockerfile — skipping build smoke"; fi
# 6. trivy image (only if we built one)
if [[ -n "$BUILT_IMAGE" ]]; then
if have trivy; then
if trivy image --exit-code 1 --severity HIGH,CRITICAL --ignore-unfixed "$BUILT_IMAGE"; then
ok "trivy image $BUILT_IMAGE"
else fail "trivy image $BUILT_IMAGE"; FAILED=1; fi
else warn "trivy not installed — skipping image scan"; fi
fi
# 7. hosting config lint — vercel.json JSON validity (detect-or-skip).
# Only runs if a vercel.json exists. Prefer python3/node: they set a reliable non-zero
# exit on malformed JSON. jq is the last resort and MUST use `-e` — some jq builds (e.g.
# Apple's jq-1.6) print a parse error to stderr but still exit 0 without it. If none of
# the three is installed, skip — never fail on a missing linter.
VERCEL_JSON=$(find . -maxdepth 2 -name 'vercel.json' -not -path '*/node_modules/*' 2>/dev/null | head -n1 || true)
if [[ -n "$VERCEL_JSON" ]]; then
if have python3; then
if python3 -c 'import json,sys; json.load(open(sys.argv[1]))' "$VERCEL_JSON" >/dev/null 2>&1; then
ok "vercel.json valid JSON ($VERCEL_JSON)"
else fail "vercel.json is not valid JSON ($VERCEL_JSON)"; FAILED=1; fi
elif have node; then
if node -e 'JSON.parse(require("fs").readFileSync(process.argv[1],"utf8"))' "$VERCEL_JSON" >/dev/null 2>&1; then
ok "vercel.json valid JSON ($VERCEL_JSON)"
else fail "vercel.json is not valid JSON ($VERCEL_JSON)"; FAILED=1; fi
elif have jq; then
if jq -e . "$VERCEL_JSON" >/dev/null 2>&1; then ok "vercel.json valid JSON ($VERCEL_JSON)"
else fail "vercel.json is not valid JSON ($VERCEL_JSON)"; FAILED=1; fi
else warn "no python3/node/jq — skipping vercel.json validation"; fi
fi
# 8. summary
if [[ $FAILED -eq 0 ]]; then ok "all checks passed (skips are not failures)"
else fail "one or more checks failed"; fi
exit "$FAILED"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |