Really Using Visual Studio Development Containers

1

HTTPie

This is the simplest scenario where we just plop a development container definition into our project and Code spins it up. But what if we needed to add some of our own tools? Perhaps our team relies heavily on Flyway for database migrations and HTTPie for testing our RESTful endpoints. This can easily be done by writing our own Docker image definition. First remove the "image" attribute from your devcontainer.json file and replace it with a "dockerFile" attribute that points to our soon-to-be-created Dockerfile.

#CLI #Command Line Tools #Curl 46 social mentions

2

Flyway

This is the simplest scenario where we just plop a development container definition into our project and Code spins it up. But what if we needed to add some of our own tools? Perhaps our team relies heavily on Flyway for database migrations and HTTPie for testing our RESTful endpoints. This can easily be done by writing our own Docker image definition. First remove the "image" attribute from your devcontainer.json file and replace it with a "dockerFile" attribute that points to our soon-to-be-created Dockerfile.

#MySQL Tools #Development #Online Services 58 social mentions

3

Visual Studio Code

At this point, like all of us, you wonder "is there a better way?" There's always a better way and the idea of using Docker to support your development environment is nothing new. The interesting bit is that Visual Studio Code is bringing some tooling to the table that makes this much easier.

#Text Editors #IDE #Software Development 1017 social mentions