This https://github.com/jpillora/overseer
may do what you need or at least give you an idea of what you can do. The way oveerseer works is, you start your app, when you send a particular kill signal, it keeps the running app running and it spawns a duplicate, it passes new http requests to the new process while still serving current requests with the old binary, once the connections to the old binary are done (or timeout), the old process dies. Regards, Diego On Sunday, September 3, 2017 at 5:35:30 PM UTC-4, emarti...@gmail.com wrote: > > Hello, > > I am looking for the 'best' way to launch and monitor several go > processes. Doing it with just 1 is easy enough, using monit or systemctl > should do the trick, however since our app takes a while to start, we want > to keep a few proceses running at all times so we don't have downtime > everytime the app needs to be restarted. Similar to how apache sub proceses > works. One of the solutions we are thinking is to create a go launcher that > will spawn sub processes and using systemctl on that launcher. > > Any recommendations? What do you guys use? > > Thanks! > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
