How to deploy an upgrade (build with rebar3)

[Fred Hebert]

On Mon, Feb 24, 2020 at 9:28 AM Loïc Hoguin <essen@REDACTED> wrote:

>
> Ranch 2.0 onward fully supports upgrades and comes with an appup you can
> use directly:
> https://github.com/ninenines/ranch/blob/master/src/ranch.appup
>
> We've recently added a test suite:
> https://github.com/ninenines/ranch/blob/master/test/upgrade_SUITE.erl
>
> The workaround described is more or less what Ranch 2.0 does during the
> upgrade: stop all the acceptor processes, perform the upgrade, resume
> the acceptor processes. The listening socket(s) stays open, so no new
> connections should be rejected as long as the backlog is large enough,
> and existing connections stay alive as well.
>
>
Good to hear, hadn't seen that one go through. That can cause a bit of a
pause and still may be a bit surprising in the shell, but that at least
makes things production safe for relup, which is definitely an improvement.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20200224/96ade012/attachment.htm>