Adam Finn Tulinius

Hi there, Thanks for the suggestion. The request is not entirely new to us, but we've talked about experimenting with HTTP based hooks first, since the security implications are easier...

> Oh! I must have missed that when looking for "hooks" in the issue tracker :) Don't worry, the draft is really rough, and it has pretty much gathered dust...

> Maybe we need to figure out how we can cut the morph deployments into more logical `phases` and then follow the intuition one gathers from `stdenv` where there is...

Hi, This was a conscious choice we made, since our network topology doesn't allow for hosts to arbitrarily go online. However, we've recently discussed implemented an alternative approach similar to...

There's plenty of things to figure out though, like, do we actually want the remote host to end up building software, or should it fail if it can't pull everything...

Maybe we should just grab the bull by the horns, and go directly for full parallel host management; pushing, switching, &c, all in parallel.

You can't just start software up on another node blindly. Yes, Marathon will do that, but it obviously requires the software to be stateless (or at least use non-local storage...