Conversation
There was a problem hiding this comment.
Did you mean to change this to 0.0.0.0? I'd rather not have these notebooks be public by default.
There was a problem hiding this comment.
I guess I didn't. Without this, I can't run the server under boot2docker. The containers never become accessible.
There was a problem hiding this comment.
Hmmm, maybe we make this configurable, leave the default as 127.0.0.1.
|
LOL - upon seeing this Olivier said "great, I am glad you implemented it this way, that was I can write some javascipt that keeps it alive..." |
There was a problem hiding this comment.
Something we could do in the future here is also dump the logs of the container before we obliterate it.
use the proxy's inactive_since REST API
and kill the proxy if the server exits
also changes default cull timeout to 1 hr
|
now configurable, with a default of one hour. |
|
This PR closes all containers created by this process. Upon a hot reload of tornado (change of the python script), does it keep the old values? If we restart the process through other means, I take it we'll have to do maintenance to clean out old containers. |
like it says on the tin.
every hour (configurable), it checks for idle containers and brings them down, removing the proxy route.