Nobody likes repeatedly typing out lengthy command-line incantations. Today let's make our containerized work easier by customizing our environment!
The time has come to simplify starting up new shells in our development containers. Along the way, we'll learn more about the `docker-compose` `up`, `exec`, and `run` subcommands!
A comfy development environment includes niceties such as shell aliases and PATH customizations. But where should those be configured in a devcontainer? Let's find out!
A brand new containerized development environment can be pretty spartan. Over time, you'll furnish it with all the developer conveniences of home. Let's look at how that process unfolds!
A web app devcontainer isn't much good if you can't see the app. Let's talk about loopback addresses, interface binding, and port-mapping with docker-compose!
Sometimes you just need to munge some XML. And Nokogiri makes processing massive quantities of XML easy and blazingly fast. Here's a quick tutorial to get you started!
In a devcontainer, system files are ephemeral and subject to being reset any time the container is rebuilt. This can can be a problem for development package dependencies. In this …
In Dockerfiles, fewer RUN commands are better. Why? For that, we need to talk about layers. Which is exactly what we're going to do in this video!
Continuing in our quest to containerize development, in this video we begin customizing our app container in order to capture an essential tool dependency.