get decking to do production deployment

[alexandrosm]

Have you put any thought into having decking deploy e.g. to amazon?

[makeusabrew]

Hey Alexandros,

Sorry; I've no idea why GitHub doesn't email me notifications of issues in my repos until I comment on them (despite telling me I'm subscribed already) - I completely missed this.

I'm not sure if decking should be involved in production deploys; mainly because I'm still not 100% sure what the idiomatic "docker way" is to deploy (and further, to reload relevant services) - as per our very brief twitter exchange on the subject a couple of weeks ago. I've got a rough implementation of my own but it feels sub optimal (and manual).

I've been flat out on other work recently so haven't had much time to think about decking and where it's heading; I'd love to develop it further but frankly it's doing just enough (for me!) at the moment, and I'm aware that more and more alternatives are popping up - be interested to see how they all manage production deploys. My gut instinct is that deployment fits in to a much wider picture (e.g. a part of a CI pipeline) but I'm open to all ideas :).

[alexandrosm]

Hi Nick,

It feels we'll need to build our own deployment script to amazon as well. Perhaps on top of CoreOS boxes, or using Serf. Yeah, it's not clear yet how exactly deployment should work, but it feels like a waste for all that config info to be inside the decking.json file and not be used.

In general the promise of Docker is to do dev/test/deploy with the same containers, so it "feels" like decking should follow along in that, but I agree it's unclear.

Have you seen other alternatives pop up beyond the ones we talked about? Would love to keep up to date.

Decking is doing well enough for us too. It's a lovely little project. And I also agree it has potential, but I guess you can't fight all the battles all the time. Resin actually does deployment of Docker containers (to embedded devices) so maybe some day we will want more complex deployments and we will give decking/deployments another look. But for the moment, it's doing its job.

If we do do some deployment work now and end up extending decking, I'll keep you updated and push anything we make and can push.

As for the idiomatic way to do deployments, maybe @petrosagg can give us some light? He's our main Docker guy and usually has insight in these things.

[makeusabrew]

Thanks for your feedback as always :).

It sounds like we've both got deployment at the 'good enough' stage for now. I do agree ideally it'd be as simple as "decking deploy [target]" and am by no means ruling it out but I think for now I want to focus on making development easier rather than deployment.

I've not seen any new concrete alternatives, no - my point above should really have said "I keep seeing fig pop up a lot" :). I need to carve out some time to really look at what's out there and evaluate how and if decking fits. A brief look at the fig docs just now when writing this reply suggests that they tread on each other's toes quite a lot, and fig already has quite a bit of traction - but interestingly makes no effort to tackle deployments.

Anyway; will keep deployments in mind, but for now will focus on making development as smooth as possible above anything else.