Comment by blurrybird

Comment by blurrybird 3 days ago

If you commit the .devcontainer.json and associated files your whole team gets a consistent, local-feeling, environment for free.

Containerisation solved the "Works on my machine" gap between local and prod. This is just solving for the same gap between Dev 1 and Dev 2.

globular-toast 3 days ago

That's a different thing. You're talking about running the software under development in a container. I think the commenter was asking about running the dev tooling in a container, which I find a massive pain.

Reply View 1 reply

dymk 3 days ago

No, that’s what they’re talking about - running the tooling in a container. Dev tool chains are a pain in the ass to keep consistent in even small teams. Devcontainers solve that.

Reply View | 0 replies

ColonelPhantom 3 days ago

Devcontainers don't "feel" local to me, since my CLI tools are not available in them. Think ripgrep or fd, for example.

Reply View 1 reply

3eb7988a1663 3 days ago

You could include those as part of the tooling. I have been experimenting with including mise as part of the image and then layer on the extra tools within there. Put all of those steps into the build so it is automatic.

Reply View | 0 replies