AWS_ACCESS_KEY_ID

AWS_SECRET_ACCESS_KEY

AWS_DEFAULT_REGION

INTERNAL_IP

IP_PORT

SWARM_TOKEN

BUCKET

DIGITAL_OCEAN_TOKEN

Gain insights into Docker architecture, images, and containers. Learn Docker Compose, JS integration, and production readiness. Master deploying, clustering, and scaling Rails apps using Docker tools.

tarball.tar.gz

simpleJob

simpleJob2

simpleJob-copy

viewImages

dockerCompose1

challenge1

dockerComposeRedis1

dockerComposeRedis2

dockerComposeRedis3

cdToUsercode

delGitCopyUpCreate

delGitCopyUp

delGitCopyUpMigrate

webPackerCh7

RSpec-Ch8

RSpec-Ch8_2

RSpec-Ch8_2_1

RSpec-Ch8_3

runRailsUsingCustomImage

dockerCompose1-copy

RSpec-Ch8_2-copy

delGitCopyUp-copy

RSpec-Ch8_5

RSpec-Ch8_6

RSpec-Ch8_6_GUI

dockerCompose1-copy-copy

dockerComposePostgres1

webPackerCh7-copy

postgress_last_lesson

Ch12_2

postgress_2nd_last_lesson

Ch12_3

gem_1

gem_2

irritation_1

irritation_1_1

Ch12_1

webPackerCh7_2

Cloud

Cloud_DO

Cloud_1

Cloud_2_1

Cloud_2_2

Cloud_2_4

RSpec-Ch8_2_new

RSpec-Ch8_7

Cloud_1_1_bucket

dockerComposeRedis3-copy

dockerComposeRedis2-copy

Cloud_DO_2

chap4_1

chap5_3

chap5_4

challenge

simpleJob2-ForceRelaunch

simpleJob-ForceRelaunch

RSpec-Ch8_5-copy

dockerCompose1-copy-copy-copy

testing

chap4_1-copy

chap5_3-copy

chap5_4-copy

dockerComposeRedis3-copy-iwrz0a

postgress_2nd_last_lesson-copy

postgress_last_lesson-copy

webPackerCh7_2-copy

This course is your field manual for building Rails applications with Docker. 

To kick things off, you’ll start by learning the basics of Docker like architecture, images, and containers. You will then be introduced to Docker Compose and use it to build up to a multiservice application with Redis.

You will then work to get your Dockerized setup to play nice with JavaScript, using both the standard asset pipeline and webpacker, Rails’ newest approach for integrating modern JavaScript front ends.

Lastly, you will learn how to prepare your Rails app for production. Once ready, using Docker’s own tools, you will provision machines, create a cluster, deploy the app, and scale the app’s resources to meet its changing needs.

By the end of the course, you will be able to confidently use Docker in any of your further projects.

Docker for Rails Developers

## Highlights
The true power of using containers for our apps is not running a process in
an individual container (though that is useful), but rather how we are able to
wire containers together so they can talk to each other.

In this chapter, we have seen how we can add services to our application, running
in separate containers. More importantly, we have seen how Docker’s built-in
networking is used to let the services talk to each other.

Let’s review the highlights:
1. We started a Redis server in a container using `docker run`. We covered two
new options: `--name` for giving containers a human-friendly name, and `-d`
for running a container in detached mode.

2. We added a separate service in Compose for running the Redis server.

3. We verified that the Redis server was running and that we could connect
to it from a separate container by starting a new container to run `redis-cli`.

4. We discussed the networking features Docker provides and how Compose
facilitates containers talking to each other.

5. We connected our Rails app to the Redis server, making it store and
increment a value, which we then retrieved and displayed.

6. Finally, we saw that our trusty `docker-compose up` works, and will start
up both the Rails and Redis servers in one go.

## What to expect in the next chapter?

Next, we are going to take what we have learned about Compose and use it to add
a Postgres database. We will go a step further and see how to ensure our data
persists even if the container running our database was deleted.

# Highlights
The true power of using containers for our apps is not running a process in
an individual container (though that is useful), but rather how we are able to
wire containers together so they can talk to each other.

In this chapter, we have seen how we can add services to our application, running
in separate containers. More importantly, we have seen how Docker’s built-in
networking is used to let the services talk to each other.

Let’s review the highlights:
1. We started a Redis server in a container using `docker run`. We covered two
new options: `--name` for giving containers a human-friendly name, and `-d`
for running a container in detached mode.

2. We added a separate service in Compose for running the Redis server.

3. We verified that the Redis server was running and that we could connect
to it from a separate container by starting a new container to run `redis-cli`.

4. We discussed the networking features Docker provides and how Compose
facilitates containers talking to each other.

5. We connected our Rails app to the Redis server, making it store and
increment a value, which we then retrieved and displayed.

6. Finally, we saw that our trusty `docker-compose up` works, and will start
up both the Rails and Redis servers in one go.

# What to expect in the next chapter?

Next, we are going to take what we have learned about Compose and use it to add
a Postgres database. We will go a step further and see how to ensure our data
persists even if the container running our database was deleted.

Let's review what we have covered in this chapter.

Quick Recap

Introduction

A Brave New World

Running a Rails App in a Container

Fine-Tuning Our Rails Image

Describing Our App Declaratively with Docker Compose

Beyond the App: Adding Redis

Docker for Rails Developer—Exam 1

Adding a Database: Postgres

Playing Nice with JavaScript

Testing in a Dockerized Environment

Advanced Gem Management

Some Minor Irritations

Docker for Rails Developer—Exam 2

The Production Landscape

Preparing for Production

A Production-Like Playground

Deploy a Full Stack Web Application over Kubernetes

Deploying to the Cloud

Docker for Rails Developer - Exam 3

Closing Thoughts and Next Steps

APPENDIX

Quick Recap

Highlights