Steve Melrose

Hey @anthony-o. Cheers for doing these 2 PRs. I won't properly get to look at these for a week or 2, just wanted to let you know you weren't being...

Decking differentiates between _creating_ the container (`decking create`) and _running_ the container (`decking start|stop|restart`). My understanding is if you update the runtime config for a container in decking, you need...

@satyrius @makeusabrew You'd also _have_ to recreate the container to apply new runtime arguments, e.g. volumes, ports. You can't add new ones to an already existing container (that I know...

@satyrius `docker run` creates and starts a new container _every_ time it is called, regardless whether you change arguments or not. Try it yourself using the following, ``` $ docker...

@satyrius @makeusabrew's proposal should solve your fundamental issue though. If we add a prompt and/or config switch to rebuild containers on decking config change (assuming you don't care about the...

+1

> Maybe you should track config file and prompt user to rebuild container. @satyrius That's exactly what @makeusabrew is proposing should be done. Re: documentation and workflows, I would argue...

@makeusabrew https://github.com/stephenmelrose/docker-multi-container-example could be a good candidate for this as and when I get it working properly. Trying to incorporate all the different decking elements too.

Cheers for all these. Will start taking a look when I get back next week. On Thursday, 28 August 2014, robodude666 [email protected] wrote: > If you try to pass --help...

I did some looking into promises a few months ago. I think they have a lot to offer to frond-end dev, but I feel async is a much better fit...