Quick Recap

Highlights

Ahh, that’s better; we can hang up our apron. Our preparation—or mise en place—is complete. The following are the highlights:

1. We configured our app to run in production, with the necessary environment variables set.

2. We created an enhanced production image that precompiled our assets.

3. We discussed the need for making our images available on different machines, and learned how Docker Registries facilitate this.

4. We saw the naming convention we need to refer to a specific version of an image unambiguously:

   [<registry hostname>[:port]/]<username>/<image name>[:<tag>]
   

5. You created a Docker Hub account (if you didn’t already have one).

6. We built our production image and pushed it to a public Docker Registry (Docker Hub), making it available for download on our production machines.

With our production config in place and image pushed to Docker Hub, we are ready to start deploying our app to production-like environments.