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

## Docker Compose 

Docker Compose is a utility for launching and managing multiple containers. It is more powerful and easier than using a series of `docker run` commands.

The configuration is usually defined in a `docker-compose.yml` (YAML) file. This lesson provides a summary of the commands that will be used most often in your Docker journey.


YML is a standard data format using new lines, tabs, colons, and dashes to indicate sections and data.

All configuration files must specify:

1. Docker Compose version compatibility.
1. The services (containers) to launch.
1. The networks (if used).
1. The volumes (if used).

```yaml
version: '3'

services:

  #container
  mycontainer:
    #...definition...


networks:

volumes:
```

The following sections describe common settings used to configure service containers for Docker Compose `v3` and above.


## Use or build `image` 

Specify a starting repository image, e.g., for the `latest` MySQL:

```yaml
  mycontainer:
    image: mysql
```

A new image can be built by specifying the relative path `context`, the name of the `dockerfile` in that location, and any associated build `args` passed to `Dockerfile` `ARG` instructions:

```yaml
  mycontainer:
    build:
      context: ./
      dockerfile: Dockerfile
      args:
        - arg1=val1
        - arg2=val2
        - arg3=val3
```


## Set the `container_name`

Set the container name. This can be used for inter-container communications across the same Docker network:

```yaml
  mycontainer:
    container_name: mycontainer
```


## Container `depends_on` another

Express a dependency between services to ensure one or more other containers have started before launching this one:

```yaml
  mycontainer:
    depends_on:
      - containerA
      - containerB
```


## Set `environment` variables

Define any number of individual environment variables:

```yaml
  mycontainer:
    environment:
      - MYVAR1=value1
      - MYVAR2=value2
      - MYVAR3=value3
```

Sets of environment variables can be defined in a **`.env` file**, e.g.

```.env
#example values
MYVAR1=value1
MYVAR2=value2
MYVAR3=value3
```

All values can be imported using `env_file:`:

```yaml
  mycontainer:
    env_file: .env
```

Multiple files can also be specified:

```yaml
  mycontainer:
    env_file:
      - ./one.env
      - ./two.env
      - ./three.env
```


## Attach to Docker `networks`

Join one or more Docker networks (created on first use):

```yaml
  mycontainer:
    networks:
      - mynetwork
```

It is also possible to set aliases (alternative hostnames) and IP addresses for the container on the network:

```yaml
  mycontainer:
    networks:
      mynetwork:
        aliases:
          - myname1
          - myname2
        ipv4_address: 172.16.238.20
        ipv6_address: 2001:3984:3989::20
```

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

```yaml
networks:
  mynetwork:
```



# Docker Compose 

Docker Compose is a utility for launching and managing multiple containers. It is more powerful and easier than using a series of `docker run` commands.

The configuration is usually defined in a `docker-compose.yml` (YAML) file. This lesson provides a summary of the commands that will be used most often in your Docker journey.


YML is a standard data format using new lines, tabs, colons, and dashes to indicate sections and data.

All configuration files must specify:

1. Docker Compose version compatibility.
1. The services (containers) to launch.
1. The networks (if used).
1. The volumes (if used).

```yaml
version: '3'

services:

  #container
  mycontainer:
    #...definition...


networks:

volumes:
```

The following sections describe common settings used to configure service containers for Docker Compose `v3` and above.


# Use or build `image` 

Specify a starting repository image, e.g., for the `latest` MySQL:

```yaml
  mycontainer:
    image: mysql
```

A new image can be built by specifying the relative path `context`, the name of the `dockerfile` in that location, and any associated build `args` passed to `Dockerfile` `ARG` instructions:

```yaml
  mycontainer:
    build:
      context: ./
      dockerfile: Dockerfile
      args:
        - arg1=val1
        - arg2=val2
        - arg3=val3
```


# Set the `container_name`

Set the container name. This can be used for inter-container communications across the same Docker network:

```yaml
  mycontainer:
    container_name: mycontainer
```


# Container `depends_on` another

Express a dependency between services to ensure one or more other containers have started before launching this one:

```yaml
  mycontainer:
    depends_on:
      - containerA
      - containerB
```


# Set `environment` variables

Define any number of individual environment variables:

```yaml
  mycontainer:
    environment:
      - MYVAR1=value1
      - MYVAR2=value2
      - MYVAR3=value3
```

Sets of environment variables can be defined in a **`.env` file**, e.g.

```.env
#example values
MYVAR1=value1
MYVAR2=value2
MYVAR3=value3
```

All values can be imported using `env_file:`:

```yaml
  mycontainer:
    env_file: .env
```

Multiple files can also be specified:

```yaml
  mycontainer:
    env_file:
      - ./one.env
      - ./two.env
      - ./three.env
```


# Attach to Docker `networks`

Join one or more Docker networks (created on first use):

```yaml
  mycontainer:
    networks:
      - mynetwork
```

It is also possible to set aliases (alternative hostnames) and IP addresses for the container on the network:

```yaml
  mycontainer:
    networks:
      mynetwork:
        aliases:
          - myname1
          - myname2
        ipv4_address: 172.16.238.20
        ipv6_address: 2001:3984:3989::20
```

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

```yaml
networks:
  mynetwork:
```



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

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

Docker Compose File

Docker Compose