Quick Recap

Highlights

Who knew that gem management could be such a hot topic? With this new option at your disposal, you should feel ready for anything. Let’s take a look at what we have covered in this chapter:

1. We discussed the downsides to our previous approach to managing gems: any gem changes required all gems to be reinstalled from scratch.

2. We explored a way to speed up gem changes that involved creating a volume for caching our gems. By mounting the volume into our container (and setting BUNDLE_PATH), we could manage our gems manually and benefit from faster builds.

Hopefully, you are also starting to appreciate the meta point here: how problems with our Docker setup can be identified, thought through, and eventually solved in creative ways. The more you use Docker and understand how it works, the more you will start spotting opportunities for improvements yourself.

Good as it is, Compose is not without failings.

What to expect in the next chapter?

In the spirit of full disclosure, we are going to explore a couple of common pain points you may encounter when using Compose. In the following chapter, you will learn about these irritations and what we can do to minimize their impact.