Posted Wed, 29 Aug 2012 09:57:32 +0200 in reply to Nick Sabalausky
On Tuesday, 28 August 2012 at 23:39:26 UTC, Nick Sabalausky wrote:
If a have a vibe.d app behind an nginx reverse proxy on a linux
and want to restart the vibe.d app, what's the standard
to do that?
Also, (I suppose this is getting more nginx/linux though, but
am I correct in my understanding that the nginx reverse proxy
not act as a watchdog and restart the vibe.d app if it exits
crashes or otherwise just simply isn't running? If it indeed
then what would be a good way to set such a thing up?
Or...should I just simply be looking up "how to setup an app as
a linux(debian) service"? Would that be the right way to go?
I am no specialist here by any means, but as there are not really
a lot of people here, probably small hints will do some good.
But, please, don't trust me :)
nginx itself won't do anything, it has no idea of what backend is
other than URL to communicate. If it has crashed, appropriate
HTTP error from nginx will happen in most default cases.
Watchdog implementation itself is up to you. I have not seen
anything related to it in vibe sources so far ( in release at
least ). It can be separate small daemon monitor application or
embedded into main application itself via some forking/signal
processing magic - those are two main approaches I have met so
far. Linux services are called daemons and, afaik, are not
restarted automagically on crash unless you implement it yourself.