Think inside the box. Developing inside a container to avoid conflicts, improve security and speed up on-boarding

By Michael Jolley

Elevator Pitch

“It works on my machine.” In this presentation, we learn how to use Visual Studio Code Remote Development to standardize the dev environments for each project, remove the need to install third party software like Python or Node, and ensure that when it runs on “my” machine, it runs in production.

Description

As developers, our most famous response, “it works on my machine,” doesn’t cut it anymore. We need a way to develop each project in environments that are as identical to production as possible. In this presentation, we learn how to use Visual Studio Code Remote Development to standardize the development environments for each project, remove the need to install third party software like Python or Node, and ensure that when it runs on “my” machine, it runs in production.

Notes

Topics covered:

  • Pros & cons of developing within a container from VS Code
  • Opening existing projects in a container
  • Attaching to running containers
  • Port forwarding options
  • Accessing the container terminal from VS Code
  • Debugging code running in a container