Local-Monuments-Website

This project is containerized web application entirely created from scratch. The whole application is my authorship. The application is composed of 3 services: Postgres, Nginx, and Gunicorn. In a nutshell: PostgreSQL works as our database that stores all data about monuments, Gunicorn manages the traffic (content of the website) to the Nginx server so you can just simply enter the localhost and use the whole website. To see more information about how the website works run this application and enter the About page. This project shows plenty of ways on how to run this app but I recommend you to choose the Docker Compose because of the low complexity and short time required to run an app. When you already run this app you could enter localhost (default port 80) to see the Home page of the application.

preview.mov

---

Stack

Python-related tools:

• Flask
• Psycopg2
• Black

Container-related tools:

• Docker
• Docker Compose
• Docker Swarm Stack
• Docker Swarm commands
• Kubernetes

Other:

• PostgreSQL
• Nginx
• Gunicorn WSGI server
• Bash
• Linux
• Git
• Web Lanuages (HTML, CSS, JavaScript)

Click to see the project structure:

.
├───.idea
│   └───...
├───.git
│   └───...
├─── docker-compose.yml
├─── docker-stack.yml
├─── visualizer.stack.yml
├─── k8s-manifests
│    ├── namespace.yml
│    ├── gunicorn-deployment-service.yml
│    ├── nginx-deployment-service.yml
│    ├── postgres-configmap.yml
│    ├── postgres-pv.yml
│    ├── postgres-pvc.yml
│    └── postgres-deployment-service.yml
├─── README.md
├─── LICENSE
└─── services
     ├─── database
     │    ├─── Connecting.txt
     |    └─── Dockerfile
     ├─── proxy-server
     │    ├─── conf
     |    └─── Dockerfile
     └─── WSGI-server
          ├── Dockerfile
          ├── .dockerignore
          ├── infrastructure.png
          ├── docker-entrypoint.sh
          ├── main_python_files
          │   ├── __init__.py
          │   ├── config.py
          │   ├── init_db.py
          │   └── routes.py
          ├── requirements.txt
          ├── run.py
          └── src                    
              ├── static
              │   ├── css
              │   │   ├── about.css
              │   │   ├── base.css
              │   │   ├── gallery.css
              │   │   └── home.css
              │   └── js
              │       ├── base.js
              │       ├── gallery.js
              │       └── home.js
              └── template
                  ├── about.html
                  ├── base.html
                  ├── gallery.html
                  └── home.html

---

How to run an app

Note Remember that this project implements only core functionality so you should add your additional stuff in case of deploying this app on the production environment

Click to look at the demo process of deploying this app (example with Docker Compose):

startup.mov

Requirements

Whatever method to run the application you will choose you need to have Docker and Git installed you your computer first. You can download docker on any OS here. Currently, the best way of installing a Docker is to install the whole Docker Desktop (supported for Windows, macOS, and Linux). If you already have a Docker and Git you will have to download only images used by containers but this process should consume no more than 400 MB and is automatically performed before each container is launched (every container uses lightweight versions of the images to reduce memory and time while building them and reduce vulnerabilities). Remember to run the docker daemon (by e.g. opening the Docker Desktop app) before deploying an app locally or to make sure that your are in the cluster if you want to deploy this app in it.

Recommended method:

Docker Compose

This method is recommended because it's the easiest and the fastest one. Furthermore, most features are included with it. A few deploying ways have some limited functionalities because they couldn't be applied. For example, basic Docker commands don't have a max number of replicas per node because it's not a needed thing when you what to run this app fast, locally and for example for learning purposes. Docker Compose is a good compromise (in this case) between simplicity and functionality.

To run the app with Compose file, first, you have to clone this repo wherever you want:

git clone https://github.com/JakubSzuber/Local-Monuments-Website

Enter the project's directory:

cd Local-Monuments-Website

Launch all containers that will communicate with each other by using the same bridge network, created by Docker Compose by default. You can add "-d" flag to disable logs on your console:

docker-compose up

---

After launching all containers you should see in the Docker Desktop containers list a similar view to above which means that every container is running successively. Now you can click on whatever container to see information about its image layers or enter the container's inspection, terminal, logs, or stats.

Other methods:

Docker commands

You can deploy localy this app by creating containers one by one by using docker commands separately. The order of the command is important!

First create a bridge network for the containers:

docker network create monuments_net

Run your postgres database:

docker container run
-d
--name flask-database
--expose 5432
-e POSTGRES_USER=admin
-e POSTGRES_PASSWORD=admin
-e POSTGRES_DB=flask_db
-v postgres_data:/var/lib/postgresql/data
--cpus "0.50"
--memory 128M
--network monuments_net
--restart always
jakubszuber/custom-postgres

Run your main container responsible for the application logic (this container contains all necessary files):

docker container run
-d
--name
wsgi-server
--expose 5000
--cpus "0.50"
--memory 256M
--network monuments_net
--restart always
jakubszuber/custom-gunicorn

Run your nginx proxy server:

docker container run
-d
--name nginx-server
-p 80:80
--cpus "0.50"
--memory 32M
--network monuments_net
--restart always
jakubszuber/custom-nginx

Docker Swarm Stack

This way of deploying this app has the most functionalities. Most features that are applied to docker-stack.yml are focused on working on the production environment. Of course, if you would like to use this application in some way on the production you probably should make some modifications and add some additional stuff depending on your needs (docker-stack.yml implements the most core and basic infrastructure). Moreover you can uncomment lines that specify that services can be deployed only on worker nodes. Remember to initialize the cluster by "docker swarm init" or just join the existing one before you deploy an app by using this way

Note The Nginx container may restart a few times before it finally becomes stable. That's because the WSGI server (which is required for Nginx work) takes some time to start, so you'll just have to wait around one minute

To run the app with compose file first, you have to clone this repo wherever you:

git clone https://github.com/JakubSzuber/Local-Monuments-Website

Enter the project's directory:

cd Local-Monuments-Website

Launch all the resources needed for the application to work properly:

docker stack deploy -c docker-stack.yml Local-Monuments-Website

Furthermore you can use good looking visualizer to visualize your Docker Swarm cluster. To see dashboard enter http://localhost:9500

docker stack deploy --replicas -c visualizer.stack.yml visualizer

Docker Swarm commands

You can deploy locally this app in the Swarm cluster by creating containers one by one by using Docker Swarm Commands in a shell instead of using a Docker Swarm Stack. Remember that the order of the command is important!

Note If you decided to use Swarm commands instead of Swarm Stack (docker-stack.yml) then you won't have a few functionalities. More specifically - with the below commands you won't have functionalities of "placement:" part that specify the max replicas per node and the type of nodes that can take the replicas. Moreover number of replicas deployed is limited to one. Of course if you want those features and more you can use your own commands to have exact resources that you want based on your needs.

First create a overlay network for the containers (you can additionally add flags to specify your gateway, network's private IPv4, and subnet mask e.g. "--gateway 127.0.0.1" --subnet 127.0.0.1/24):

docker network create --driver overlay monuments_net

Run your postgres database by this command

docker service create
--name flask-database
--label app=local-monument-website
--update-parallelism 2
--update-delay 10s
--restart-condition on-failure
--restart-delay 10s
--restart-max-attempts 3
--restart-window 120s
--limit-cpu 0.50
--limit-memory 256M
--reserve-cpu 0.25
--reserve-memory 128M
--env POSTGRES_USER=admin
--env POSTGRES_PASSWORD=admin
--env POSTGRES_DB=flask_db
--mount type=volume,src=postgres_data,dst=/var/lib/postgresql/data
--network monuments_net
jakubszuber/custom-postgres

Run your main container responsible for the application logic (this container contains all necessary files) by this command:

docker service create
--name wsgi-server
--label app=local-monument-website
--update-parallelism 2
--update-delay 10s
--restart-condition on-failure
--restart-delay 10s
--restart-max-attempts 3
--restart-window 120s
--limit-cpu 0.50
--limit-memory 512M
--reserve-cpu 0.25
--reserve-memory 256M
--with-registry-auth
--network monuments_net
jakubszuber/custom-gunicorn

Run your nginx proxy server by this command:

docker service create
--name proxy-server
--label app=local-monument-website
--update-parallelism 2
--update-delay 10s
--restart-condition on-failure
--restart-delay 10s
--restart-max-attempts 3
--restart-window 120s
--limit-cpu 0.50
--limit-memory 256M
--reserve-cpu 0.25
--reserve-memory 128M
--publish published=80,target=80
--with-registry-auth
--network monuments_net jakubszuber/custom-nginx

Furthermore you can use good looking visualizer to visualize your Docker Swarm cluster. To see dashboard enter http://localhost:9500

docker stack deploy --replicas -c visualizer.stack.yml visualizer

Kubernetes

Note Directory k8s-manifests contains manifest files that are made generic because there are always many external tools in the Kubernetes production environment so those manifest files only implement the most core and basic infrastructure (if you want to use it you will have to enhance them significantly). After deploying this app enter on the node localhost:3007 to see app's homepage

Kubernetes Declarative objects

The best way of deploying this app in the production is to of course use a "kubectl apply", so follow the Declarative approaches of working with K8s. It's absolutely the fastest, easiest, and most flexible way. You can deploy this app by using two times "kubectl apply" and then eventually change the manifest files depending on your needs and use "kubectl apply" again to apply modifications on all running resources by using only a single command! You theoretically can also use Imperative commands or objects but it's not necessary or even it would be a waste of time and no needed creation of unnecessary complexity

To run the app with Compose file, first, you have to clone this repo wherever you:

git clone https://github.com/JakubSzuber/Local-Monuments-Website

Enter the project's directory:

cd Local-Monuments-Website

First create a our application's namespace:

kubectl apply -f k8s-manifests/namespace.yml

Then create all other resources at once by a single command:

kubectl apply -f k8s-manifests

You can print all resources within this app's namespace (so all resources that create that app): deployment for Nginx, Gunicorn, and PostgreSQL, ClusterIP service for Postgres and Gunicorn, NodePort service for Nginx, and resources related to Posgres (Configmap, Persistant Volume, Persistant Volum Claim):

kubectl get all --namespace=local-monument-website

Final result & Clean up

Depending on your method you will have different clean-ups.

---

With Docker Compose you can determinate all resources with also deleting the volume used for postgres by using a single command:

docker compose down -v

---

With Docker commands you have to use a few command to delete all recources:

docker network rm monuments_net

docker rm flask-database -v

docker rm wsgi-server

docker rm nginx-server

---

With Docker Swarm Stack you can determinate all resources with also deleting the volume used for postgres by using a single command:

docker stack remove Local-Monuments-Website

You have to remove a volume separately:

docker volume rm Local-Monuments-Website_postgres_data

And if you additionally used a visualizer:

docker stack remove visualizer

---

With Docker Swarm commands you have to use a few command to delete all recources:

docker network rm monuments_net

docker service rm flask-database

docker volume rm postgres_data

docker service rm wsgi-server

docker service rm nginx-server

And if you additionally used a visualizer:

docker stack remove visualizer

---

With Kubernets declarative approach you can determinate all resources by using a single command:

kubectl delete kubectl delete -f k8s-manifests

Text source

https://pl.wikipedia.org/wiki/Kolegiata_Naj%C5%9Bwi%C4%99tszej_Maryi_Panny_Kr%C3%B3lowej_%C5%9Awiata_w_Stargardzie https://www.pomorzezachodnie.travel/Zaplanuj_pobyt-Przydatne_informacje-Miejsca_kultu_religijnego-Kosciol_Rzymskokatolicki/a,4146/Kosciol_pw_sw_Jana_Chrzciciela https://pl.wikipedia.org/wiki/Ko%C5%9Bci%C3%B3%C5%82_%C5%9Bw._Jana_w_Stargardzie https://pl.wikipedia.org/wiki/Brama_Pyrzycka_w_Stargardzie https://pomorzezachodnie.travel/Poznawaj-Dziedzictwo_Pomorza-Fortyfikacje_i_militaria-Obwarowania_miejskie/a,6195/Brama_Pyrzycka https://sciaga.pl/tekst/51768-52-stargardzkie_zabytki_brama_pyrzycka https://pl.wikipedia.org/wiki/Brama_Wa%C5%82owa https://pomorzezachodnie.travel/Spedzaj_czas-Kulturalnie-Galerie/a,5123/Brama_Walowa https://pl.wikipedia.org/wiki/Brama_M%C5%82y%C5%84ska_w_Stargardzie http://baza-turystyczna.eu/wojewodztwo-zachodnio-pomorskie--4/miasto-stargard_szczecinski--66/zabytki/obiekt-brama_portowa_mlynska--120/ https://pl.wikipedia.org/wiki/Wie%C5%BCa_ci%C5%9Bnie%C5%84 http://baza-turystyczna.eu/wojewodztwo-zachodnio-pomorskie--4/miasto-stargard_szczecinski--66/zabytki/obiekt-wieza_cisnien--118/ https://pl.wikipedia.org/wiki/Wie%C5%BCa_ci%C5%9Bnie%C5%84_w_Stargardzie https://www.wikiwand.com/pl/Wie%C5%BCa_ci%C5%9Bnie%C5%84_w_Stargardzie https://pomorzezachodnie.travel/Poznawaj-Dziedzictwo_Pomorza-Zabytki_techniki_i_inzynierii/a,6197/Wieza_cisnien https://pl.wikipedia.org/wiki/Baszta https://pl.wikipedia.org/wiki/Baszta_Morze_Czerwone https://pomorzezachodnie.travel/Poznawaj-Dziedzictwo_Pomorza-Fortyfikacje_i_militaria-Obwarowania_miejskie/a,6196/Baszta_Morze_Czerwone https://tropter.com/pl/polska/stargard/baszta-morze-czerwone https://pl.wikipedia.org/wiki/Baszta_Bia%C5%82og%C5%82%C3%B3wka https://www.polska.travel/pl/muzea/baszta-bialoglowka https://pl.wikipedia.org/wiki/Ratusz_w_Stargardzie https://pomorzezachodnie.travel/Zaplanuj_pobyt-Przydatne_informacje-Urzedy_publiczne/a,2763/Urzad_Miasta_Stargard_Ratusz_Staromiejski_ https://zabytek.pl/pl/obiekty/stargard-ratusz)

Links to each used image is in the file init_db.py