

This helps configure the VS Code environment, for example naming the environment. For example, you could base it on node:latest and add some extra packages if you wish. The definition is whatever you need it to be, with no special requirements for VS Code. If you’re new to Docker, you can read this, or the official documentation.

With just a few files, you can configure VS Code to have a consistent environment (including plugins) for all your team. If you’re in a team that works on multiple projects, keeping everything in sync will become a burden.ĭev Containers provide the perfect solution in VS Code. We want that burden to be taken away from them, or at least shared amongst the team. We don’t want engineers wasting time on maintaining language versions, or OS libraries, or anything that slows them down. Ideally this would be closely aligned to the environment you ultimately ship to, i.e. Engineers need to work in a consistent environment for their project. I am not a fan of the “Works on my machine” mentality. This post outlines how to setup a VS Code Dev Container, so your team can share the same development environment.

OK, maybe that wasn’t my first reaction 😅.

My first reaction was to get a working environment that I could use, and then share with my team. I am the only engineer in my team now who knows PHP. Obviously a lot has changed in 4 years (both in the language, setup, and the team I work in). It was written in PHP, a language I’d barely written in the last 3 years. The deadline was tight, and we had a week to complete it. Last week my team was tasked with picking up a project that I had last worked on 4 years ago.
