Zero down-time deploy and server checks #562
Conversation
This change makes Dokku start up the new container, run a set of checks against it, and only switch traffic over to the new containers if all checks complete successfully. No requests are dropped during the switch over. To specify checks, add a CHECKS file to the root of your project directory. This is a text file with one line per check. Empty lines and lines starting with # are ignored. A check is a relative URL and may be followed by expected content from the page, for example: /about Our Amazing Team Even if you don’t use any checks, this change will prevent downtime during switching from old to new container. See: https://labnotes.org/zero-downtime-deploy-with-dokku/
|
👍 |
|
Huh, pretty cool. |
|
Looking good, simple and pragmatic! What's stopping this from getting merged? |
|
👌 |
|
👍 |
1 similar comment
|
👍 |
|
+1 |
|
Thia works great just what i Needed for gradle/Java to work without downtime. Thanks |
|
👍 |
|
Ping @asm89 @rhy-jot |
|
(thumbsup) |
|
I've been using this successfully Works great. Would love to see this merged in. |
|
+1 |
|
@rhy-jot @progrium can we get this reviewed and, hopefully, merged? |
|
👍 |
|
Any idea when it will end up in the main branch? |
|
I've ended up using dokku-alt - seems to be getting a bit more attention https://github.com/dokku-alt/dokku-alt On Tue, Aug 12, 2014 at 1:41 AM, jlachowski notifications@github.com
Alex MacCaw +1.415.624.7665 |
|
@maccman thanks for the link |
|
Any chance this will get reviewed or rejected any time soon? Until then, dokku-alt seems interesting, at first. |
|
Oh man, okay, I'm going to have to come back and push some of these through. |
Zero down-time deploy and server checks
|
❤️ |
|
👏 thank you sir @progrium |
|
is this available on digital ocean? ie. |
|
Nope, 0.2.3 was released in April (as seen in the tags) and this was merged in August. |
|
This was released. |
This change makes Dokku start up the new container, run a set of checks
against it, and only switch traffic over to the new containers if all
checks complete successfully. No requests are dropped during the switch
over.
To specify checks, add a
CHECKSfile to the root of your projectdirectory. This is a text file with one line per check. Empty lines and
lines starting with # are ignored.
A check is a relative URL and may be followed by expected content from
the page, for example:
Even if you don’t use any checks, this change will prevent downtime
during switching from old to new container.
Thanks to https://github.com/michaelshobbs for simplifying the process by grabbing checks from the project directory.
See: https://labnotes.org/zero-downtime-deploy-with-dokku/