Files
cc-ci/tests/wordpress/recipe_meta.py
autonomic-bot d9a446cd36
Some checks failed
continuous-integration/drone/push Build is failing
enroll(wordpress): test suite + bridge POLL_REPOS entry
Enrolls wordpress as a maintained recipe (operator request 2026-08-03):
- tests/wordpress/: recipe_meta (install-wizard-aware health 200/302, 900s deploy
  timeout for mariadb+core-copy first boot, WARM_CANONICAL), custom suite:
  health check, install-wizard completion + REST API round-trip (?rest_route= vs
  /wp-json/ splits DB vs .htaccess failure layers), and the sec4.3 post round-trip
  (XML-RPC write -> REST read -> permalink HTML, unique marker). PARITY.md documents
  the baseline (no recipe-maintainer parity corpus for wordpress).
- nix/modules/bridge.nix: POLL_REPOS += recipe-maintainers/wordpress (!testme bridge
  enrollment; deploy to the cc-ci host follows separately after the in-flight
  /upgrade-all run - test-before-switch policy).

Mirror recipe-maintainers/wordpress created + main synced to coopcloud upstream
(adcd0e9f) with published tags. used-recipes.md gains 'wordpress weekly' in the
orchestrator repo.
2026-08-03 21:05:33 +00:00

13 lines
623 B
Python

# Per-recipe harness config for wordpress (classic PHP app + mariadb). A fresh deploy
# (no POST_DEPLOY_CMDS core_install in the CI env) serves the WP install wizard: GET /
# redirects 302 to /wp-admin/install.php until the custom tier completes the install.
HEALTH_PATH = "/"
HEALTH_OK = (200, 302)
# First boot copies the WP core into the content volume and waits for mariadb init;
# the recipe's own healthcheck has start_period 1m — give the deploy headroom.
DEPLOY_TIMEOUT = 900
HTTP_TIMEOUT = 300
# canon §2.B: enroll as a DATA-WARM canonical (all recipes enrolled — operator 2026-06-17).
WARM_CANONICAL = True