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

## `localhost` domain alternative
If you specify the exposed port as `8001` for WordPress, then it will be launched from the `localhost` domain on port `8001`. However, that can be impractical when you're developing several sites:

* Your browser may cache files from one site and show them on another.
* WordPress stores the domain in its database, so you might want to use something similar to the production name.

Optionally, you can configure other domains for development use in your `hosts` file. This is located at:

* `/etc/hosts` on Linux and macOS
* `C:\Windows\System32\drivers\etc\hosts` on Windows (administrator permissions are required to view and edit it).

Add a line to the bottom of the `hosts` file, e.g.,

```txt
127.0.0.1    dev.wordpress
```
And save it. The changes are applied immediately on Linux and macOS, but Windows users must run `nbtstat -R` or reboot.

From then on, you can use [http://dev.wordpress](#) rather than [http://localhost](#). Both resolve to the loopback address `127.0.0.1`.

The `hosts` file allows you to override DNS (Domain Name System) information. You can block ad networks and spyware by putting `0.0.0.0` in front of the name of the domain you want to block.

This file can also help when you want to test a development server that you are about to deploy. Add the machine's IP address and domain name in the `hosts` file. Now when you access it using its domain name, you will be taken to that server.


## Administration panel permissions

WordPress allows you to install, edit, and delete theme and plugin files directly from its administration panels. This is permitted on Windows, but Linux and macOS users must grant access rights to the project's `wp-content` folder by entering the following command on the host:

```bash
chmod 777 ./wp-content -R
```
This command grants every user the right to access, read, write, and execute the files in the `wp-content` folder. The argument `-R` recursively applies this to every file in that directory.

If you do not grant access rights:

* WordPress and users testing your site will not be able to change code in the `wp-content` directory (that could be a good thing).
* You must manually download [plugins](https://wordpress.org/plugins/) and [themes](https://wordpress.org/themes/) from [WordPress.org](https://wordpress.org/) or elsewhere. Extract the ZIP file to an appropriate `wp-content` subdirectory before enabling it in the administration panels.
* Some plugins, such as caching systems, will not operate.




# `localhost` domain alternative
If you specify the exposed port as `8001` for WordPress, then it will be launched from the `localhost` domain on port `8001`. However, that can be impractical when you're developing several sites:

* Your browser may cache files from one site and show them on another.
* WordPress stores the domain in its database, so you might want to use something similar to the production name.

Optionally, you can configure other domains for development use in your `hosts` file. This is located at:

* `/etc/hosts` on Linux and macOS
* `C:\Windows\System32\drivers\etc\hosts` on Windows (administrator permissions are required to view and edit it).

Add a line to the bottom of the `hosts` file, e.g.,

```txt
127.0.0.1    dev.wordpress
```
And save it. The changes are applied immediately on Linux and macOS, but Windows users must run `nbtstat -R` or reboot.

From then on, you can use [http://dev.wordpress](#) rather than [http://localhost](#). Both resolve to the loopback address `127.0.0.1`.

The `hosts` file allows you to override DNS (Domain Name System) information. You can block ad networks and spyware by putting `0.0.0.0` in front of the name of the domain you want to block.

This file can also help when you want to test a development server that you are about to deploy. Add the machine's IP address and domain name in the `hosts` file. Now when you access it using its domain name, you will be taken to that server.


# Administration panel permissions

WordPress allows you to install, edit, and delete theme and plugin files directly from its administration panels. This is permitted on Windows, but Linux and macOS users must grant access rights to the project's `wp-content` folder by entering the following command on the host:

```bash
chmod 777 ./wp-content -R
```
This command grants every user the right to access, read, write, and execute the files in the `wp-content` folder. The argument `-R` recursively applies this to every file in that directory.

If you do not grant access rights:

* WordPress and users testing your site will not be able to change code in the `wp-content` directory (that could be a good thing).
* You must manually download [plugins](https://wordpress.org/plugins/) and [themes](https://wordpress.org/themes/) from [WordPress.org](https://wordpress.org/) or elsewhere. Extract the ZIP file to an appropriate `wp-content` subdirectory before enabling it in the administration panels.
* Some plugins, such as caching systems, will not operate.




Learn what more you can explore if you try WordPress locally.

More on WordPress

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

More on WordPress

`localhost` domain alternative

Assessment - Docker for Web Developers

More on WordPress

localhost domain alternative

`localhost` domain alternative