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 
In this chapter, we learned how to set up and configure a database for our
Rails app, something the vast majority of Rails apps typically need.


Let’s review what we covered:

* We started up a Postgres server in a container using Compose.

* We verified that the Postgres server was running by connecting with the
Postgres client from a separate container.

* We configured our Rails app to talk to Postgres by installing the Postgres
gem, modifying our database.yml file, and running the Rake task to create
the databases.

* We put our new database through its paces by generating a scaffold,
running migrations, and inserting, deleting, and updating records.

* We discussed why it is a good idea to decouple our database container
from data we want to persist.

* Finally, we used a named volume to store our data separately, allowing
us to manage its life cycle independently of the container.

## What to expect in the next chapter?
You have now seen how to add two services: Redis and Postgres. You should be
able to apply the same knowledge to add any other services you can think
of. In fact, we will add yet another service in the next chapter as we turn our
attention away from back-end technologies to explore how to incorporate a
modern, JavaScript front-end for your Rails app.

# Highlights 
In this chapter, we learned how to set up and configure a database for our
Rails app, something the vast majority of Rails apps typically need.


Let’s review what we covered:

* We started up a Postgres server in a container using Compose.

* We verified that the Postgres server was running by connecting with the
Postgres client from a separate container.

* We configured our Rails app to talk to Postgres by installing the Postgres
gem, modifying our database.yml file, and running the Rake task to create
the databases.

* We put our new database through its paces by generating a scaffold,
running migrations, and inserting, deleting, and updating records.

* We discussed why it is a good idea to decouple our database container
from data we want to persist.

* Finally, we used a named volume to store our data separately, allowing
us to manage its life cycle independently of the container.

# What to expect in the next chapter?
You have now seen how to add two services: Redis and Postgres. You should be
able to apply the same knowledge to add any other services you can think
of. In fact, we will add yet another service in the next chapter as we turn our
attention away from back-end technologies to explore how to incorporate a
modern, JavaScript front-end for your Rails app.

Let's revise what we have covered so far.

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