Reply to post:

Docker introduces developer environments in containers


> Total BS. Switching branch is a simple git operation and your tooling should handle the dependencies. I work on a lot of different project types... web, mobile, serverless, command line, etc. I set up my environment once and I'm done so I struggle to see the point of something like this.

So if your stack consists of proxy, application, datastore, search, job server and an event streamer/bus, and your ops team updates configuration anywhere in that pipeline, your tooling will handle any/all cases?

I think the point of this tool is to streamline and encapsulate the orchestration of an entire stack against something like k8s, so the devs don't have to think about it; just a guess, so correct me if i am wrong and sorry or the rhetorical bitchiness above.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

Biting the hand that feeds IT © 1998–2022