Edu-Carone-SA makes Mike deployments safer to ship
This fork turns deployment from a hopeful push into a sequence that checks the database and services are ready.
Edu-Carone-SA has added a deliberate database-update step before the application goes live. It runs separately, waits for success, and exposes operational logs when something goes wrong, making a failed release easier to diagnose rather than quietly leaving the system half-updated.
- Database changes run before the new service version is deployed, with an option to skip the step when no changes are needed.
- Release images now match the cloud cluster's ARM-based hardware, preventing a build from arriving in a form the service cannot run.
- Each release gets its own fixed image reference, avoiding collisions with protected image tags.
- Service checks, startup timing and required backend access have also been tightened so deployments have a clearer path to a healthy state.
So what Legal-product teams running Mike in their own cloud environment should care because this makes routine releases more predictable and failures more visible.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?