mirror of
https://github.com/jhd3197/ServerKit.git
synced 2026-11-09 05:24:49 +09:00
Juan DenisandClaude Opus 5
18767c2244
serverkit-email's live copy under app/plugins/ was the only git-TRACKED one, which is what kept test_builtin_extension_drift non-vacuous on a fresh clone. Plan 52's cutover deletes it, so on CI the guard had zero pairs to compare and test_drift_check_is_not_vacuous fired -- correctly. It still passed on a dev box, where the gitignored live copies exist, so the failure only reproduces in a clean checkout. Track serverkit-status's live copy instead (verified byte-identical to builtin-extensions/serverkit-status/backend), un-ignore just that path, and update both docstrings to name the new anchor. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
17 lines
838 B
Python
17 lines
838 B
Python
"""ServerKit Status Pages extension backend package.
|
|
|
|
Extracted from core (plan 47): the status-pages blueprint (public status/badge
|
|
routes + authenticated management API) and its service ship here so a fresh panel
|
|
that never publishes a status page loads none of it. Mounted under
|
|
``/api/v1/status`` via the manifest's ``url_prefix``; the public /status/<slug>
|
|
and /status/badge/<slug> pages work whenever the extension is installed. The
|
|
StatusPage / StatusComponent / StatusIncident / HealthCheck models stay in core
|
|
(G2). Core's WordPress health-check job reaches
|
|
``StatusPageService.sync_component_from_health`` through
|
|
``plugin_service.get_installed_extension_attr`` only when installed. Upgrades
|
|
re-acquire it automatically (``CONVERTED_BUILTIN_SLUGS``).
|
|
"""
|
|
from .status_pages import status_pages_bp
|
|
|
|
__all__ = ['status_pages_bp']
|