mirror of
https://github.com/Memo-2023/mana-monorepo.git
synced 2026-05-15 00:01:10 +02:00
af9b1f9369
The previous startup.sh checked colima status via `colima status | grep running` and, if that failed, ran `colima stop --force` unconditionally before starting. This is destructive: a transient status mis-detection can kill a healthy running VM, and the subsequent start often hangs because of leftover locks/processes. Triggered today during the ManaCore→Mana rename: reloading the docker-startup LaunchAgent ran the script, which falsely concluded colima was down, killed the running VM, and left 12 zombie limactl processes plus a stale disk lock symlink. The whole production stack (incl. Forgejo) was offline until manual cleanup. Changes: - Use `docker info` as the readiness check instead of `colima status` — it directly tests the thing we care about (docker socket reachable) - Only do cleanup work when we actually need to start; never SIGKILL a running VM as a "precaution" - When we do need to start: reap any zombie limactl/colima processes from prior failed runs, and clear the stale disk-in-use lock if no process actually holds it - Verify successful start with `docker info`, not `colima status` Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| mac-mini | ||
| test-data | ||
| test-reporting | ||
| audit-workspace-deps.mjs | ||
| backup-monitoring.sh | ||
| check-status.sh | ||
| create-gift-codes.mjs | ||
| deploy-metrics.sh | ||
| ecosystem-audit.mjs | ||
| fix-mixed-imports.mjs | ||
| generate-dockerfiles.mjs | ||
| generate-env.mjs | ||
| generate-status-page.sh | ||
| lighthouse-audit.sh | ||
| run-tests-with-coverage.sh | ||
| setup-databases.sh | ||
| validate-dockerfiles.mjs | ||
| validate-monorepo.mjs | ||