Files
computer-playbook/scripts/tests/workspace/compose/02_performance.sh
T
kevinveenbirkenbachandClaude Opus 5.5 b24eabef55 fix(workspace): keep the docs chain out of the matomo performance deploy
CI run 40979252521: the workspace compose jobs (ubuntu, centos, manjaro)
ran out of the 345-minute budget inside compose/02_performance. On
store-i18n matomo variant 1 pins web-app-docs, whose variant 0 enables
dashboard, matomo, prometheus and design, and prometheus pulls the AI
chain, so round 1 of the matomo-only deploy grew from 1 app (main) to
12; all three jobs were cancelled inside the web-app-docs Playwright run.

The step now disables docs next to tor, so round 1 deploys matomo alone
as on main and the following dashboard-unreachable check holds again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-30 10:33:38 +01:00

24 lines
903 B
Bash
Executable File

#!/usr/bin/env bash
# Deploy on performance hardware — deploy the full set of applications.
set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# shellcheck source=scripts/tests/workspace/utils/common.sh
source "${SCRIPT_DIR}/../utils/common.sh"
echo "Deploying matomo (full cycle: deploy + update pass) so it becomes reachable via its dedicated inventory entry."
make compose-deploy mode=reinstall apps="${MATOMO_APP}" full_cycle=true disable=tor,docs
inspect
echo "Re-trusting the CA after the fresh deploy rebuilt the certificates."
make network-trust-ca
matomo_url="$(stack_url matomo)"
dashboard_url="$(stack_url dashboard)"
echo "Verifying matomo is now reachable after its dedicated deploy."
assert_http_status 200 "${matomo_url}"
echo "Verifying the dashboard is no longer reachable after the matomo-only fresh deploy."
assert_http_status 000 "${dashboard_url}"