About SO_REUSEPORT: https://metacpan.org/pod/Mojo::Server::Daemon#reuse http://mojolicio.us/perldoc/Mojolicious/Guides/Cookbook#Zero-downtime-software-upgrades
On Monday, April 6, 2015 at 8:12:31 PM UTC+2, Nathan Waddell wrote: > > Yeah, I concur that the standard hot swap model probably isn't compatible > with a foreground process. Thanks for the input. I know I'm not deploying > in the 'typical' configuration, and unfortunately that's not really up to > me. However, I'd like to use this opportunity to try to give back somehow - > even if that's just putting my questions and experiences here for others > who might wind up in the same situation. > > I could see the possibility of writing an adapter for the service manager > that would handle registering the new server's pid with the service manager > and perhaps using the SO_REUSEPORT socket option to remain bound to the > same port. I could be mistaken, but I don't think that being run as a > foreground process == no hotswapping. I think it moves more into the idea > of "managed" hotswapping. > > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious+unsubscr...@googlegroups.com. To post to this group, send email to mojolicious@googlegroups.com. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
