[Chore]: Add README

0x0D-web_stack_debugging_0/README.md

@@ -1 +1,68 @@
-## Web stack debugging 
+![img](https://assets.imaginablefutures.com/media/images/ALX_Logo.max-200x150.png)
+  > Web stack debugging 
+
+![who-loves-debugging](https://s3.amazonaws.com/intranet-projects-files/holbertonschool-sysadmin_devops/265/uWLzjc8.jpg)
+
+## Background context
+The Webstack debugging series will train you in the art of debugging. Computers and software rarely work the way we want (that’s the “fun” part of the job!).
+
+Being able to debug a webstack is essential for a Full-Stack Software Engineer, and it takes practice to be a master of it.
+
+In this debugging series, broken/bugged webstacks will be given to you, the final goal is to come up with a Bash script that once executed, will bring the webstack to a working state. But before writing this Bash script, you should figure out what is going on and fix it manually.
+
+Let’s start with a very simple example. My server must: 
+
+- have a copy of the ```/etc/passwd``` file in ```/tmp```
+- have a file named ```/tmp/isworking``` containing the string OK
+
+Let’s pretend that without these 2 elements, my web application cannot work.
+
+Let’s go through this example and fix the server.
+
+```
+itsfoss@vagrant:~$ docker run -d -ti ubuntu:14.04
+Unable to find image 'ubuntu:14.04' locally
+14.04: Pulling from library/ubuntu
+34667c7e4631: Already exists
+d18d76a881a4: Already exists
+119c7358fbfc: Already exists
+2aaf13f3eff0: Already exists
+Digest: sha256:58d0da8bc2f434983c6ca4713b08be00ff5586eb5cdff47bcde4b2e88fd40f88
+Status: Downloaded newer image for ubuntu:14.04
+76f44c0da25e1fdf6bcd4fbc49f4d7b658aba89684080ea5d6e8a0d832be9ff9
+itsfoss@vagrant:~$ docker ps
+CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
+76f44c0da25e        ubuntu:14.04        "/bin/bash"         13 seconds ago      Up 12 seconds                           infallible_bhabha
+itsfoss@vagrant:~$ docker exec -ti 76f44c0da25e /bin/bash
+root@76f44c0da25e:/# ls /tmp/
+root@76f44c0da25e:/# cp /etc/passwd /tmp/
+root@76f44c0da25e:/# echo OK > /tmp/isworking
+root@76f44c0da25e:/# ls /tmp/
+isworking  passwd
+root@76f44c0da25e:/#
+itsfoss@vagrant:~$
+```
+
+Then my answer file would contain 
+```
+itsfoss@ubuntu:~$ cat answerfile
+#!/usr/bin/env bash
+# Fix my server with these magic 2 lines
+cp /etc/passwd /tmp/
+echo OK > /tmp/isworking
+itsfoss@ubuntu:~$
+```
+Note that as you cannot use interactive software such as ```emacs``` or ```vi``` in your Bash script, everything needs to be done from the command line (including file edition).
+
+## Installing docker
+For this project you will be given a container which you can use to solve the task. If you would like to have Docker so that you can experiment with it and/or solve this problem locally, you can install it on your machine, your Ubuntu 14.04 VM, or your Ubuntu 16.04 VM if you upgraded.
+
+- [MacOS](https://docs.docker.com/desktop/install/mac-install/)
+- [Windows](https://docs.docker.com/desktop/install/windows-install/)
+- [Ubuntu 14.04](https://www.liquidweb.com/kb/how-to-install-docker-on-ubuntu-14-04-lts/)(Note that Docker for Ubuntu 14 is deprecated and you will have to make some adjustments to the instructions when installing)
+- [Ubuntu 16.04](https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-16-04)
+
+## Resource 
+### man or help
+- curl 
+- docker