Brian Morton
Brian Morton
Thinking about this more, I think keeping this as two different endpoints would be ideal. You could kick off the deploy and make a second request to follow the progress...
I haven't been running deployster through vulcand yet, but it's a good idea.
I'll bounce a couple questions back at you: How does deployster/deployster-sidekick get enough information to setup the frontend? It'd have to know the routing logic you want to use for...
:+1: to having deployster only handle registration/de-registration. I've thought about building some kind of UI or something for vulcand independently of this project for making setting that stuff up easy....
That unit file is mostly copied from the "Run a simple sidekick" section of [this CoreOS guide](https://coreos.com/docs/launching-containers/launching/launching-containers-fleet/).
No worries! I like this. I think keeping it in a docker container is a good idea too. Are you interested in doing either side of this work? I have...
It looks like you've got a good chunk of this whole thing handled, so I'll let you handle this first and then we can figure out if we want to...
I like this idea and I think for deployster to truly be usable, many of these things will need to be supported. Just a couple thoughts: - The biggest differentiator...
If we do this within the process itself, that could work. Is that what you had in mind? The pro is that we'd keep our list of dependencies low. The...