Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

On Thu, Jul 14, 2016, 19:07 Kai Hendry wrote: > I would love to see that 10 lines of shell you claimed, but I think you > might be underestimating the fine work that went into Dokku! > It's not so much underestimating the work in Dokku as much as leveraging what systemd

Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

Am Sat, 18 Jun 2016 13:56:03 +0200 schrieb Paul Menzel : > Dear systemd folks, > > > the setup is as follows. > > Nginx is used as the Web server, which communicates with a Ruby on > Rails application over a socket. Puma [1] is used as the application >

Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

On Thu, 14 Jul 2016, at 05:07 PM, David Timothy Strauss wrote: > Dokku would be about a 5-10 lines of shell script with services running > in > systemd. I would love to see that 10 lines of shell you claimed, but I think you might be underestimating the fine work that went into Dokku! Cheers,

Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

Dokku would be about a 5-10 lines of shell script with services running in systemd. On Wed, Jul 13, 2016, 20:41 Kai Hendry wrote: > On Sat, 18 Jun 2016, at 07:56 PM, Paul Menzel wrote: > > Is that possible by just using systemd, or is a load balancer like > > HAProxy or

Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

On Sat, 18 Jun 2016, at 07:56 PM, Paul Menzel wrote: > Is that possible by just using systemd, or is a load balancer like > HAProxy or a special NGINX configuration and service file templates > needed? I'm looking for answers too and the best switcheroo I've found so far is

Re: [systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

You either need a load balancer (less elegant) or need to make use of the Linux kernel's SO_REUSEPORT option so the new application can bind to the same port as the old one (at which point the old application should unbind the port and shut itself down).

[systemd-devel] Zero downtime restart of Web application (Nginx, Puma, JRuby)

Dear systemd folks, the setup is as follows. Nginx is used as the Web server, which communicates with a Ruby on Rails application over a socket. Puma [1] is used as the application server. Nginx and Puma are managed by systemd service files. If a new version of the application is installed,