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

# WordPress []()<img src="/api/collection/10370001/5351434856431616/page/5559872215580672/image/5242146540486656" style="width:50px;height:50px;"/>


WordPress is a PHP and MySQL-based open-source Content Management System first launched in 2003. It powers 40% of all websites, is supported by many web hosts, is easy to set-up, and offers thousands of free themes and plugins.

If you're a web developer, you've probably encountered WordPress at some point in your career. Even modern static sites can adopt WordPress as a headless CMS where it is used to edit the content that is fed into a site generator.

Even if you don't use WordPress, the concepts demonstrated in this chapter show how to execute an application in a Docker container. This is essential for development, but the technique is rarely discussed in Docker tutorials.


# WordPress requirements

To develop a WordPress-powered site, you must install:

1. A web server, typically Apache.
1. The PHP runtime and extensions, then configure the web server accordingly.
1. MySQL or MariaDB, then define a new database for WordPress use.
1. WordPress itself, plus any required themes and plugins.

Tools such as #key# XAMPP: It is the most popular PHP development environment. #key#  can ease some of that effort but, with Docker, you'll be running WordPress and developing code within minutes.

# Docker configuration plan

You will be pulling two Docker images:

1. `wordpress`
1. `mysql:5`
    
Using the latest image for `wordpress` is a good choice. It provides the stable versions of Debian Linux, Apache, PHP, and WordPress. There are more lightweight `alpine` images, but they do not match production hosting environments and may not work as expected. The containers launched from these images will be added to a `wpnet` Docker network.


## Docker volumes

Two Docker volumes will be created:

1. The `wpdata` for the MySQL database that are mounted to `/var/lib/mysql` in the MySQL container.
1. The `wpfiles` for WordPress application files that are mounted to the Apache server root directory at `/var/www/html` in the WordPress container.

>  📌 Some developers will claim that mounting the `wpfiles` volume is an anti-pattern because the WordPress container is no longer stateless. This is true, but WordPress is not a stateless application. Docker is being used to emulate a live server environment for development purposes. You are unlikely to use the same configuration in production.

Mounting the `wpfiles` volume has a number of benefits:

1. Docker start-up is faster. There's no need to copy the core WordPress files every time the container is launched.

1. The WordPress application can be updated automatically. This would happen on live installations, so replicating it during development is useful.

>  📌 If you choose not to mount a `wpfiles` volume, you can run `docker pull wordpress` every so often to download the latest application image.

It should not be necessary to inspect or modify files stored on either volume. 


## Development directory bind mount

A `wp-content` subdirectory will be created in the project directory. This contains all plugins, themes, and uploaded assets and mounts to `/var/www/html/wp-content` in the WordPress container.

WordPress developers should only ever create and modify files in the `wp-content` directory.

>  📌 There's nothing to stop you from editing core WordPress files, but the changes would disappear the moment the application is updated.

As a bonus, this makes it easier to commit `wp-content` files to Git or other repositories. It is the only WordPress folder on your host PC.


# WordPress []()<img src="/api/collection/10370001/5351434856431616/page/5559872215580672/image/5242146540486656"/>


WordPress is a PHP and MySQL-based open-source Content Management System first launched in 2003. It powers 40% of all websites, is supported by many web hosts, is easy to set-up, and offers thousands of free themes and plugins.

If you're a web developer, you've probably encountered WordPress at some point in your career. Even modern static sites can adopt WordPress as a headless CMS where it is used to edit the content that is fed into a site generator.

Even if you don't use WordPress, the concepts demonstrated in this chapter show how to execute an application in a Docker container. This is essential for development, but the technique is rarely discussed in Docker tutorials.


# WordPress requirements

To develop a WordPress-powered site, you must install:

1. A web server, typically Apache.
1. The PHP runtime and extensions, then configure the web server accordingly.
1. MySQL or MariaDB, then define a new database for WordPress use.
1. WordPress itself, plus any required themes and plugins.

Tools such as #key# XAMPP: It is the most popular PHP development environment. #key#  can ease some of that effort but, with Docker, you'll be running WordPress and developing code within minutes.

# Docker configuration plan

You will be pulling two Docker images:

1. `wordpress`
1. `mysql:5`
    
Using the latest image for `wordpress` is a good choice. It provides the stable versions of Debian Linux, Apache, PHP, and WordPress. There are more lightweight `alpine` images, but they do not match production hosting environments and may not work as expected. The containers launched from these images will be added to a `wpnet` Docker network.


## Docker volumes

Two Docker volumes will be created:

1. The `wpdata` for the MySQL database that are mounted to `/var/lib/mysql` in the MySQL container.
1. The `wpfiles` for WordPress application files that are mounted to the Apache server root directory at `/var/www/html` in the WordPress container.

>  📌 Some developers will claim that mounting the `wpfiles` volume is an anti-pattern because the WordPress container is no longer stateless. This is true, but WordPress is not a stateless application. Docker is being used to emulate a live server environment for development purposes. You are unlikely to use the same configuration in production.

Mounting the `wpfiles` volume has a number of benefits:

1. Docker start-up is faster. There's no need to copy the core WordPress files every time the container is launched.

1. The WordPress application can be updated automatically. This would happen on live installations, so replicating it during development is useful.

>  📌 If you choose not to mount a `wpfiles` volume, you can run `docker pull wordpress` every so often to download the latest application image.

It should not be necessary to inspect or modify files stored on either volume. 


## Development directory bind mount

A `wp-content` subdirectory will be created in the project directory. This contains all plugins, themes, and uploaded assets and mounts to `/var/www/html/wp-content` in the WordPress container.

WordPress developers should only ever create and modify files in the `wp-content` directory.

>  📌 There's nothing to stop you from editing core WordPress files, but the changes would disappear the moment the application is updated.

As a bonus, this makes it easier to commit `wp-content` files to Git or other repositories. It is the only WordPress folder on your host PC.


Learn the steps we will be following to use WordPress with Docker. 

Getting Started with WordPress

Learn the steps we will be following to use WordPress with Docker.

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

Getting Started with WordPress

WordPress