Files
computer-playbook/scripts/tests/workspace/compose/02_performance.sh
T
kevinveenbirkenbachandClaude Opus 5 3ea989a713 style: delete the comments the policy rejects across the tree
121 lines of restated code, step narration, section banners and rationale
prose, in workflow YAML, compose overrides, group_vars, lookup and action
plugins, role tasks, shell scripts and tests.

Three lines go the other way: where a reason has to survive it is now a
registered nocheck directive carrying it, not free prose. Two of them point at
an invariant further down the same file, the third records why an end-of-life
object store keeps no Playwright surface.

Scope was decided per line rather than per file. Classifying by "no additions"
would have swept roles/web-app-erpnext/tasks along with it, where the removed
lines are delegate_to, environment and cmd — a behaviour change that has no
business in a comment commit.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-10-03 01:23:08 +02:00

24 lines
898 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
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}"