Files
Do SikiandClaude Sonnet 5 d8cccc1a65
CI Pipeline with Test Management / 🧪 Run Tests & Generate Reports (push) Canceled after 0s
Test Reporting & Gherkin Analysis / 🧪 Run Tests & Generate Reports (push) Canceled after 0s
CI Pipeline with Test Management / 🐳 Docker Integration Tests (push) Canceled after 0s
CI Pipeline with Test Management / 🏗️ Build Docker Image (push) Canceled after 0s
CI Pipeline with Test Management / 📊 Generate Test Summary (push) Canceled after 0s
Test Reporting & Gherkin Analysis / 📊 Analyze Test Coverage (push) Canceled after 0s
Test Reporting & Gherkin Analysis / 🔄 Sync with Linear (push) Canceled after 0s
Test Reporting & Gherkin Analysis / ⚡ Performance Monitoring (push) Canceled after 0s
fix(deploy): drop stale content-editor systemd restart from staging script
scripts/deploy_to_stage_on_local.sh restarted a
"mozdit-content-editor.service" systemd unit after every staging deploy
— the old custom CMS's own service (content-editor.js, retired in
MITHOME-93). Left in place, the next staging deploy would pull the
commit that deletes content-editor.js and then try to restart a
service pointing at a now-missing script.

Removed the restart from the deploy script; the server-side systemd
unit itself (if still installed) needs a manual stop/disable — out of
reach from here (no SSH access in this session), flagging it to the
user instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-09-11 22:13:47 +02:00
..