Galaxy now runs health checks before activating new versions
A few weeks ago, we announced the version restore feature, which allows you to easily reactivate a previous version of your app in Galaxy. This was especially handy in the case of faulty deploys, but we’re excited to announce new precautions that will help prevent a bad deploy from ever going live in the first place! Meteor Galaxy will now run health checks on a deploying version before activating it.
How it works
When you upload a new version that builds successfully, Galaxy will begin monitoring containers launched for this new version. Galaxy will wait a minimum of 10 minutes for the user’s desired count of containers to be running and healthy.
If there aren’t enough healthy containers by the deadline, Galaxy will report a failed deploy and return to maintaining and launching containers for the last healthy version. If the app was previously stopped or did not have a healthy previous version, Galaxy will automatically stop the app.
With these changes, Galaxy will now be able to track deploy completions and generate activities accordingly. This will give users more insight into the deployment process, allowing them to see exactly when a deploy has finished and whether or not it was successful.
We hope this is helpful! As always, let us know if you have any feedback about the version restore feature.
Klaire studies Computer Science at Yale and is joining us for the summer as an intern at Meteor. Be sure to follow along with her work on Twitter!
Safer app deploys on Galaxy was originally published in Meteor Blog on Medium, where people are continuing the conversation by highlighting and responding to this story.