Adding node on start, and not on hook

[subnetmarco]

This change adds the node on start, and not on hook. It provides a better way of dealing with the nodes table, and also allows nginx to be the last service to start up.

Also tries to address issue #1004.

[subnetmarco]

I think you will like this @mars - although terminating the foreground process will not terminate all the other services (like < v0.6.x was erroneously doing). As opposed to #1007 which terminates the other process when the main one is terminated (but not really an issue if terminating means shutting down the whole Docker container).

Basically this would allow the older behavior to work again. Still, not a replacement of supervisor (or similar solutions).

[mars]

this would allow the older behavior to work again.

The old behavior being "run kong w/ Nginx daemon off" to get stderr/stdout streams?

It's an improvement indeed, as log spelunking on Docker containers makes ops difficult. Stream all the logs!

[subnetmarco]

Yep. Although, like the old behavior, if you terminate nginx it will not terminate the other services, but it doesn't matter if terminating nginx means shutting down the entire container.