Set up grunt watch task to restart Hapi server on server changes? about chronicle HOT 5 CLOSED

I actually don't think we need this; I'm fine to bounce the server manually while developing. If you want to add it, that's cool with me; my first thought is to daemonize the server (node-forever? something else?), then grunt can be dead simple: either it sends a SIGTERM (which leads to graceful shutdown, which leads to restart), or it asks the daemon directly to restart itself (forever restart api-server).

How do we currently manage server processes in fxa stuff in production vs dev?

from chronicle.

@nchapman Thoughts?
I'm fine w/ not restarting Hapi on changes and using forever.
We can just use the watch command to regen the CSS.

from chronicle.

I'd love for this to work. It seems like a grunt task that manages processes would be the way to go to handle the restart. I know there are a few different ones out there but not sure if they do what we need...

from chronicle.

Sorry about the stop energy, let's just solve this for dev and handle prod when we get to prod. +1 to grunt-hapi-restarter or whatever ^_^

from chronicle.

Fixed in #59.

from chronicle.