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

# Attach persistent Docker `volumes`

Mount a Docker volume (created on first use) or bind a host directory:

```yaml
  mycontainer:
    volumes:

      #Docker volume
      - type: volume
        source: rootfiles
        target: /var/www/html

      #bind host directory
      - type: bind
        source: ./myfiles
        target: /var/www/html/myfiles
```

A shorter syntax can also be used to define `<source>:<destination>`. The `<source>` is presumed to be Docker volume unless it starts with `.` or `..` relative file paths.


```yaml
  mycontainer:

    #idential to above
    volumes:
      - rootfiles:/var/www/html
      - ./myfiles:/var/www/html/myfiles
```

Docker volumes (and optional configurations) must be referenced after the `services:` definition at the bottom of `docker-compose.yml`:

```yaml
volumes:
  rootfiles:
```

> 📌 The containers you specify in your Compose file are under your `services` tag.

# Set a custom `dns` server

Define one or more DNS servers:

```yaml
  mycontainer:
    dns:
      - 1.1.1.1
      - 8.8.8.8
```


# `expose` ports

Ports can be exposed to the host using "host:container" notation:

```yaml
  mycontainer:
    expose:
      - "3000:3000"
```

Using a single container value, such as:
```yaml
  mycontainer:
    expose:
      - "3000"
```
It only exposes the port to other containers on the same Docker network and not to the host this file is running on.

More than one port can be exposed for a container and even to a different port, e.g.,
```yaml
  nodejs:
    expose:
      - "8000:3000"
      - "9229:9229"
```
The default port `3000` of the container or service `nodejs` is mapped on `8000` so now it's available on `8000`. Moreover, if you want to use devTools for Node.js debugging , you need to expose the `9229` port to `9229`, which can be done by adding another port under the `expose` property.

# Define `external_links` to other containers

Containers started outside the current `docker-compose.yml` file can be referenced assuming they are on the same Docker network:

```yaml
  mycontainer:
    external_links:
      - mysql
```


# Override the defaults 

Override the `Dockerfile` `CMD` command using shell or `exec` (array) forms:

```yaml
  mycontainer:
    command: node ./test.js
    #or [ "node", "./test.js" ]
```

Override the `Dockerfile` `ENTRYPOINT` command using shell or `exec` (array) forms:

```yaml
  mycontainer:
    entrypoint: node ./test.js
    #or [ "node", "./test.js" ]
```


# Specify a `restart` policy

Restart policies include:

* `no`: never restart the container (the default)
* `always`: always restart the container when it stops
* `on-failure`: restart the container when it fails with an exit code

```yaml
  mycontainer:
    restart: on-failure
```


# Run a `healthcheck`

Configure a check that is run periodically to check a container is alive and responding:

```yaml
  mycontainer:
    healthcheck:
      test: [ "CMD", "curl", "-f", "http://localhost:3000/test" ]
      interval: 1m00s
      timeout: 10s
      retries: 3
```


# Define a logging service

A log can be output using the `driver` of `"json-file"`, `"syslog"`, or `"none"`:

```yaml
  mycontainer:
    logging:
      driver: syslog
      options:
        syslog-address: "tcp://192.168.1.100:1234"
```
 
The option `"none"` does not display logs on the console. For both options, [**`"syslog"`**](https://docs.docker.com/config/containers/logging/syslog/) and [**`"json-file"`**](https://docs.docker.com/config/containers/logging/json-file/), the `log-driver` and `log-opts` keys need to be set with appropriate values in the `daemon.json`.

Learn more properties that you can add in the docker-compose.yml file.

More on the Docker Compose File

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 the Docker Compose File

Attach persistent Docker `volumes`

Assessment - Docker for Web Developers

More on the Docker Compose File

Attach persistent Docker volumes

Attach persistent Docker `volumes`