|
16
|
1
|
|
|
2 # Table of Contents
|
|
|
3
|
|
|
4 1. [Usage](#org6a0ed95)
|
|
|
5 2. [What could you do next?](#orgb192b61)
|
|
|
6
|
|
|
7
|
|
|
8 <a id="org6a0ed95"></a>
|
|
|
9
|
|
|
10 # Usage
|
|
|
11
|
|
|
12 Make sure you have Docker installed
|
|
|
13
|
|
|
14 ./run.sh
|
|
|
15
|
|
|
16 Using docker compose, this script build the Docker images (server and client), create a user-defined bridge network, and run both containers. After that, you will be provided with the client shell to send messages to the server.
|
|
|
17
|
|
|
18 To close the connection type `exit` from the client shell and press `ENTER`.
|
|
|
19
|
|
|
20 Some things that I find interested:
|
|
|
21
|
|
|
22 - Run `docker logs --follow hey-server-1` in another terminal. Doing that you can see the messages arriving at the server.
|
|
|
23 - If you have Wireshark installed you can use it to sniff the packets sent in the Docker network. This is good to understand TCP.
|
|
|
24
|
|
|
25
|
|
|
26 <a id="orgb192b61"></a>
|
|
|
27
|
|
|
28 # What could you do next?
|
|
|
29
|
|
|
30 A good exercise will be to implement logic for some commands in the server. For example, you could program the server to send to the client the current date every time the server receives the command `date`.
|
|
|
31
|
