username

password

Gain insights into Docker's architecture, images, and containers. Learn about running databases, using WordPress and Node.js with Docker, and confidently apply Docker in web development projects.

tarballverified.tar.gz

sqlJob

wordpressJob

nodejsJob

quizJob

ch4_2

ch4_3

ch4_3_2

ch4_3_3

ch4_4

ch4_challenge

ch5_3_nginx

drupal

cdToUsercode

ch6_4

ch6_4_2

ch_6_5

ch_6_5_2

ch_6_6

ch_7_2

ch_7_3

debugging_gui

cdToUsercode_gui

ch_5_3

adminerWordPress

executeJob

ch10_3

ch_5_4_drupal

PROJECT

PROJECT_prod

PROJECT_DEV

ch_5_3-copy

debugging_gui-copy

ch_5_3-copy-vgib6g

ch_5_4_drupal-copy

PROJECT-copy

PROJECT_DEV-copy

ch_6_5_2-copy

Docker is the most useful web development tool you’re not using. This course is your guide for building all kinds of web applications with Docker.

You will be introduced to Docker basics including its architecture, images, and containers. Then you'll run various databases and view them via CLI or Adminer. Next, you will learn how easy it is to use WordPress with Docker. After that is the Node.js app and its live editing and debugging with Chrome's devTools. Finally, you will make your own project to practice your Docker knowledge.

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

Docker for Web Developers

## What to expect in this chapter?

The pre-built Docker images such as MySQL, Adminer, and WordPress are useful, but you'll eventually want to run your own programs in a container.

In this chapter, you'll be creating a Node.js "Hello World" application that is built into a Docker image and launched as a container. By default, the image will be ready for deployment on a production server, but Docker Compose will be used to override some settings to create a development and debugging environment. You'll be able to edit source code on your host, but the files will be executed within a continually running container. This has several benefits:

* Docker will manage dependencies for you -- there's no need to install and maintain language runtimes.
* The process is a little different from developing locally.
* The container is isolated. Your application cannot do anything like crash the host PC or wipe files.
* You can distribute your application to other developers or testers. It will run identically on any other device with zero configuration.


## Container-based application development

Docker simplifies web development. Any web application you create can be run in a single container.

However, if you want to deploy similar containers to live production servers, the application should be stateless. Any number of instances can be started and any can react to requests. In practical terms, your application should not store essential state data in local files or memory.

>  For example, an application stores login credentials in memory when a user logs in. A single container is used during development so everything works as expected.
>
> The application is then deployed to a production server and run in two containers that receive requests via a load balancer. A user accesses the system and has their login processed by container1. Their next request is served by container2. It does not have the user's state and redirects to the login page.



# What to expect in this chapter?

The pre-built Docker images such as MySQL, Adminer, and WordPress are useful, but you'll eventually want to run your own programs in a container.

In this chapter, you'll be creating a Node.js "Hello World" application that is built into a Docker image and launched as a container. By default, the image will be ready for deployment on a production server, but Docker Compose will be used to override some settings to create a development and debugging environment. You'll be able to edit source code on your host, but the files will be executed within a continually running container. This has several benefits:

* Docker will manage dependencies for you -- there's no need to install and maintain language runtimes.
* The process is a little different from developing locally.
* The container is isolated. Your application cannot do anything like crash the host PC or wipe files.
* You can distribute your application to other developers or testers. It will run identically on any other device with zero configuration.


# Container-based application development

Docker simplifies web development. Any web application you create can be run in a single container.

However, if you want to deploy similar containers to live production servers, the application should be stateless. Any number of instances can be started and any can react to requests. In practical terms, your application should not store essential state data in local files or memory.

>  For example, an application stores login credentials in memory when a user logs in. A single container is used during development so everything works as expected.
>
> The application is then deployed to a production server and run in two containers that receive requests via a load balancer. A user accesses the system and has their login processed by container1. Their next request is served by container2. It does not have the user's state and redirects to the login page.



Learn what container-based application development is.

Stepping into App Development

Why Docker for Web Developers?

Introduction

What is Docker?

Launch a MySQL Database with Docker

WordPress Development with Docker

Application Development with Docker

Push Your Docker Image to a Repository

Docker Orchestration on Production Servers

Docker CLI Commands

Dockerfile and Docker Compose

Project: Never-Ending Quizzery

Assessment - Docker for Web Developers

APPENDIX

Stepping into App Development

What to expect in this chapter?