Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker Compose Wrapper

github.com

Post reply on HN
Print view View original

21–25 of 25 posts

Re: Docker Compose Wrapper

#21

Post by zimbatm »

athyuttamre wrote: post #19
zimbatm wrote: post #17

Does any of these solutions give me back live-reload when developing web apps on OSX ? As far as I know the code is uploaded into the container and only gets replaced when the image is re-created. At which point there are issues with private git dependencies because it can't access the SSH_AUTH_SOCK.

You could host a volume into your container containing the code base. Then use any standard live reloading library to make it work.

Does it mean that I need two docker compose, one for development and one for deployment ?

Re: Docker Compose Wrapper

#22

Post by Myrmornis »

dacompton wrote: post #5

Is this a joke?

I sympathize with this question but I think this thread is actually mocking someone's well-intentioned and serious project. Personally I have at minimum a "dc" alias and I can totally see how one might start evolving that into a shell wrapper to make your common tasks less verbose. But perhaps the author envisioned it saving more typing and being more generally useful than it is, and also under-estimated the importance of the increased surface for errors and bugs that the project brings.

Re: Docker Compose Wrapper

#23

Post by markbnj »

zimbatm wrote: post #17

Does any of these solutions give me back live-reload when developing web apps on OSX ? As far as I know the code is uploaded into the container and only gets replaced when the image is re-created. At which point there are issues with private git dependencies because it can't access the SSH_AUTH_SOCK.

We run containers locally for components that our code needs, i.e. if the code needs redis, or elasticsearch or whatever it's easier to spin up a local container, keeps the dev system free of clutter, and what you're running can often be the same or very close to what is in prod. For our own code, why should it care whether it is running in a container or not? We develop locally on the host and package into a container at deployment.

Re: Docker Compose Wrapper

#25

Post by athyuttamre »

zimbatm wrote: post #21
athyuttamre wrote: post #19

Earlier quoted context omitted.

You could host a volume into your container containing the code base. Then use any standard live reloading library to make it work.

Does it mean that I need two docker compose, one for development and one for deployment ?

That's correct. I have this setup at http://github.com/athyuttamre/signmeup.
Post reply on HN