# Per-recipe harness config for plausible (Phase 2 Q4.7 — analytics platform).
# Requires SECRET_KEY_BASE (64+ char), DISABLE_AUTH, DISABLE_REGISTRATION env vars to deploy.
# We use a fixed CI value for SECRET_KEY_BASE — safe for ephemeral per-run deploys.
HEALTH_PATH = "/"
HEALTH_OK = (200, 302)
# plausible's app starts before its clickhouse events DB is ready (the recipe's `app` depends_on lists
# `events_db` but the service is named `plausible_events_db`, so swarm applies no ordering) and returns
# 500 until clickhouse + DB migrations finish — several minutes on a cold deploy. Give a wide HTTP
# window so the health poll waits out that init (it serves 302 once ready). [v1 failed at HTTP_TIMEOUT=600.]
DEPLOY_TIMEOUT = 1200
HTTP_TIMEOUT = 1200

# Phase-2: configure the recipe's required env (no placeholders allowed).
EXTRA_ENV = {
    "DISABLE_AUTH": "true",
    "DISABLE_REGISTRATION": "true",
    # 64-char stable value for CI — plausible (Phoenix) requires >= 64 chars
    "SECRET_KEY_BASE": "ccciplausibletestkeybase64charsexactlyforCIephemeral4567890123",
}