I've never used Packer - not 100% sure what problem it solves. w.r.t. Docker - I know that some people are using it to contain Postgres or Redis. I'm not using it that way. I'm happy with how apps are currently provisioned and deployed using Ansible and Cap3.
But - my app has webhooks, and we're letting 3rd parties write services that are invoked by the webhooks. The services are stored in docker containers. This makes the services language independent, easy to distribute, and safe. Communication between docker services is done by TCP, the container lets you provision and listen on a port. The TCP comms can be some custom protocol, HTTP, or a messaging layer like zeromq. The docker addressing we've done has been pretty much hard-coded. It looks like the docker people are working on adding a service-discovery layer. We're counting on that! On Thursday, November 7, 2013 11:13:21 AM UTC-8, Kir S. wrote: > > Lee, Andy, do you have any established workflow with Docker or Packer? > Some developers make a new image for each deploy revision, some run git > pull in the production container. > I also didn’t get still, how the services can communicate with each other > inside Docker? Under services I mean rails app, postgres and redis. > > On Thursday, November 7, 2013 8:25:15 PM UTC+4, Andy L wrote: >> >> >>> I do think it's interesting that although Ansible could do what Cap is >>> doing, you aren't using it for that. And that with Python in the stack you >>> are using Capistrano over Fabric. >>> >>> >> For us using two different tools makes sense. For provisioning, I don't >> want developers doing ad-hoc stuff, so the limitations of Ansible, the >> non-scriptable YAML manifests, the standalone toolchain is a bonus. For >> app deployment, we want more control, using familiar tools Ruby/Rake etc. >> Cap has also figured out rails deployment - bundler/assets/etc. It is also >> helpful that the community focus of Ansible and Capistrano is distinct. >> >> I guess I'm saying what you already know. :-p >> > -- -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en --- You received this message because you are subscribed to the Google Groups "Capistrano" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
