DEV Community: Moataz Burhan

100DaysOfCode — Day 09

Moataz Burhan — Fri, 19 Feb 2021 01:40:05 +0000

Today, I finished the following sections in "Learn How To Code: Google's Go (golang) Programming Language" course:
• Section 14: Functions
• Section 16: Pointers

End of day 9 of 100DaysOfCode.

100DaysOfCode — Day 08

Moataz Burhan — Wed, 17 Feb 2021 04:27:10 +0000

Today, I finished the following sections in "Learn How To Code: Google's Go (golang) Programming Language" course:
• Section 10: Data Grouping
• Section 12: Structs

End of day 8 of 100DaysOfCode.

100DaysOfCode — Day 07

Moataz Burhan — Tue, 16 Feb 2021 03:40:30 +0000

Today, I finished the following sections in "Learn How To Code: Google's Go (golang) Programming Language" course:

Section 4: Variables, values, & type
Section 6: Go fundamentals
Section 8: Control flow

End of day 7 of 100DaysOfCode.

100DaysOfCode — Day 06

Moataz Burhan — Mon, 15 Feb 2021 07:40:38 +0000

This is a simple tutorial demonstrates creating Golang Docker image.

Prerequisites:

Day 5 tutorial

Go App

Create a simple Go program hello-http.go:

package main

import (
    "fmt"
    "log"
    "net/http"
)

func hello(w http.ResponseWriter, r *http.Request) {
    fmt.Fprintf(w, "hello world\n")
}

func main() {
    http.HandleFunc("/", hello)
    log.Println("Starting server on 0.0.0.0:8080")
    http.ListenAndServe(":8080", nil)
}

Docker file

In the same directory, create Docker manifest file (Dockerfile):

# initializes a new build stage and sets the base image
FROM golang:1.15.1-alpine

# copy hello-http.go and add it to the filesystem of the image
ADD hello-http.go .

# compile the program
RUN go build hello-http.go

# provide the default command for the container
CMD ["/go/hello-http"]

docker build

Build an image from your Dockerfile

$ docker build . -t hello:v1.0.0

-t Name and tag the image in the 'name:tag' format

List docker images:

$ docker images

REPOSITORY                         TAG       IMAGE ID       CREATED          SIZE
hello                              v1.0.0    47f0babcdfe2   44 minutes ago   306MB

run the command:

$ docker run -dit --rm -p 8080:8080 --name hello hello:v1.0.0

docker run Run a command in a new container
-d Run container in background and print container ID
-i interactive
-t Allocate a pseudo-TTY
--rm Automatically remove the container when it exits
-p 8080:8080 Publish a container's port(s) to the host
hello:v1.0.0 Docker image to run
--name hello Assign a name to the container

Test your container

$ docker ps

docker ps List containers

You see a list like this shows a container running hello image.

CONTAINER ID   IMAGE          COMMAND            CREATED          STATUS          PORTS                    NAMES
7c3c8774134d   hello:v1.0.0   "/go/hello-http"   54 minutes ago   Up 54 minutes   0.0.0.0:8080->8080/tcp   hello

Now open your browser and go to http://localhost:8080/:

End the container

Now run the following command to end the container:

$ docker stop hello

Now list the containers

$ docker ps

CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

Note that docker container has stopped and automatically removed:

$ docker ps -a

You will see this:

CONTAINER ID   IMAGE                    COMMAND                  CREATED          STATUS                     PORTS     NAMES

End of day 6 of 100DaysOfCode.

100DaysOfCode — Day 05

Moataz Burhan — Sat, 13 Feb 2021 22:44:56 +0000

In this series, I will alternate between Go language learning, Docker concepts, and Kubernetes.

Today, I finished a basic docker tutorial. I am glad to share it with you.

Prerequisite

Install docker
- Install Docker Desktop on Mac
- Install Docker Desktop on Windows

What is a container?

Docker provides the ability to package and run an application in a loosely isolated environment called a container. A container is simply another process on your machine that has been isolated from all other processes on the host machine.

Your first container

Open a command prompt or bash window, and run the command:

$ docker run -dp 80:80 --name getting-started docker/getting-started

docker run Run a command in a new container
-d Run container in background and print container ID
-p 80:80 Publish a container's port(s) to the host
docker/getting-started Docker image to run
--name getting-started Assign a name to the container

Test your container

$ docker ps

docker ps List containers

You see a list like this shows a container running docker/getting-started image.

CONTAINER ID   IMAGE                    COMMAND                  CREATED         STATUS         PORTS                NAMES
1af9e7993c08   docker/getting-started   "nginx -g 'daemon of…"   2 minutes ago   Up 2 minutes   0.0.0.0:80->80/tcp   getting-started

Now open your browser and go to http://localhost/. Boom ... your container is up and running:

End the container

Now run the following command to end the container:

$ docker stop getting-started

Now list the containers

$ docker ps

CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

Note that docker container has stopped but it is still in your system. You can see stopped containers using the following command:

$ docker ps -a

You will see this:

CONTAINER ID   IMAGE                    COMMAND                  CREATED          STATUS                     PORTS     NAMES
1af9e7993c08   docker/getting-started   "nginx -g 'daemon of…"   6 minutes ago    Exited (0) 3 minutes ago             getting-started

To remove the container run the following command:

$ docker rm getting-started

$ docker ps -a

Remove the image

Note that docker/getting-started image was downloaded when ran docker run command. Run the following command to see image in your system:

$ docker images

REPOSITORY                    TAG       IMAGE ID       CREATED         SIZE
docker/getting-started        latest    3c156928aeec   9 months ago    24.8MB

Run the following command to remove the downloaded image:

$ docker rmi docker/getting-started

Untagged: docker/getting-started:latest
Untagged: docker/getting-started@sha256:d2c4fb0641519ea208f20ab03dc40ec2a5a53fdfbccca90bef14f870158ed577
Deleted: sha256:3c156928aeec9595a140d3e9bb67fc6849650a0a756bbb0b1690ce9a4ddca884
Deleted: sha256:bd0923edebaabd47c31d4f79115f9cbd91e6045c9b2585f02b346af81a6d3dbd
Deleted: sha256:0d6528f3488cda7f74d825579182af56cbdd7fed5bccacfa3042834b514157ac
Deleted: sha256:ec7d8444b0ff84cd1e55ec191abe60e26f996ac883d87dcb50fdca507f2af8be
Deleted: sha256:beee9f30bc1f711043e78d4a2be0668955d4b761d587d6f60c2c8dc081efb203

End of day 5 of 100DaysOfCode.

100DaysOfCode — Day 03

Moataz Burhan — Sat, 13 Feb 2021 17:43:55 +0000

In day 3, I started “Learn How To Code: Google’s Go (golang) Programming Language” course by Todd McLeod from udemy.com. Section 1 (Introduction) and Section 2.

End of day 3 of 100DaysOfCode.

100DaysOfCode — Day 02

Moataz Burhan — Sat, 13 Feb 2021 17:41:15 +0000

In day 2, I started creating a simple service and Dockerfile. See the code here https://github.com/MoatazBurhan/Grunderound. To test this code, install Docker first. Follow this document to instructions: https://docs.docker.com/get-started/.
Go Code

This code simply reads your URL path and display it in the browser.

package main

import (
   "fmt"
   "html"
   "log"
   "net/http"
)

func main() {

   http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
      fmt.Fprintf(w, "redirecting to link based on %q", html.EscapeString(r.URL.Path))
   })

   log.Fatal(http.ListenAndServe(":8081", nil))
}

Dockerfile

FROM golang:1.15.8
RUN mkdir /app
ADD . /app
WORKDIR /app
RUN go build -o main .
CMD ["/app/main"]

Deploying the Application

$ git clone https://github.com/MoatazBurhan/Grunderound
$ docker build -t go-service .
$ docker run -d -p 8080:8081 go-service

If you open up http://localhost:8080 within your browser, you should see that the application is successfully responding with redirecting to link based on "/".

End of day 2 of 100DaysOfCode.

100DaysOfCode — Day 01

Moataz Burhan — Sat, 13 Feb 2021 17:36:21 +0000

Here is my progress in my 100DaysOfCode challenge:

The plan is to build a micro-services project in GoLang using Doctor and Kubernetes. Until today I am open to suggestions about what the project is going to be. I am leaning toward building a website that allows the users to shorten their long links.

Here is what I accomplished in day one:

I picked a name for the project, Grunderound. In the book, Unbirthday by Liz Braswell, Grunderound is a place of nonsense in Wonderland. When I asked my daughter for name suggestions, she suggested this name from the book she is reading. It is a place where you look for secrets, “you grunder around looking for the right wrong”, explains the Mad Hatter in the book.

I created a repository for the project in my github space. Honestly this is my first side project that I plan to work on it seriously. The repository is almost empty currently: https://github.com/MoatazBurhan/Grunderound

I struggled a little when choosing the type of license to use. Maybe it is too early to make a decision about that. I do not know. I am always foggy in this area. I felt like I should either use MIT or GNU GPL V3. After reading about the differences in https://choosealicense.com/ I ended up choosing MIT. Please comment with your opinion if your think this is not the best choice.

I started thinking about the project layout. Note that I am new to all the technologies I am using in this project (Go, Docker, and Kubernetes). So I do not really know what I am doing. I started reading Jin Feng’s suggestions in Go Microservice with Clean Architecture: Application Layout. I will continue on this tomorrow.

End of day 1 of 100DaysOfCode.

100DaysOfCode challenge

Moataz Burhan — Sat, 13 Feb 2021 17:31:29 +0000

I’m publicly committing to the 100DaysOfCode Challenge starting today! I will be building an implementation of shortened URL in GO. A micro-services project using Docker and Kubernetes: https://github.com/MoatazBurhan/Grunderound

Learn More and Join me! hey @ka11away

https://100DaysOfCode.com #100DaysOfCode

I will use this space to publish my progress everyday.