From 7afa9e0815f712c1293b325c6262c6158ea63009 Mon Sep 17 00:00:00 2001 From: David Heinemeier Hansson Date: Sat, 18 Feb 2023 16:23:46 +0100 Subject: [PATCH] Mention healthcheck as part of steps instead --- README.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index d5c2b9c9..199e410f 100644 --- a/README.md +++ b/README.md @@ -22,8 +22,6 @@ env: Then edit your `.env` file to add your registry password as `MRSK_REGISTRY_PASSWORD` (and your `RAILS_MASTER_KEY` for production with a Rails app). -Finally, you have to ensure your application can answer `200 OK` to a `GET /up` request (or configure an alternative health path). That's how the zero-downtime deploy process knows that your new version is ready to serve traffic. - Now you're ready to deploy to the servers: ``` @@ -39,9 +37,10 @@ This will: 5. Push the image to the registry. 6. Pull the image from the registry on the servers. 7. Ensure Traefik is running and accepting traffic on port 80. -8. Stop any containers running a previous versions of the app. -9. Start a new container with the version of the app that matches the current git version hash. -10. Prune unused images and stopped containers to ensure servers don't fill up. +8. Ensure your app responds with `200 OK` to `GET /up`. +9. Stop any containers running a previous versions of the app. +10. Start a new container with the version of the app that matches the current git version hash. +11. Prune unused images and stopped containers to ensure servers don't fill up. Voila! All the servers are now serving the app on port 80. If you're just running a single server, you're ready to go. If you're running multiple servers, you need to put a load balancer in front of them.