## Compose sample application ### ASP.NET server with an Nginx proxy and a MySQL database Project structure: ``` . ├── backend │   ├── Dockerfile │   ├── aspnet.csproj │   └── Program.cs ├── db │   └── password.txt ├── docker-compose.yaml ├── proxy │   ├── conf │   └── Dockerfile └── README.md ``` [_docker-compose.yaml_](docker-compose.yaml) ``` services: backend: build: backend ... db: image: mysql:8.0.19 ... proxy: build: proxy ports: - 80:80 ... ``` The compose file defines an application with three services `proxy`, `backend` and `db`. When deploying the application, docker-compose maps port 80 of the proxy service container to port 80 of the host as specified in the file. Make sure port 80 on the host is not already being in use. ## Deploy with docker-compose ``` $ docker-compose up -d ``` ## Expected result Listing containers must show three containers running and the port mapping as below: ``` $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8906b14c5ad1 nginx-aspnet-mysql_proxy "nginx -g 'daemon of…" 2 minutes ago Up 2 minutes 0.0.0.0:80->80/tcp nginx-aspnet-mysql l_proxy_1 13e0e0a7715a nginx-aspnet-mysql_backend "/server" 2 minutes ago Up 2 minutes 8000/tcp nginx-aspnet-mysq l_backend_1 ca8c5975d205 mysql:5.7 "docker-entrypoint.s…" 2 minutes ago Up 2 minutes 3306/tcp, 33060/tcp nginx-aspnet-mysql l_db_1 ``` After the application starts, navigate to `http://localhost:80` in your web browser or run: ``` $ curl localhost:80 ["Blog post #0","Blog post #1","Blog post #2","Blog post #3","Blog post #4"] ``` Stop and remove the containers ``` $ docker-compose down ```