Show HN: DevLab – Docker Containerization for Local Development
1–10 of 19 posts
Re: Show HN: DevLab – Docker Containerization for Local Development
#2I stumbled upon Docker Compose yesterday, so please excuse my ignorance since I'm only familiar with it at a high level overview level, but Docker Compose looks very similar to DevLab.
How is DevLab different than Docker Compose?
Re: Show HN: DevLab – Docker Containerization for Local Development
#3Sorry I am pretty much a noob (specially at containerization) compared to most of the peeps here, but I can't resist asking - what is the need for this? What exactly does the author mean by "services (like databases) without needing to setup and maintain these environments manually"? Don't we just install node/mongo once ever followed by only updates?
My question is not just for this particular thing, but all "lets dev in a container" thing like python's virtual env, npm's "local hard copy of all the modules" etc.? Does it really happen that your node binary or $language interpreter/compiler gets infected/changed somehow? Or one of your crucial modules gets borked? And if it does, shouldn't we be looking at investigating why such a thing really happened in the first place instead of duplicating everything?
As for maintenance, what kind of maintenance does node (or any $compiler or $interpreter) require? Don't they just sit waiting for invocation with some code to return the output/compiler binary? The only thing I have ever needed is stuff like nvm/rvm for using multiple versions of the same package/interpreter/compiler. Can anyone educate me?
Re: Show HN: DevLab – Docker Containerization for Local Development
#4Sorry I am pretty much a noob (specially at containerization) compared to most of the peeps here, but I can't resist asking - what is the need for this? What exactly does the author mean by "services (like databases) without needing to setup and maintain these environments manually"? Don't we just install node/mongo once ever followed by only updates? My question is not just for this particular thing, but all "lets d…
I don't see much use for this project over, say, Compose, but I use dockerised services for development in my current day-job.
I'm an architect helping to move a a cluster of monoliths to a proper service-oriented setup; some of the teams work in PHP Symfony with MySQL, some work in Python 2.7 with Postgres, some in Python 3.4 with [insert hipster technology here]. We use Redis and Couchbase at various versions for different systems, Eventstore for messaging, and Elasticsearch.
That's a lot of moving parts to keep updated, but because we're deploying docker containers to production anyway, it's really simple to get up and running by just running `docker-compose up` from the root of a project.
tl;dr you're correct, unless you have to work in multiple systems that can version their infrastructure separately.
Re: Show HN: DevLab – Docker Containerization for Local Development
#5I stumbled upon Docker Compose yesterday, so please excuse my ignorance since I'm only familiar with it at a high level overview level, but Docker Compose looks very similar to DevLab. How is DevLab different than Docker Compose? https://docs.docker.com/compose/
There's a post linked from the repo that gives some of their reasoning. http://blog.fluidbyte.net/containerize-your-local-dev-in-min...
"... Between Makefiles that spun up commands and Docker-Compose we were tired of our tooling getting in our way, or creating extra tasks for us to manage. The goal of DevLab is to have a tool with a small footprint, both in application and configuration requirements, which allows for local containerization using Docker. ..."
Re: Show HN: DevLab – Docker Containerization for Local Development
#6Sorry I am pretty much a noob (specially at containerization) compared to most of the peeps here, but I can't resist asking - what is the need for this? What exactly does the author mean by "services (like databases) without needing to setup and maintain these environments manually"? Don't we just install node/mongo once ever followed by only updates? My question is not just for this particular thing, but all "lets d…
As far as I can tell, the entire point is to ensure your code is platform independent from the start instead of making subtle assumptions derived from how your development boxes are configured. Making the test environment as similar to the deployment environment as you can.
Re: Show HN: DevLab – Docker Containerization for Local Development
#7Sorry I am pretty much a noob (specially at containerization) compared to most of the peeps here, but I can't resist asking - what is the need for this? What exactly does the author mean by "services (like databases) without needing to setup and maintain these environments manually"? Don't we just install node/mongo once ever followed by only updates? My question is not just for this particular thing, but all "lets d…
As far as I can tell, the entire point is to ensure your code is platform independent from the start instead of making subtle assumptions derived from how your development boxes are configured. Making the test environment as similar to the deployment environment as you can.
Begging for an example ;)
I do understand this. And I do agree. But the more I think about it, the more I find that those arguments don't matter in real life. Code written in high level languages/platforms like node/ruby/python/etc. is meant to be platform independent since the underlying VM abstracts the low-level details. Can you give me an example of the "configuration" differences that you (can?) encounter on different systems while developing on such platforms? (Except for the obvious and documented ones which containers can't solve either).
Re: Show HN: DevLab – Docker Containerization for Local Development
#8Sorry I am pretty much a noob (specially at containerization) compared to most of the peeps here, but I can't resist asking - what is the need for this? What exactly does the author mean by "services (like databases) without needing to setup and maintain these environments manually"? Don't we just install node/mongo once ever followed by only updates? My question is not just for this particular thing, but all "lets d…
As far as I can tell, the entire point is to ensure your code is platform independent from the start instead of making subtle assumptions derived from how your development boxes are configured. Making the test environment as similar to the deployment environment as you can.
[deleted]
Re: Show HN: DevLab – Docker Containerization for Local Development
#9Earlier quoted context omitted.
As far as I can tell, the entire point is to ensure your code is platform independent from the start instead of making subtle assumptions derived from how your development boxes are configured. Making the test environment as similar to the deployment environment as you can.
Begging for an example ;) I do understand this. And I do agree. But the more I think about it, the more I find that those arguments don't matter in real life . Code written in high level languages/platforms like node/ruby/python/etc. is meant to be platform independent since the underlying VM abstracts the low-level details. Can you give me an example of the "configuration" differences that you (can?) encounter on di…
Here's an example:
A few weeks ago we had an issue where a db migration would not work on some of our developer machines (it worked fine on mine and in staging and in production). After a lot of sleuthing, we found that it was because their version of the database was slightly different because they had installed it months after I did. Furthermore, it was a real pain to roll back to the appropriate version.
A container that locked down the db version would have avoided all that.
Re: Show HN: DevLab – Docker Containerization for Local Development
#10I think it just adds complexity by introducing yet another external dependency to dev environment. Not sure it will save time on projects with custom services (not available on Docker w/required configuration) vs running traditional VM.