From 11304414680d7e58ced562c25a862fd5a85c2ee7 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Fri, 7 Feb 2025 15:03:26 +0330
Subject: [PATCH 001/116] added docker stack file

---
 .../Docker/docker-stack-example.yml           | 74 +++++++++++++++++++
 1 file changed, 74 insertions(+)
 create mode 100644 Containerization & Orchestration/Docker/docker-stack-example.yml

diff --git a/Containerization & Orchestration/Docker/docker-stack-example.yml b/Containerization & Orchestration/Docker/docker-stack-example.yml
new file mode 100644
index 0000000..d492724
--- /dev/null
+++ b/Containerization & Orchestration/Docker/docker-stack-example.yml	
@@ -0,0 +1,74 @@
+version: "3.8"
+
+services:
+  web:
+    image: nginx:alpine
+    ports:
+      - "80:80"
+    deploy:
+      # Service mode: use "replicated" for a set number of replicas,
+      # or "global" to run one instance on every node.
+      mode: replicated
+
+      # Number of container replicas to run (only applicable in replicated mode)
+      replicas: 3
+
+      # Rolling update configuration (applies when updating the service)
+      update_config:
+        # Number of containers to update at the same time
+        parallelism: 2
+        # Delay between updating groups of containers (e.g., "10s" for 10 seconds)
+        delay: 10s
+        # Action to take if an update fails: rollback, pause, or continue
+        failure_action: rollback
+        # Time to monitor each updated container before proceeding to the next batch
+        monitor: 10s
+        # Maximum failure ratio (0.0 to 1.0) acceptable during the update
+        max_failure_ratio: 0.3
+
+      # Rollback configuration (applies if a deployment needs to be undone)
+      rollback_config:
+        parallelism: 1
+        delay: 10s
+        # Action to take if rollback fails
+        failure_action: pause
+        monitor: 10s
+        max_failure_ratio: 0.2
+
+      # Restart policy for containers in the service
+      restart_policy:
+        # Restart condition can be "none", "on-failure", or "any"
+        condition: on-failure
+        # Delay between restart attempts
+        delay: 5s
+        # Maximum number of restart attempts before considering the container as failed
+        max_attempts: 3
+        # Time window used to evaluate restart attempts (e.g., "120s")
+        window: 120s
+
+      # Resource constraints and reservations for containers
+      resources:
+        limits:
+          # Maximum number of CPUs the container can use (as a fraction or whole number)
+          cpus: "0.50"
+          # Maximum memory (e.g., "50M" for 50 megabytes)
+          memory: 50M
+        reservations:
+          # Guaranteed minimum CPUs for the container
+          cpus: "0.25"
+          # Guaranteed minimum memory
+          memory: 20M
+
+      # Placement constraints and preferences to control which nodes run the service
+      placement:
+        # Constraints ensure that only nodes meeting certain conditions are eligible.
+        constraints:
+          - node.role == manager
+          - node.labels.region == us-east
+        # Preferences allow you to influence (but not enforce) distribution.
+        preferences:
+          - spread: node.labels.az
+
+      # Custom metadata labels for the service
+      labels:
+        com.example.description: "Sample web service using all deploy parameters"

From 55347bfd59175cb87600b950a43305da548d184b Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 12 Feb 2025 21:08:15 +0330
Subject: [PATCH 002/116] Update Kuber Doc

---
 .../Kubernetes/3-Commands.md                  | 198 +++++++++++-------
 1 file changed, 121 insertions(+), 77 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/3-Commands.md b/Containerization & Orchestration/Kubernetes/3-Commands.md
index 5c36378..2041bd5 100755
--- a/Containerization & Orchestration/Kubernetes/3-Commands.md	
+++ b/Containerization & Orchestration/Kubernetes/3-Commands.md	
@@ -1,8 +1,12 @@
+Below is an improved version of your Kubernetes Command Reference. This revision enhances clarity, fixes typos, organizes related commands into logical sections, and standardizes formatting for readability.
 
+---
 
 # Kubernetes Command Reference
 
-This document provides a reference for common `kubectl` commands used for managing Kubernetes clusters. Use the examples and explanations below to help manage nodes, namespaces, pods, deployments, and more.
+This document provides a concise reference for common `kubectl` commands used to manage Kubernetes clusters. Whether you’re managing nodes, namespaces, pods, deployments, or autoscaling, the examples below will help you perform everyday tasks with ease.
+
+---
 
 ## Table of Contents
 
@@ -10,6 +14,9 @@ This document provides a reference for common `kubectl` commands used for managi
   - [Table of Contents](#table-of-contents)
   - [General Commands](#general-commands)
   - [Node Management](#node-management)
+    - [Listing Nodes](#listing-nodes)
+    - [Labeling Nodes](#labeling-nodes)
+    - [Node Maintenance (Cordon/Drain)](#node-maintenance-cordondrain)
   - [Namespace Management](#namespace-management)
   - [Pod Management](#pod-management)
     - [Listing Pods](#listing-pods)
@@ -18,9 +25,10 @@ This document provides a reference for common `kubectl` commands used for managi
   - [API Resources and Documentation](#api-resources-and-documentation)
   - [Logs and Pod Information](#logs-and-pod-information)
   - [Applying YAML Files](#applying-yaml-files)
-  - [Managing Nodes and Labels](#managing-nodes-and-labels)
   - [Viewing Cluster Resources](#viewing-cluster-resources)
   - [ReplicaSet and Deployment Management](#replicaset-and-deployment-management)
+    - [Scaling and Rollouts](#scaling-and-rollouts)
+    - [Autoscaling](#autoscaling)
   - [Additional Information](#additional-information)
 
 ---
@@ -29,6 +37,8 @@ This document provides a reference for common `kubectl` commands used for managi
 
 - **List API Resources**
 
+  Display all available API resources along with their short names:
+
   ```bash
   kubectl api-resources
   ```
@@ -37,34 +47,65 @@ This document provides a reference for common `kubectl` commands used for managi
 
 ## Node Management
 
-- **Show all nodes**
+### Listing Nodes
+
+- **Show All Nodes**
 
   ```bash
-  kubectl get node
+  kubectl get nodes
   ```
 
-- **Set a label on a node**
+### Labeling Nodes
+
+- **Set a Custom Label on a Node**
 
   ```bash
-  kubectl label nodes <node-name> kubernetes.io/<label-key>=<label-value>
+  kubectl label node <node-name> kubernetes.io/<label-key>=<label-value>
   ```
 
+  > **Note:** Replace `<node-name>`, `<label-key>`, and `<label-value>` with your desired values.
+
+### Node Maintenance (Cordon/Drain)
+
+- **Cordon a Node**  
+  Prevent new pods from being scheduled on the node.
+
+  ```bash
+  kubectl cordon <node-name>
+  ```
+
+- **Uncordon a Node**  
+  Mark the node as schedulable again.
+
+  ```bash
+  kubectl uncordon <node-name>
+  ```
+
+- **Drain a Node**  
+  Evict all pods from the node (excluding those managed by DaemonSets).
+
+  ```bash
+  kubectl drain <node-name> --ignore-daemonsets --delete-local-data
+  ```
+
+  > **Warning:** Draining a node will evict running pods. Ensure this action is planned to avoid service disruption.
+
 ---
 
 ## Namespace Management
 
-- **List all namespaces**
+- **List All Namespaces**
 
   ```bash
   kubectl get namespaces
-  # or the abbreviated version:
+  # Or use the shorthand:
   kubectl get ns
   ```
 
-- **Create a custom namespace**
+- **Create a New Namespace**
 
   ```bash
-  kubectl create ns <namespace-name>
+  kubectl create namespace <namespace-name>
   ```
 
 ---
@@ -73,104 +114,103 @@ This document provides a reference for common `kubectl` commands used for managi
 
 ### Listing Pods
 
-- **List pods in the default namespace**
+- **List Pods in the Default Namespace**
 
   ```bash
-  kubectl get pod
+  kubectl get pods
   ```
 
-- **List pods with detailed information (wide output) in the default namespace**
+- **List Pods with Detailed Information (Wide Output)**
 
   ```bash
-  kubectl get pod -o wide
+  kubectl get pods -o wide
   ```
 
-- **List pods with detailed information in a specific namespace**
+- **List Pods in a Specific Namespace**
 
   ```bash
-  kubectl get pod -o wide -n <namespace-name>
+  kubectl get pods -o wide -n <namespace-name>
   ```
 
 ### Running a Pod
 
-- **Run a new pod**
+> **Note:** While `kubectl run` is a versatile command, note that in recent Kubernetes versions it is primarily used for running single pods (not deployments). For more complex configurations, consider using YAML manifests.
 
-  Use the following command structure to run a pod with various options:
+- **Basic Example:**
 
   ```bash
-  kubectl run <pod-name> <switch> {
-    --image=<image-name>,                # Container image to use
-    --port=<port-number>,                # Port that the container exposes
-    -n <namespace-name>,                 # Namespace in which to run the pod
-    --env="KEY=VALUE",                   # Environment variables for the container
-    --command,                           # Treat the following arguments as the command
-    --replicas=<number>,                 # Number of pod replicas to create
-    --labels="key=value,key2=value2",    # Labels to assign to the pod(s)
-    --dry-run=client,                    # Print the object without creating it
-    --restart=<Always|OnFailure|Never>,  # Pod restart policy
-    --overrides='<json>',                # JSON override for the generated object
-    --image-pull-policy=<policy>,        # Image pull policy (Always, IfNotPresent, Never)
-    --limits=cpu=<cpu>,memory=<memory>,   # Resource limits for the container
-    --requests=cpu=<cpu>,memory=<memory>  # Resource requests for the container
-  }
+  kubectl run <pod-name> --image=<image-name> --port=<port-number> -n <namespace-name>
   ```
 
-  - **Example:**
+- **Advanced Example with Multiple Options:**
 
-    ```bash
-    kubectl run mypod --image=nginx --port=80 -n mynamespace \
-      --env="ENV_VAR_NAME=VALUE" --command -- nginx -g "daemon off;" \
-      --replicas=3 --labels="app=myapp,env=prod" --dry-run=client \
-      --restart=Always --overrides='{"spec": {"containers": [{"name": "nginx", "image": "nginx"}]}}' \
-      --image-pull-policy=IfNotPresent --limits=cpu=100m,memory=256Mi \
-      --requests=cpu=50m,memory=128Mi
-    ```
+  ```bash
+  kubectl run mypod --image=nginx --port=80 -n mynamespace \
+    --env="ENV_VAR_NAME=VALUE" --command -- nginx -g "daemon off;" \
+    --restart=Always --dry-run=client \
+    --labels="app=myapp,env=prod" \
+    --limits=cpu=100m,memory=256Mi --requests=cpu=50m,memory=128Mi
+  ```
+
+  **Common Options Explained:**
+
+  - `--image`: Container image to use.
+  - `--port`: Port exposed by the container.
+  - `-n` or `--namespace`: Namespace in which to run the pod.
+  - `--env`: Set environment variables.
+  - `--command`: Treat the following arguments as the command to run.
+  - `--restart`: Pod restart policy (`Always`, `OnFailure`, or `Never`).
+  - `--labels`: Assign labels to the pod.
+  - `--dry-run`: Validate the command without creating the pod.
+  - `--limits` and `--requests`: Define resource limits and requests for the container.
 
 ### Deleting a Pod
 
-- **Delete a pod in a custom namespace**
+- **Delete a Pod in a Specific Namespace**
 
   ```bash
-  kubectl delete pod -n <namespace-name> <pod-name>
+  kubectl delete pod <pod-name> -n <namespace-name>
   ```
 
 ---
 
 ## API Resources and Documentation
 
-- **Get documentation for an API resource**
+- **Get Detailed Documentation for an API Resource**
 
   ```bash
   kubectl explain <api-resource-name>
   ```
 
-  - *Example:*
+  *Example:*
 
-    ```bash
-    kubectl explain pod
-    ```
+  ```bash
+  kubectl explain pod
+  ```
 
 ---
 
 ## Logs and Pod Information
 
-- **Stream logs for a running pod**
+- **Stream Logs for a Running Pod**
 
   ```bash
   kubectl logs -f -n <namespace-name> <pod-name>
   ```
 
-- **Get detailed state and log information for a pod**
+- **Get Detailed Information About a Pod**
 
   ```bash
-  kubectl describe pod -n <namespace-name> <pod-name>
+  kubectl describe pod <pod-name> -n <namespace-name>
   ```
 
 ---
 
 ## Applying YAML Files
 
-- **Apply configuration from a YAML file to a specific namespace**
+- **Apply a Configuration from a YAML File**
+
+  Apply a YAML configuration to a specific namespace:
 
   ```bash
   kubectl apply -f <yaml-file> -n <namespace-name>
@@ -178,59 +218,65 @@ This document provides a reference for common `kubectl` commands used for managi
 
 ---
 
-## Managing Nodes and Labels
-
-- **Label a node with a custom key-value pair**
-
-  ```bash
-  kubectl label nodes <node-name> kubernetes.io/<label-key>=<label-value>
-  ```
-
----
-
 ## Viewing Cluster Resources
 
-- **Display all resources loaded in a namespace**
+- **Display All Resources in a Namespace**
 
   ```bash
   kubectl get all -n <namespace-name>
   ```
 
-- **Display replica sets, pods, and deployments in a specific namespace**
+- **Display ReplicaSets, Pods, and Deployments in a Specific Namespace**
 
   ```bash
-  kubectl get rs,pod,deployment -n <namespace-name>
+  kubectl get rs,pods,deployments -n <namespace-name>
   ```
 
 ---
 
 ## ReplicaSet and Deployment Management
 
+### Scaling and Rollouts
+
 - **Scale a ReplicaSet**
 
   ```bash
-  kubectl scale rs <replicaset-name> -n <namespace-name> --replicas=<count>
+  kubectl scale rs <replicaset-name> --replicas=<count> -n <namespace-name>
   ```
 
-- **View rollout history of a deployment**
+- **View Rollout History of a Deployment**
 
   ```bash
-  kubectl rollout history deployment -n <namespace-name> <deployment-name>
+  kubectl rollout history deployment <deployment-name> -n <namespace-name>
   ```
 
-- **View details of a specific revision in a deployment's rollout history**
+- **View Details of a Specific Revision**
 
   ```bash
-  kubectl rollout history deployment -n <namespace-name> <deployment-name> --revision <number>
+  kubectl rollout history deployment <deployment-name> -n <namespace-name> --revision=<number>
   ```
 
-- **Roll back a deployment to a specific revision**
+- **Roll Back a Deployment to a Specific Revision**
 
   ```bash
-  kubectl rollout undo deployment -n <namespace-name> <deployment-name> --to-revision=<number>
+  kubectl rollout undo deployment <deployment-name> -n <namespace-name> --to-revision=<number>
   ```
 
-  > **Note:** The command for rolling back to a specific revision is `kubectl rollout undo` rather than using `--to-revision` with `kubectl rollout history`.
+### Autoscaling
+
+- **Autoscale a Deployment**
+
+  Automatically scale a deployment based on CPU utilization:
+
+  ```bash
+  kubectl autoscale deployment <deployment-name> -n <namespace-name> --cpu-percent=<target-cpu-percentage> --min=<min-pods> --max=<max-pods>
+  ```
+
+- **View Horizontal Pod Autoscalers (HPA)**
+
+  ```bash
+  kubectl get hpa -n <namespace-name>
+  ```
 
 ---
 
@@ -238,6 +284,4 @@ This document provides a reference for common `kubectl` commands used for managi
 
 - **Static Manifest Files**
 
-  All YAML files located under `/etc/kubernetes/manifests/` are automatically loaded after a server reboot.
-
----
+  Any YAML files placed in `/etc/kubernetes/manifests/` are automatically loaded when the kubelet starts (for example, after a server reboot).

From d831f0e72f711f923263aac110ae4d3e394ef376 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Thu, 13 Feb 2025 00:24:16 +0330
Subject: [PATCH 003/116] Added Wordload files

---
 .../Kubernetes/workloads/cronjob.yaml         | 20 +++++++++++++
 .../Kubernetes/workloads/deployment.yaml      | 28 +++++++++++++++++++
 .../Kubernetes/workloads/ds.yml               | 19 +++++++++++++
 .../Kubernetes/workloads/job.yaml             | 15 ++++++++++
 .../Kubernetes/workloads/namespace.yaml       |  5 ++++
 .../Kubernetes/workloads/pod.yaml             | 23 +++++++++++++++
 .../Kubernetes/workloads/replicaset.yml       | 18 ++++++++++++
 7 files changed, 128 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/cronjob.yaml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/deployment.yaml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/ds.yml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/job.yaml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/namespace.yaml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/pod.yaml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/replicaset.yml

diff --git a/Containerization & Orchestration/Kubernetes/workloads/cronjob.yaml b/Containerization & Orchestration/Kubernetes/workloads/cronjob.yaml
new file mode 100644
index 0000000..b8396e3
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/cronjob.yaml	
@@ -0,0 +1,20 @@
+apiVersion: batch/v1
+kind: CronJob
+metadata:
+  name: cronjob1
+  namespace: ns-test
+spec:
+  schedule: "* * * * *"
+  jobTemplate:
+    spec:
+      template:
+        spec:
+          containers:
+            - name: mycronjob
+              image: debian
+              command:
+                - /bin/bash
+                - -c
+                - "echo 'Hello, CronJob!'"
+          restartPolicy: Never
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/deployment.yaml b/Containerization & Orchestration/Kubernetes/workloads/deployment.yaml
new file mode 100644
index 0000000..fa20bc0
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/deployment.yaml	
@@ -0,0 +1,28 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-deployment
+  namespace: ns-test
+  labels:
+    name: deployment-test
+spec:
+  replicas: 2
+  selector:
+    matchLabels:
+      name: app1
+  template:
+    metadata:
+      labels:
+        name: app1
+    spec:
+      containers:
+        - name: nginx-deployment
+          image: nginx:1.26
+          resources:
+            limits:
+              cpu: "400m"
+              memory: "512Mi"
+            requests:
+              cpu: "200m"
+              memory: "128Mi"
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/ds.yml b/Containerization & Orchestration/Kubernetes/workloads/ds.yml
new file mode 100644
index 0000000..9ab75a1
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/ds.yml	
@@ -0,0 +1,19 @@
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  name: daemonset-test
+  namespace: ns-test
+spec:
+  selector:
+    matchLabels:
+      name: node-exporter
+  template:
+    metadata:
+      labels:
+        name: node-exporter
+    spec:
+      containers:
+        - name: node-exporter
+          image: prom/node-exporter
+
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/job.yaml b/Containerization & Orchestration/Kubernetes/workloads/job.yaml
new file mode 100644
index 0000000..67bd525
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/job.yaml	
@@ -0,0 +1,15 @@
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: job1
+  namespace: ns-test
+spec:
+  template:
+    spec:
+      containers:
+        - name: job-container
+          image: debian
+          command:
+            - echo
+            - "hello world"
+      restartPolicy: Never
diff --git a/Containerization & Orchestration/Kubernetes/workloads/namespace.yaml b/Containerization & Orchestration/Kubernetes/workloads/namespace.yaml
new file mode 100644
index 0000000..0b8d1d8
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/namespace.yaml	
@@ -0,0 +1,5 @@
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: ns-test
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/pod.yaml b/Containerization & Orchestration/Kubernetes/workloads/pod.yaml
new file mode 100644
index 0000000..66dae37
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/pod.yaml	
@@ -0,0 +1,23 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  namespace: ns-test
+  name: pod-tests
+  labels:
+    var1: var1_value
+    var2: var2_value
+    app.kubernetes.io/var3: var3_value
+    app.kubernetes.io/var4: var4_value
+spec:
+  containers:
+    - name: nginx
+      image: nginx
+      resources:
+        limits:
+          memory: "150Mi"
+          cpu: "500m"
+        requests:
+          memory: "100Mi"
+          cpu: "200m"
+  nodeSelector:
+    kubernetes.io/hostname: kuber-2
diff --git a/Containerization & Orchestration/Kubernetes/workloads/replicaset.yml b/Containerization & Orchestration/Kubernetes/workloads/replicaset.yml
new file mode 100644
index 0000000..b7eaf4b
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/replicaset.yml	
@@ -0,0 +1,18 @@
+apiVersion: apps/v1
+kind: ReplicaSet
+metadata:
+  name: app1
+  namespace: ns-test
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app.kubernetes.io/name: app1
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/name: app1
+    spec:
+      containers:
+        - name: nginx
+          image: nginx

From e182881068a1d12c3b85df58a6931a0f03785647 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Sat, 15 Feb 2025 17:28:07 +0330
Subject: [PATCH 004/116] added some file and updated

---
 .../Kubernetes/3-Commands.md                  | 49 ++++++++++++-------
 .../workloads/deployment-with-service.yaml    | 23 +++++++++
 .../Kubernetes/workloads/service.yaml         | 15 ++++++
 3 files changed, 70 insertions(+), 17 deletions(-)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/service.yaml

diff --git a/Containerization & Orchestration/Kubernetes/3-Commands.md b/Containerization & Orchestration/Kubernetes/3-Commands.md
index 2041bd5..4c9ce9d 100755
--- a/Containerization & Orchestration/Kubernetes/3-Commands.md	
+++ b/Containerization & Orchestration/Kubernetes/3-Commands.md	
@@ -1,10 +1,10 @@
-Below is an improved version of your Kubernetes Command Reference. This revision enhances clarity, fixes typos, organizes related commands into logical sections, and standardizes formatting for readability.
+Below is an enhanced version of your Kubernetes Command Reference. This revision further refines the structure, improves consistency, and adds a few extra sections for clarity and ease of use.
 
 ---
 
 # Kubernetes Command Reference
 
-This document provides a concise reference for common `kubectl` commands used to manage Kubernetes clusters. Whether you’re managing nodes, namespaces, pods, deployments, or autoscaling, the examples below will help you perform everyday tasks with ease.
+This guide provides a concise reference for common `kubectl` commands used to manage Kubernetes clusters. Whether you’re managing nodes, namespaces, pods, deployments, or autoscaling, the examples below will help you perform everyday tasks with confidence.
 
 ---
 
@@ -22,21 +22,21 @@ This document provides a concise reference for common `kubectl` commands used to
     - [Listing Pods](#listing-pods)
     - [Running a Pod](#running-a-pod)
     - [Deleting a Pod](#deleting-a-pod)
-  - [API Resources and Documentation](#api-resources-and-documentation)
-  - [Logs and Pod Information](#logs-and-pod-information)
+  - [API Resources \& Documentation](#api-resources--documentation)
+  - [Logs \& Pod Information](#logs--pod-information)
   - [Applying YAML Files](#applying-yaml-files)
   - [Viewing Cluster Resources](#viewing-cluster-resources)
-  - [ReplicaSet and Deployment Management](#replicaset-and-deployment-management)
+  - [ReplicaSet \& Deployment Management](#replicaset--deployment-management)
     - [Scaling and Rollouts](#scaling-and-rollouts)
     - [Autoscaling](#autoscaling)
+  - [Port Forwarding](#port-forwarding)
   - [Additional Information](#additional-information)
 
 ---
 
 ## General Commands
 
-- **List API Resources**
-
+- **List API Resources**  
   Display all available API resources along with their short names:
 
   ```bash
@@ -88,7 +88,7 @@ This document provides a concise reference for common `kubectl` commands used to
   kubectl drain <node-name> --ignore-daemonsets --delete-local-data
   ```
 
-  > **Warning:** Draining a node will evict running pods. Ensure this action is planned to avoid service disruption.
+  > **Warning:** Draining a node will evict running pods. Ensure that you plan this action to avoid service disruption.
 
 ---
 
@@ -98,7 +98,7 @@ This document provides a concise reference for common `kubectl` commands used to
 
   ```bash
   kubectl get namespaces
-  # Or use the shorthand:
+  # Or the shorthand:
   kubectl get ns
   ```
 
@@ -134,7 +134,7 @@ This document provides a concise reference for common `kubectl` commands used to
 
 ### Running a Pod
 
-> **Note:** While `kubectl run` is a versatile command, note that in recent Kubernetes versions it is primarily used for running single pods (not deployments). For more complex configurations, consider using YAML manifests.
+> **Note:** The `kubectl run` command is best suited for running single pods. For more complex deployments, consider using YAML manifests.
 
 - **Basic Example:**
 
@@ -174,7 +174,7 @@ This document provides a concise reference for common `kubectl` commands used to
 
 ---
 
-## API Resources and Documentation
+## API Resources & Documentation
 
 - **Get Detailed Documentation for an API Resource**
 
@@ -190,7 +190,7 @@ This document provides a concise reference for common `kubectl` commands used to
 
 ---
 
-## Logs and Pod Information
+## Logs & Pod Information
 
 - **Stream Logs for a Running Pod**
 
@@ -234,7 +234,7 @@ This document provides a concise reference for common `kubectl` commands used to
 
 ---
 
-## ReplicaSet and Deployment Management
+## ReplicaSet & Deployment Management
 
 ### Scaling and Rollouts
 
@@ -264,8 +264,7 @@ This document provides a concise reference for common `kubectl` commands used to
 
 ### Autoscaling
 
-- **Autoscale a Deployment**
-
+- **Autoscale a Deployment**  
   Automatically scale a deployment based on CPU utilization:
 
   ```bash
@@ -280,8 +279,24 @@ This document provides a concise reference for common `kubectl` commands used to
 
 ---
 
+## Port Forwarding
+
+Sometimes you need to access a service or pod directly from your local machine. Use the following command to forward a port:
+
+```bash
+kubectl port-forward -n <namespace-name> svc/<service-name> <local-port>:<target-port>
+```
+
+> **Example:** Forward local port 8080 to port 80 of the service named `my-service` in the `mynamespace` namespace:
+>
+> ```bash
+> kubectl port-forward -n mynamespace svc/my-service 8080:80
+> ```
+
+---
+
 ## Additional Information
 
-- **Static Manifest Files**
-
+- **Static Manifest Files**  
   Any YAML files placed in `/etc/kubernetes/manifests/` are automatically loaded when the kubelet starts (for example, after a server reboot).
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml b/Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml
new file mode 100644
index 0000000..912d9a0
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml	
@@ -0,0 +1,23 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-deployment
+  namespace: ns-test
+  labels:
+    name: deployment-test
+    app: nginx
+spec:
+  replicas: 2
+  selector:
+    matchLabels:
+      name: app1
+      app: nginx
+  template:
+    metadata:
+      labels:
+        name: app1
+        app: nginx
+    spec:
+      containers:
+        - name: nginx-deployment
+          image: nginx:1.26
diff --git a/Containerization & Orchestration/Kubernetes/workloads/service.yaml b/Containerization & Orchestration/Kubernetes/workloads/service.yaml
new file mode 100644
index 0000000..e2cf24d
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/service.yaml	
@@ -0,0 +1,15 @@
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx
+  namespace: ns-test
+  labels:
+    app: nginx
+spec:
+  type: NodePort # ClusterIP Or LoadBalancer
+  selector:
+    app: nginx
+  ports:
+    - name: http
+      port: 80
+      targetPort: 80

From 91faa030faea18e4abf20d0755dbf8a05c178471 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 9 Apr 2025 14:59:32 +0200
Subject: [PATCH 005/116] update kuber doc

---
 Containerization & Orchestration/Kubernetes/3-Commands.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/3-Commands.md b/Containerization & Orchestration/Kubernetes/3-Commands.md
index 4c9ce9d..c28e7cf 100755
--- a/Containerization & Orchestration/Kubernetes/3-Commands.md	
+++ b/Containerization & Orchestration/Kubernetes/3-Commands.md	
@@ -1,7 +1,3 @@
-Below is an enhanced version of your Kubernetes Command Reference. This revision further refines the structure, improves consistency, and adds a few extra sections for clarity and ease of use.
-
----
-
 # Kubernetes Command Reference
 
 This guide provides a concise reference for common `kubectl` commands used to manage Kubernetes clusters. Whether you’re managing nodes, namespaces, pods, deployments, or autoscaling, the examples below will help you perform everyday tasks with confidence.

From 5e3d651660736ee41f02baa60f11661d9d6b8d3d Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 9 Apr 2025 15:24:55 +0200
Subject: [PATCH 006/116] added nfs document

---
 Storage/NFS/setup.md | 121 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 121 insertions(+)
 create mode 100644 Storage/NFS/setup.md

diff --git a/Storage/NFS/setup.md b/Storage/NFS/setup.md
new file mode 100644
index 0000000..7af2176
--- /dev/null
+++ b/Storage/NFS/setup.md
@@ -0,0 +1,121 @@
+# 📡 NFS Server & Client Setup Guide (Ubuntu)
+
+Easily set up a Network File System (NFS) for sharing files between Linux systems on the same network.
+
+---
+
+## 🖥️ Server Configuration (Ubuntu)
+
+### 1. Install NFS Kernel Server
+
+Install the required package:
+
+```bash
+sudo apt update
+sudo apt install nfs-kernel-server
+```
+
+### 2. Create a Shared Directory
+
+Replace `<shared-directory>` with your preferred path:
+
+```bash
+sudo mkdir -p <shared-directory>
+sudo chown nobody:nogroup <shared-directory>
+sudo chmod 777 <shared-directory>
+```
+
+> ✅ *Best practice:* Use a dedicated directory for NFS shares, e.g., `/srv/nfs/shared`.
+
+### 3. Configure NFS Exports
+
+Create an exports configuration file:
+
+```bash
+sudo vim /etc/exports.d/shared.exports
+```
+
+Add the following line (update paths and IPs accordingly):
+
+```
+<shared-directory> <client-ip>(rw,sync,no_root_squash,no_subtree_check)
+```
+
+> 💡 **Notes:**  
+> - `<shared-directory>`: Full path to the directory you want to share  
+> - `<client-ip>`: IP address of the client allowed to access the share  
+
+### 4. Apply Export Changes
+
+```bash
+sudo exportfs -ra
+```
+
+### 5. Enable and Restart NFS Service
+
+```bash
+sudo systemctl enable nfs-server
+sudo systemctl restart nfs-server
+```
+
+---
+
+## 💻 Client Configuration (Ubuntu)
+
+### 1. Install NFS Client Packages
+
+```bash
+sudo apt update
+sudo apt install nfs-common rpcbind
+```
+
+### 2. Create a Mount Point
+
+Choose a local directory to mount the share (e.g., `/mnt/nfs`):
+
+```bash
+sudo mkdir -p <mount-point>
+sudo chmod 777 <mount-point>
+```
+
+### 3. Mount the NFS Share (Temporary)
+
+```bash
+sudo mount -t nfs <server-ip>:<shared-directory> <mount-point>
+```
+
+> Example:  
+> `sudo mount -t nfs 192.168.0.10:/srv/nfs/shared /mnt/nfs`
+
+### 4. Enable Auto-Mount at Boot
+
+Edit the fstab file:
+
+```bash
+sudo vim /etc/fstab
+```
+
+Add this line:
+
+```
+<server-ip>:<shared-directory> <mount-point> nfs defaults 0 0
+```
+
+> Example:  
+> `192.168.0.10:/srv/nfs/shared /mnt/nfs nfs defaults 0 0`
+
+### 5. Verify and Reload Mounts
+
+```bash
+sudo mount -a
+```
+
+---
+
+## ✅ Final Checklist
+
+- 🔄 NFS server and client packages installed  
+- 📁 Shared and mount directories properly set  
+- 🔐 Permissions and access IPs correctly configured  
+- ⚙️ Auto-mount enabled with `/etc/fstab`  
+

From 92e3749529347089e7596b0ddc853c11927dfaf3 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Fri, 16 May 2025 00:15:52 +0330
Subject: [PATCH 007/116] docker doc: update swarm doc

---
 .../Docker/5-Docker-Swarm.md                  | 172 +++++++++++-------
 1 file changed, 104 insertions(+), 68 deletions(-)

diff --git a/Containerization & Orchestration/Docker/5-Docker-Swarm.md b/Containerization & Orchestration/Docker/5-Docker-Swarm.md
index 1f19db3..cdc471d 100755
--- a/Containerization & Orchestration/Docker/5-Docker-Swarm.md	
+++ b/Containerization & Orchestration/Docker/5-Docker-Swarm.md	
@@ -1,89 +1,85 @@
-# Docker Swarm Documentation
+# 📦 Docker Swarm Documentation
 
-This guide covers key commands and workflows for managing a Docker Swarm cluster. It includes information on initializing the cluster, node management, service management, and best practices to ensure your cluster remains operational.
+Comprehensive guide to managing a **Docker Swarm** cluster. This document includes core commands, workflows, and best practices for maintaining a healthy and operational environment.
 
 ---
 
-## Table of Contents
+## 📚 Table of Contents
 
-1. [Cluster Health & Manager Count](#cluster-health--manager-count)
-2. [Example Workflow: Setting Up Nginx](#example-workflow-setting-up-nginx)
-3. [Cluster Initialization and Management](#cluster-initialization-and-management)
-4. [Node Management](#node-management)
-5. [Service Management](#service-management)
-6. [Join Tokens](#join-tokens)
+1. [🔧 Cluster Health & Manager Count](#-cluster-health--manager-count)
+2. [🚀 Example Workflow: Setting Up Nginx](#-example-workflow-setting-up-nginx)
+3. [⚙️ Cluster Initialization and Management](#️-cluster-initialization-and-management)
+4. [🖥️ Node Management](#️-node-management)
+5. [🛠️ Service Management](#️-service-management)
+6. [🔑 Join Tokens & Node Configuration](#-join-tokens--node-configuration)
 
 ---
 
-## Cluster Health & Manager Count
+## 🔧 Cluster Health & Manager Count
 
-To maintain a healthy and functional Docker Swarm cluster, **the number of manager nodes must exceed 50% of the total nodes**. If the manager nodes fall below 51% of the cluster, the system will lose quorum and become non-operational. Always monitor your manager count to ensure high availability.
+A Docker Swarm cluster requires a **majority of manager nodes** to be functional for quorum.
+
+> **Best Practice:** Always maintain **more than 50%** manager nodes online. Losing quorum will render the cluster non-operational.
 
 ---
 
-## Example Workflow: Setting Up Nginx
+## 🚀 Example Workflow: Setting Up Nginx
 
-When deploying services such as Nginx, the typical workflow in Docker Swarm is:
+Docker Swarm handles service deployment through several internal components:
 
-1. **API**: Handle incoming requests.
-2. **Allocator**: Distribute workload to available nodes.
-3. **Dispatcher**: Manage task assignments.
-4. **Scheduler**: Ensure tasks run on the optimal nodes.
+1. **API** – Receives service requests.
+2. **Allocator** – Determines resource allocation.
+3. **Dispatcher** – Assigns tasks to nodes.
+4. **Scheduler** – Places tasks on optimal nodes.
 
-This workflow ensures that your service is efficiently distributed and scaled across the cluster.
+This process ensures resilient and efficient service distribution.
 
 ---
 
-## Cluster Initialization and Management
+## ⚙️ Cluster Initialization and Management
 
-### Create Cluster
+### 🔹 Initialize Cluster
 
-Initialize a new Docker Swarm cluster:
 ```bash
 docker swarm init
 ```
-This command sets up the current node as the manager of a new cluster.
 
-### Create Cluster with a Specific Interface
+### 🔹 Initialize with Specific Interface
 
-Specify an IP address or interface name when initializing the cluster:
 ```bash
-docker swarm init --advertise-addr <ip or interface name>
+docker swarm init --advertise-addr <ip-or-interface>
 ```
-This ensures that the node advertises the correct network interface for other nodes to join.
 
-### Join Cluster
+### 🔹 Join Existing Cluster
 
-Add a node to an existing Docker Swarm cluster:
 ```bash
 docker swarm join
 ```
 
-### Leave Cluster
+### 🔹 Leave Cluster
 
-Remove a node from the cluster:
 ```bash
 docker swarm leave
 ```
 
-### Unlock Locked Manager
+### 🔹 Unlock a Manager Node
 
-Unlock a manager node that has been locked:
 ```bash
 docker swarm unlock
 ```
 
 ---
 
-## Node Management
+## 🖥️ Node Management
 
-### List Nodes
+### 🔸 List Nodes
 
-View the status and details of all nodes in your cluster:
 ```bash
 docker node ls
 ```
+
 **Example Output:**
+
 ```
 ID                            HOSTNAME   STATUS    AVAILABILITY   MANAGER STATUS   ENGINE VERSION
 8yw8jrjeqczaci0qkuy060g09 *   docker-1   Ready     Active         Leader           24.0.5
@@ -92,101 +88,141 @@ kd3ujmt1ey3pw6v9189fouxfa     docker-3   Ready     Active         Reachable
 tm1msy58ztcltt36rs1lb76p7     docker-4   Down      Active                          24.0.5
 ```
 
-### Remove Node
+### 🔸 Remove a Node
 
-Remove a node from the cluster by specifying its ID:
 ```bash
 docker node rm <node-id>
 ```
-**Example:**
+
+### 🔸 Promote to Manager
+
 ```bash
-docker node rm tm1msy58ztcltt36rs1lb76p7
+docker node promote <hostname-or-id>
 ```
 
-### Promote Node to Manager
+### 🔸 Inspect a Node
 
-Upgrade a worker node to a manager node:
 ```bash
-docker node promote <hostname or ID>
+docker node inspect <nodename>
 ```
-**Example:**
+
+### 🔸 Change Node Role
+
 ```bash
-docker node promote v4gvf7xenw0izmxgvhr6hb2rj
+docker node update --role manager <nodename>
+docker node update --role worker <nodename>
+```
+
+### 🔸 Change Node Availability
+
+```bash
+docker node update --availability active <nodename>
+docker node update --availability pause <nodename>
+docker node update --availability drain <nodename>
+```
+
+### 🔸 Add or Remove Labels
+
+**Add:**
+
+```bash
+docker node update --label-add env=development <nodename>
+docker node update --label-add env=testing <nodename>
+```
+
+**Remove:**
+
+```bash
+docker node update --label-rm env= <nodename>
+docker node update --label-rm env <nodename>
+```
+
+**Use label constraints in service deployment:**
+
+```yaml
+deploy:
+  placement:
+    constraints:
+      - node.labels.env == development
 ```
-This command promotes the specified node, enabling it to participate in cluster management decisions.
 
 ---
 
-## Service Management
+## 🛠️ Service Management
 
-### Show Task Status on Cluster
+### 🔹 Show Tasks on a Node
 
-Display the status of tasks running on each node:
 ```bash
 docker node ps
 ```
 
-### List Services
+### 🔹 List All Services
 
-List all services currently running in the cluster:
 ```bash
 docker service ls
 ```
 
-### Create Service
+### 🔹 Create a New Service
 
-Create a new service with the specified name and Docker image:
 ```bash
 docker service create --name <service-name> <image-name>
 ```
 
-### Scale Service
+### 🔹 Scale a Service
 
-Adjust the number of replicas for an existing service:
 ```bash
 docker service scale <service-name>=<replica-count>
 ```
+
 **Example:**
+
 ```bash
 docker service scale nginx=5
 ```
-This command scales the `nginx` service to 5 replicas.
 
-### Inspect Service
+### 🔹 Inspect a Service
 
-View detailed information about a specific service:
 ```bash
 docker service inspect <service-name>
 ```
 
-### Create Service with Replicas and Environment Variables
+### 🔹 Create Service with Replicas, Env Vars, and Port Mapping
 
-Launch a new service with multiple replicas, environment variables, and port publishing:
 ```bash
-docker service create --name <service-name> --replicas <replica-count> --env <env-variable> --publish <host-port>:<container-port> <image-name>
+docker service create \
+  --name <service-name> \
+  --replicas <count> \
+  --env <ENV_VAR=value> \
+  --publish <host-port>:<container-port> \
+  <image-name>
 ```
+
 **Example:**
+
 ```bash
-docker service create --name nginx --replicas 3 --env MY_ENV_VAR=value --publish 8080:80 nginx
+docker service create \
+  --name nginx \
+  --replicas 3 \
+  --env MY_ENV_VAR=value \
+  --publish 8080:80 \
+  nginx
 ```
-This creates an `nginx` service with 3 replicas, sets the environment variable `MY_ENV_VAR` to `value`, and maps port 8080 on the host to port 80 in the container.
 
 ---
 
-## Join Tokens
+## 🔑 Join Tokens & Node Configuration
 
-To securely add new nodes to the swarm, use the join tokens provided by Docker Swarm.
+Securely add nodes to your Swarm using join tokens.
 
-### Get Worker Join Token
+### 🔹 Get Worker Token
 
-Display the token required for a node to join as a worker:
 ```bash
 docker swarm join-token worker
 ```
 
-### Get Manager Join Token
+### 🔹 Get Manager Token
 
-Display the token required for a node to join as a manager:
 ```bash
 docker swarm join-token manager
 ```
+

From 4ef37b9655a1545cda0c8ac4b39997d465afe556 Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Fri, 16 May 2025 15:37:50 +0330
Subject: [PATCH 008/116] Update README.md

---
 README.md | 117 +++++++++++++++++++++++++++++++++++++-----------------
 1 file changed, 80 insertions(+), 37 deletions(-)

diff --git a/README.md b/README.md
index 22d8b10..b07ff94 100755
--- a/README.md
+++ b/README.md
@@ -1,56 +1,99 @@
-# Linux Documents
+# 🐧 Linux Documents
 
-Welcome to the Linux Documents repository! This collection serves as a comprehensive resource for various Linux-related configurations, setups, and management scripts. It is designed to assist system administrators, developers, and enthusiasts in deploying and managing different services and applications on Linux-based systems.
+A curated collection of scripts, configuration files, and guides for managing and configuring Linux-based systems. This personal repository serves as a comprehensive knowledge base to simplify deployment, automation, monitoring, security, and much more.
 
-## Table of Contents
+---
 
-### Configuration Management & Automation
-- [Ansible](https://github.com/RadinPirouz/linux-documents/tree/main/Configuration%20Management%20%26%20Automation/Ansible)
-- [CronJob](https://github.com/RadinPirouz/linux-documents/tree/main/Configuration%20Management%20%26%20Automation/CronJob)
+## 📂 Repository Structure
 
-### Web Development & Frameworks
-- [Django](https://github.com/RadinPirouz/linux-documents/tree/main/Web%20Development%20%26%20Frameworks/Django)
-- [LaravelAPI](https://github.com/RadinPirouz/linux-documents/tree/main/Web%20Development%20%26%20Frameworks/LaravelAPI)
-- [LaravelOnNginx](https://github.com/RadinPirouz/linux-documents/tree/main/Web%20Development%20%26%20Frameworks/LaravelOnNginx)
+### ⚙️ Configuration Management & Automation
+- [Ansible](./Configuration%20Management%20&%20Automation/Ansible)
+- [CronJob](./Configuration%20Management%20&%20Automation/CronJob)
 
-### Containerization & Orchestration
-- [Docker](https://github.com/RadinPirouz/linux-documents/tree/main/Containerization%20%26%20Orchestration/Docker)
-- [Kubernetes](https://github.com/RadinPirouz/linux-documents/tree/main/Containerization%20%26%20Orchestration/Kubernetes)
+### 🐳 Containerization & Orchestration
+- [Docker](./Containerization%20&%20Orchestration/Docker)
+- [Kubernetes](./Containerization%20&%20Orchestration/Kubernetes)
 
-### Monitoring & Logging
-- [Grafana](https://github.com/RadinPirouz/linux-documents/tree/main/Monitoring%20%26%20Logging/Grafana)
-- [Librenms](https://github.com/RadinPirouz/linux-documents/tree/main/Monitoring%20%26%20Logging/Librenms)
-- [Netdata](https://github.com/RadinPirouz/linux-documents/tree/main/Monitoring%20%26%20Logging/Netdata)
-- [Zabbix](https://github.com/RadinPirouz/linux-documents/tree/main/Monitoring%20%26%20Logging/Zabbix)
+### 🗄️ Databases
+- [Postgresql](./Databases/Postgresql)
 
-### Networking & Security
-- [Iptables](https://github.com/RadinPirouz/linux-documents/tree/main/Networking%20%26%20Security/Iptables)
-- [Nmap](https://github.com/RadinPirouz/linux-documents/tree/main/Networking%20%26%20Security/Nmap)
-- [Nginx](https://github.com/RadinPirouz/linux-documents/tree/main/Networking%20%26%20Security/Nginx)
-- [FileSharing](https://github.com/RadinPirouz/linux-documents/tree/main/Networking%20%26%20Security/FileSharing)
+### ⚡ Caching
+- [Redis](./Caching/redis)
 
-### Bots & Automation Tools
-- [TelegramBot](https://github.com/RadinPirouz/linux-documents/tree/main/Bots%20%26%20Automation%20Tools/TelegramBot)
+### 💻 Code Management
+- [Git](./Code%20Management/Git)
 
-### System Management
-- [Kernel](https://github.com/RadinPirouz/linux-documents/tree/main/System%20Management/Kernel)
+### 🔀 High Availability
+- [Ha-Proxy](./High%20Availability/Ha-Proxy)
 
-### Miscellaneous
-- [Info](https://github.com/RadinPirouz/linux-documents/tree/main/Miscellaneous/Info)
+### 📊 Monitoring & Logging
+- [Grafana](./Monitoring%20&%20Logging/Grafana)
+- [Librenms](./Monitoring%20&%20Logging/Librenms)
+- [Netdata](./Monitoring%20&%20Logging/Netdata)
+- [Zabbix](./Monitoring%20&%20Logging/Zabbix)
 
-## Getting Started
+### 🔐 Networking & Security
+- [iptables](./Security%20&%20Networking/Iptables)
+- [Nmap](./Security%20&%20Networking/Nmap)
+- [Nginx](./Security%20&%20Networking/Nginx)
+- [FileSharing](./Security%20&%20Networking/FileSharing)
 
-To get started, navigate to the corresponding directory and follow the instructions provided in the README or script files. Each directory contains configuration files, setup guides, and examples to help you implement and manage the specific service or tool.
+### 📦 Storage
+- [NFS](./Storage/NFS)
 
-## Contributing
+### 🧠 System & Kernel Management
+- [Kernel](./System%20&%20Kernel%20Management/Kernel)
 
-We welcome contributions! If you have improvements, bug fixes, or additional configurations to share, please fork the repository and submit a pull request. Follow the existing structure and provide clear documentation for any new additions.
+### 🌐 Web Development & Frameworks
+- [Django](./Web%20Development%20&%20Frameworks/Django)
+- [Laravel API Setup](./Web%20Development%20&%20Frameworks/LaravelAPI)
+- [Laravel on Nginx](./Web%20Development%20&%20Frameworks/LaravelOnNginx)
 
-## Contact
+### 🔁 Web Servers & Reverse Proxies
+- [Nginx](./Web%20Servers%20&%20Reverse%20Proxies/Nginx)
 
-For questions, suggestions, or issues, please open an issue on GitHub or contact the repository owner.
+### 🤖 Bots & Automation Tools
+- [TelegramBot](./Bots%20&%20Automation%20Tools/TelegramBot)
 
-Happy managing!
+### 📝 Miscellaneous
+- [Info](./Info)
 
-[GitHub Repository Link](https://github.com/RadinPirouz/linux-documents)
+---
 
+## 🚀 Getting Started
+
+```bash
+git clone https://github.com/RadinPirouz/linux-documents.git
+cd linux-documents
+```
+
+- Explore each folder for setup guides, scripts, and configuration examples.
+- Follow individual READMEs or documentation inside each directory before running any scripts.
+
+---
+
+## 📌 Notes
+- Tested on **Debian/Ubuntu** and **CentOS/RHEL**-based distributions.
+- Always review and test configurations in a staging environment before applying to production.
+
+---
+
+## 🤝 Contributing
+
+Contributions are welcome! 🛠️
+1. Fork the repository.
+2. Create a new branch (`git checkout -b feature/YourFeature`).
+3. Commit your changes (`git commit -m "Add new config for X"`).
+4. Push to the branch (`git push origin feature/YourFeature`).
+5. Open a Pull Request. 🙌
+
+Please ensure your code is tested and documented.
+---
+
+## 📬 Contact
+
+Questions or feedback? 📫
+- Telegram: [@RadinPirouz](https://t.me/RadinPirouz)
+- GitHub Issues: Open an issue in this repo
+
+⭐ If you find this repository useful, don’t forget to give it a star!

From d761d87e16c2a44689d98b19181d10be606f9f6a Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 28 May 2025 20:18:02 +0330
Subject: [PATCH 009/116] added lpic

---
 Linux/LPIC1/directorys.md | 59 +++++++++++++++++++++++++++++++++++++++
 Linux/LPIC1/runlevels.md  | 59 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 118 insertions(+)
 create mode 100644 Linux/LPIC1/directorys.md
 create mode 100644 Linux/LPIC1/runlevels.md

diff --git a/Linux/LPIC1/directorys.md b/Linux/LPIC1/directorys.md
new file mode 100644
index 0000000..d28cf19
--- /dev/null
+++ b/Linux/LPIC1/directorys.md
@@ -0,0 +1,59 @@
+# 📁 Linux Directory Structure & Basic Commands
+
+This document provides an overview of important Linux directories, their types, and essential file management commands.
+
+---
+
+## 📂 Directory Types
+
+| Type        | Description                                                                         |
+| ----------- | ----------------------------------------------------------------------------------- |
+| **Virtual** | Do not reside on disk; dynamically generated by the system (e.g., `/proc`, `/sys`). |
+| **Normal**  | Standard directories that store files and data on disk.                             |
+
+---
+
+## 🗂️ Common Linux Directories
+
+| Directory | Type    | Description                                                 |
+| --------- | ------- | ----------------------------------------------------------- |
+| `/etc`    | Normal  | System configuration files                                  |
+| `/opt`    | Normal  | Optional or third-party software packages                   |
+| `/bin`    | Normal  | Essential binary executables for all users                  |
+| `/sbin`   | Normal  | System binaries, typically for administrative tasks         |
+| `/lib`    | Normal  | Shared libraries and kernel modules                         |
+| `/home`   | Normal  | User home directories                                       |
+| `/proc`   | Virtual | Kernel and process information (virtual files)              |
+| `/srv`    | Normal  | Data for services provided by the system (e.g., web, FTP)   |
+| `/sys`    | Virtual | Kernel devices and system information                       |
+| `/usr`    | Normal  | Secondary hierarchy: programs, libraries, and documentation |
+| `/var`    | Normal  | Variable data: logs, mail, print spool, temporary files     |
+| `/dev`    | Virtual | Device files (e.g., disk, USB, terminals)                   |
+| `/mnt`    | Normal  | Mount point for temporary filesystems                       |
+| `/boot`   | Normal  | Boot loader files, kernel images                            |
+
+---
+
+## 🛠️ Basic File & Directory Commands
+
+| Command | Description                              |
+| ------- | ---------------------------------------- |
+| `cd`    | Change directory                         |
+| `ls`    | List directory contents                  |
+| `rm`    | Remove files or directories              |
+| `mkdir` | Create a new directory                   |
+| `touch` | Create an empty file or update timestamp |
+| `cp`    | Copy files or directories                |
+| `mv`    | Move or rename files or directories      |
+
+### 📘 Examples
+
+```bash
+cd /etc           # Navigate to /etc directory
+ls -l             # List files in long format
+rm file.txt       # Delete file.txt
+mkdir new_folder  # Create a directory named 'new_folder'
+touch file.txt    # Create a new empty file
+cp file1.txt file2.txt  # Copy file1.txt to file2.txt
+mv file.txt /home/user/ # Move file.txt to another directory
+```
diff --git a/Linux/LPIC1/runlevels.md b/Linux/LPIC1/runlevels.md
new file mode 100644
index 0000000..16eaa31
--- /dev/null
+++ b/Linux/LPIC1/runlevels.md
@@ -0,0 +1,59 @@
+# Linux Runlevels Guide
+
+This document outlines the standard runlevels for **Red Hat** and **Debian**-based systems. Runlevels are used by `init` systems to define different states or modes of operation for the system.
+
+---
+
+## 📊 Runlevels Overview
+
+| Runlevel | Description                          | Red Hat      | Debian          |
+| -------- | ------------------------------------ | ------------ | --------------- |
+| 0        | Halt                                 | ✅ Supported  | ✅ Supported     |
+| 1        | Single User Mode                     | ✅ Supported  | ✅ Supported     |
+| 2        | Multi-user (No Network)              | ❌ (HaveNet)  | ✅ Supported     |
+| 3        | Multi-user (Network, No GUI)         | ✅ Supported  | ✅ Supported     |
+| 4        | Custom/User Defined                  | ✅ Supported  | ✅ Supported     |
+| 5        | Multi-user (GUI Mode) / Halt *(err)* | ❌ (GUI Mode) | ❌ (Halt/Error?) |
+| 6        | Reboot                               | ✅ Supported  | ✅ Supported     |
+
+> 💡 **Note**:
+>
+> * On **Red Hat**, runlevel 5 typically starts the system with a graphical user interface (GUI).
+> * On **Debian**, runlevel 5 is often unused or reserved for custom setups.
+> * Runlevel behavior can be customized depending on system configuration.
+
+---
+
+## 🔧 Commands
+
+### Check Current Runlevel
+
+```bash
+runlevel
+```
+
+### Change Runlevel
+
+```bash
+telinit <runlevel>
+```
+
+or
+
+```bash
+init <runlevel>
+```
+
+> ⚠️ Changing runlevels may stop or restart services. Use with caution, especially on production systems.
+
+---
+
+## 📚 Additional Tips
+
+* Modern Linux systems (especially systemd-based) may not rely on traditional runlevels. Instead, they use *targets*. Example:
+
+  ```bash
+  systemctl get-default
+  systemctl isolate graphical.target
+  ```
+

From 2ce50f4aa9bc9c5fb2fc1a462e05f657fa8a6ccf Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 28 May 2025 21:44:45 +0330
Subject: [PATCH 010/116] added apt doc

---
 Linux/LPIC1/1-runlevels.md                    | 84 +++++++++++++++++++
 .../LPIC1/{directorys.md => 2-directorys.md}  |  0
 Linux/LPIC1/3-package-managers.md             | 75 +++++++++++++++++
 Linux/LPIC1/runlevels.md                      | 59 -------------
 4 files changed, 159 insertions(+), 59 deletions(-)
 create mode 100644 Linux/LPIC1/1-runlevels.md
 rename Linux/LPIC1/{directorys.md => 2-directorys.md} (100%)
 create mode 100644 Linux/LPIC1/3-package-managers.md
 delete mode 100644 Linux/LPIC1/runlevels.md

diff --git a/Linux/LPIC1/1-runlevels.md b/Linux/LPIC1/1-runlevels.md
new file mode 100644
index 0000000..876423d
--- /dev/null
+++ b/Linux/LPIC1/1-runlevels.md
@@ -0,0 +1,84 @@
+# 🐧 Linux Runlevels Guide
+
+This guide provides a concise overview of traditional **runlevels** in Linux systems, particularly for **Red Hat** and **Debian**-based distributions. Runlevels define specific states of system operation, historically managed by the `init` system.
+
+---
+
+## 🔄 System Boot Sequence
+
+```plaintext
+BIOS → Bootloader → Kernel → init
+```
+
+* **BIOS**: Performs hardware checks via **POST** (Power-On Self Test).
+* **Bootloader**: Loads the kernel.
+* **Kernel**: Initializes system and mounts the root filesystem.
+* **init**: Launches system processes based on the selected runlevel.
+
+---
+
+## 📊 Runlevels Comparison
+
+| Runlevel | Description                         | Red Hat          | Debian          |
+| -------- | ----------------------------------- | ---------------- | --------------- |
+| 0        | Halt / Shutdown                     | ✅ Supported      | ✅ Supported     |
+| 1        | Single-User Mode                    | ✅ Supported      | ✅ Supported     |
+| 2        | Multi-User (No Network)             | ❌ (Includes Net) | ✅ Supported     |
+| 3        | Multi-User (Network, No GUI)        | ✅ Supported      | ✅ Supported     |
+| 4        | User-Defined / Custom               | ✅ Supported      | ✅ Supported     |
+| 5        | GUI Mode / *(Halt on some systems)* | ✅ GUI Mode       | ⚠️ Custom/Halt? |
+| 6        | Reboot                              | ✅ Supported      | ✅ Supported     |
+
+> 💡 **Notes**:
+> • **Runlevel 5** on Red Hat typically launches a full graphical environment (GUI).
+> • On Debian, runlevels 2–5 are often configured identically and can be customized.
+> • Runlevel behavior is configurable via `/etc/inittab` (SysVinit systems).
+
+---
+
+## 🔧 Useful Commands
+
+### ✅ Check Current Runlevel
+
+```bash
+runlevel
+```
+
+### 🔁 Change Runlevel
+
+```bash
+telinit <runlevel>
+```
+
+or
+
+```bash
+init <runlevel>
+```
+
+> ⚠️ **Caution**: Switching runlevels may stop services or terminate user sessions. Use carefully on production systems.
+
+---
+
+## 🚀 Modern Systems: systemd Targets
+
+Most modern Linux distributions use **systemd**, which replaces runlevels with **targets**.
+
+| Runlevel | systemd Target      |
+| -------- | ------------------- |
+| 0        | `poweroff.target`   |
+| 1        | `rescue.target`     |
+| 3        | `multi-user.target` |
+| 5        | `graphical.target`  |
+| 6        | `reboot.target`     |
+
+### 📌 Common systemd Commands
+
+```bash
+# Show default target
+systemctl get-default
+
+# Change to graphical mode
+systemctl isolate graphical.target
+```
+
diff --git a/Linux/LPIC1/directorys.md b/Linux/LPIC1/2-directorys.md
similarity index 100%
rename from Linux/LPIC1/directorys.md
rename to Linux/LPIC1/2-directorys.md
diff --git a/Linux/LPIC1/3-package-managers.md b/Linux/LPIC1/3-package-managers.md
new file mode 100644
index 0000000..88b7c2d
--- /dev/null
+++ b/Linux/LPIC1/3-package-managers.md
@@ -0,0 +1,75 @@
+# 📦 Linux Libraries & Package Management
+
+This guide provides a quick overview of **library types**, **package sources**, and **Debian-based package management** commands using `apt`.
+
+---
+
+## 📚 Library Types
+
+Linux supports two main types of libraries:
+
+1. **Static Libraries (`.a`)**  
+   - Linked at **compile-time**  
+   - Included in the final binary  
+   - Larger file size, faster execution
+
+2. **Shared Libraries (`.so`)**  
+   - Linked at **run-time**  
+   - Saved separately from the binary  
+   - Saves space and allows updates without recompiling
+
+---
+
+## 📦 Package Sources
+
+### ✅ Official Packages  
+Provided and maintained by the distribution (e.g., Debian, Ubuntu, Red Hat).
+
+### 🌐 Third-Party Packages  
+Created by external developers or organizations. Use with caution and verify trustworthiness.
+
+---
+
+## 🏬 Linux Package Managers
+
+### 📦 Debian-based Systems
+- **Package Manager**: `apt`
+- **Low-level Tool**: `dpkg`
+- **Package Format**: `.deb`
+
+### 📦 Red Hat-based Systems
+- **Package Manager**: `yum` or `dnf` (newer)
+- **Low-level Tool**: `rpm`
+- **Package Format**: `.rpm`
+
+---
+
+## 🌍 Package Mirrors
+
+Mirrors are alternative download sources for package repositories, often closer geographically for faster updates.
+
+To sync with package mirrors and get the latest updates:
+
+```bash
+sudo apt update
+```
+
+---
+
+## 🔧 Common `apt` Commands
+
+| Command                  | Description                           |
+|--------------------------|---------------------------------------|
+| `apt update`             | Refresh package lists                 |
+| `apt upgrade`            | Upgrade all installed packages        |
+| `apt list`               | List packages                         |
+| `apt show <package>`     | Show details of a package             |
+| `apt install <package>`  | Install a new package                 |
+| `apt reinstall <package>`| Reinstall an existing package         |
+| `apt remove <package>`   | Remove a package (keep config files)  |
+| `apt purge <package>`    | Remove package **and** config files   |
+| `apt-cache search <term>`| Search for a package                  |
+| `apt autoremove`         | Remove unused dependencies            |
+
+> 🔐 Use `sudo` before these commands when required.
+
diff --git a/Linux/LPIC1/runlevels.md b/Linux/LPIC1/runlevels.md
deleted file mode 100644
index 16eaa31..0000000
--- a/Linux/LPIC1/runlevels.md
+++ /dev/null
@@ -1,59 +0,0 @@
-# Linux Runlevels Guide
-
-This document outlines the standard runlevels for **Red Hat** and **Debian**-based systems. Runlevels are used by `init` systems to define different states or modes of operation for the system.
-
----
-
-## 📊 Runlevels Overview
-
-| Runlevel | Description                          | Red Hat      | Debian          |
-| -------- | ------------------------------------ | ------------ | --------------- |
-| 0        | Halt                                 | ✅ Supported  | ✅ Supported     |
-| 1        | Single User Mode                     | ✅ Supported  | ✅ Supported     |
-| 2        | Multi-user (No Network)              | ❌ (HaveNet)  | ✅ Supported     |
-| 3        | Multi-user (Network, No GUI)         | ✅ Supported  | ✅ Supported     |
-| 4        | Custom/User Defined                  | ✅ Supported  | ✅ Supported     |
-| 5        | Multi-user (GUI Mode) / Halt *(err)* | ❌ (GUI Mode) | ❌ (Halt/Error?) |
-| 6        | Reboot                               | ✅ Supported  | ✅ Supported     |
-
-> 💡 **Note**:
->
-> * On **Red Hat**, runlevel 5 typically starts the system with a graphical user interface (GUI).
-> * On **Debian**, runlevel 5 is often unused or reserved for custom setups.
-> * Runlevel behavior can be customized depending on system configuration.
-
----
-
-## 🔧 Commands
-
-### Check Current Runlevel
-
-```bash
-runlevel
-```
-
-### Change Runlevel
-
-```bash
-telinit <runlevel>
-```
-
-or
-
-```bash
-init <runlevel>
-```
-
-> ⚠️ Changing runlevels may stop or restart services. Use with caution, especially on production systems.
-
----
-
-## 📚 Additional Tips
-
-* Modern Linux systems (especially systemd-based) may not rely on traditional runlevels. Instead, they use *targets*. Example:
-
-  ```bash
-  systemctl get-default
-  systemctl isolate graphical.target
-  ```
-

From a7509c6285a99de4ed2671633bb0edbdac41944f Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Tue, 3 Jun 2025 14:30:55 +0330
Subject: [PATCH 011/116] dpkg doc

---
 Code Management/Git/Gitlab/Gitlab-CI/1.md     |  0
 .../Git/Gitlab/Gitlab-CI/gitlab-ci.yaml       | 25 +++++
 Linux/LPIC1/4-dpkg.md                         | 94 +++++++++++++++++++
 3 files changed, 119 insertions(+)
 create mode 100644 Code Management/Git/Gitlab/Gitlab-CI/1.md
 create mode 100644 Code Management/Git/Gitlab/Gitlab-CI/gitlab-ci.yaml
 create mode 100644 Linux/LPIC1/4-dpkg.md

diff --git a/Code Management/Git/Gitlab/Gitlab-CI/1.md b/Code Management/Git/Gitlab/Gitlab-CI/1.md
new file mode 100644
index 0000000..e69de29
diff --git a/Code Management/Git/Gitlab/Gitlab-CI/gitlab-ci.yaml b/Code Management/Git/Gitlab/Gitlab-CI/gitlab-ci.yaml
new file mode 100644
index 0000000..8ae436c
--- /dev/null
+++ b/Code Management/Git/Gitlab/Gitlab-CI/gitlab-ci.yaml	
@@ -0,0 +1,25 @@
+job1:
+  stage: hello_stage
+  script: echo "Hi :)"
+
+job2:
+  stage: hello_stage
+  script: echo "Hello :)"
+
+job3:
+  stage: hello_stage
+  script: echo "How Are You :)"
+  needs:
+    - job2
+
+Build_job1:
+  stage: build_stage
+  script: echo "Building Code"
+  needs:
+    - job3
+  tags:
+    - build_runner
+
+stages:
+  - hello_stage
+  - build_stage
\ No newline at end of file
diff --git a/Linux/LPIC1/4-dpkg.md b/Linux/LPIC1/4-dpkg.md
new file mode 100644
index 0000000..7537c59
--- /dev/null
+++ b/Linux/LPIC1/4-dpkg.md
@@ -0,0 +1,94 @@
+
+# 📦 `dpkg` – Debian Package Manager
+
+`dpkg` is the package manager for Debian-based Linux distributions. It is used to install, remove, and manage `.deb` packages directly.
+
+### 📘 Basic Syntax
+
+```bash
+dpkg [<option>...] <command>
+```
+
+---
+
+## 🌐 Finding Packages
+
+You can browse and search for Debian packages at [pkgs.org](https://pkgs.org).
+
+---
+
+## 📋 Listing Installed Packages
+
+```bash
+dpkg -l
+dpkg --list
+```
+
+---
+
+## 📥 Installing a Package
+
+```bash
+dpkg -i <package.deb>
+dpkg --install <package.deb>
+```
+
+> ⚠️ If there are missing dependencies, run:
+
+```bash
+apt install -f
+```
+
+---
+
+## 📂 Viewing Package Contents
+
+```bash
+dpkg -c <package.deb>
+dpkg --contents <package.deb>
+```
+
+---
+
+## ℹ️ Getting Package Info
+
+```bash
+dpkg -I <package.deb>
+dpkg --info <package.deb>
+```
+
+---
+
+## 📁 Listing Installed Files
+
+```bash
+dpkg -L <package-name>
+dpkg --listfiles <package-name>
+```
+
+---
+
+## 🧹 Removing a Package (and its config files)
+
+```bash
+dpkg -p <package-name>
+dpkg --purge <package-name>
+```
+
+---
+
+## 📝 Checking Package Status
+
+```bash
+dpkg -s <package-name>
+dpkg --status <package-name>
+```
+
+---
+
+## 🔧 Reconfiguring a Package
+
+```bash
+dpkg-reconfigure <package-name>
+```
+

From ac1d0dfdebf8ea02352151d4d31f451e4dab7fe4 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 4 Jun 2025 18:30:20 +0330
Subject: [PATCH 012/116] apt\ doc

---
 Linux/LPIC1/3-package-managers.md |  26 ------
 Linux/LPIC1/5-apt.md              | 148 ++++++++++++++++++++++++++++++
 Linux/LPIC1/6-yum.md              |   0
 3 files changed, 148 insertions(+), 26 deletions(-)
 create mode 100644 Linux/LPIC1/5-apt.md
 create mode 100644 Linux/LPIC1/6-yum.md

diff --git a/Linux/LPIC1/3-package-managers.md b/Linux/LPIC1/3-package-managers.md
index 88b7c2d..173d7ba 100644
--- a/Linux/LPIC1/3-package-managers.md
+++ b/Linux/LPIC1/3-package-managers.md
@@ -47,29 +47,3 @@ Created by external developers or organizations. Use with caution and verify tru
 ## 🌍 Package Mirrors
 
 Mirrors are alternative download sources for package repositories, often closer geographically for faster updates.
-
-To sync with package mirrors and get the latest updates:
-
-```bash
-sudo apt update
-```
-
----
-
-## 🔧 Common `apt` Commands
-
-| Command                  | Description                           |
-|--------------------------|---------------------------------------|
-| `apt update`             | Refresh package lists                 |
-| `apt upgrade`            | Upgrade all installed packages        |
-| `apt list`               | List packages                         |
-| `apt show <package>`     | Show details of a package             |
-| `apt install <package>`  | Install a new package                 |
-| `apt reinstall <package>`| Reinstall an existing package         |
-| `apt remove <package>`   | Remove a package (keep config files)  |
-| `apt purge <package>`    | Remove package **and** config files   |
-| `apt-cache search <term>`| Search for a package                  |
-| `apt autoremove`         | Remove unused dependencies            |
-
-> 🔐 Use `sudo` before these commands when required.
-
diff --git a/Linux/LPIC1/5-apt.md b/Linux/LPIC1/5-apt.md
new file mode 100644
index 0000000..20fb4a7
--- /dev/null
+++ b/Linux/LPIC1/5-apt.md
@@ -0,0 +1,148 @@
+# 📦 Managing Packages with `apt` on Debian/Ubuntu
+
+The `apt` (Advanced Package Tool) command-line utility allows you to manage software on Debian-based Linux systems. Below are essential `apt` commands grouped by purpose, with clear explanations for each.
+
+---
+
+## 🔄 1. Updating and Upgrading the System
+
+### `sudo apt update`
+
+Fetches the latest package lists from repositories. This ensures your system is aware of the newest available versions of packages.
+
+```bash
+sudo apt update
+```
+
+---
+
+### `apt upgrade`
+
+Installs the newest versions of all installed packages based on the updated package lists. It does **not** remove or install any other packages.
+
+```bash
+apt upgrade
+```
+
+---
+
+## 🔍 2. Searching and Viewing Packages
+
+### `apt show <package>`
+
+Displays detailed information about a specific package, including version, dependencies, description, and more.
+
+```bash
+apt show <package>
+```
+
+---
+
+### `apt list`
+
+Lists packages based on various filters (e.g., installed, upgradable, available). Running it without arguments shows all packages.
+
+```bash
+apt list
+```
+
+---
+
+### `apt-cache search <pkg name>`
+
+Searches the package cache for packages matching the given name or description. Useful for discovering packages related to a topic or function.
+
+```bash
+apt-cache search <pkg name>
+```
+
+---
+
+## 📥 3. Installing and Reinstalling Packages
+
+### `apt install <pkg name>`
+
+Installs a package and its dependencies from the repositories.
+
+```bash
+apt install <pkg name>
+```
+
+---
+
+### `apt reinstall <package>`
+
+Reinstalls the specified package. This is useful if files from a package are accidentally deleted or corrupted.
+
+```bash
+apt reinstall <package>
+```
+
+---
+
+## ❌ 4. Removing Packages
+
+### `apt remove <package>`
+
+Removes the specified package but **retains configuration files**. Useful when planning to reinstall later without losing settings.
+
+```bash
+apt remove <package>
+```
+
+---
+
+### `apt purge <package>`
+
+Completely removes the package **along with its configuration files**. Use when you want a clean uninstallation.
+
+```bash
+apt purge <package>
+```
+
+---
+
+### `apt autoremove`
+
+Automatically removes packages that were installed as dependencies but are no longer needed.
+
+```bash
+apt autoremove
+```
+
+---
+
+## 🛠️ 5. Advanced Package Handling
+
+### `apt install -f`
+
+Attempts to **fix broken dependencies** by installing missing packages. Often used after a failed install.
+
+```bash
+apt install -f
+```
+
+---
+
+### `apt install --download-only <package>`
+
+Downloads a package without installing it. The downloaded `.deb` files are saved in:
+
+```bash
+/var/cache/apt/archives/
+```
+
+Example:
+
+```bash
+apt install --download-only <package>
+```
+
+---
+
+## ✅ Final Notes
+
+* Always start with `sudo apt update` before any install or upgrade.
+* Use `apt-cache search` when unsure of a package’s exact name.
+* Be cautious with `purge` as it deletes config files too.
+
diff --git a/Linux/LPIC1/6-yum.md b/Linux/LPIC1/6-yum.md
new file mode 100644
index 0000000..e69de29

From c33a3bf102340b2f19c4655db3a754549dcbb3db Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 4 Jun 2025 18:49:05 +0330
Subject: [PATCH 013/116] yum doc

---
 Linux/LPIC1/6-yum.md | 156 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 156 insertions(+)

diff --git a/Linux/LPIC1/6-yum.md b/Linux/LPIC1/6-yum.md
index e69de29..ef64081 100644
--- a/Linux/LPIC1/6-yum.md
+++ b/Linux/LPIC1/6-yum.md
@@ -0,0 +1,156 @@
+# 🍽️ Managing Packages with `yum` on RHEL/CentOS
+
+`yum` (Yellowdog Updater, Modified) is the traditional package manager for RPM-based Linux distributions such as **Red Hat Enterprise Linux (RHEL)** and **CentOS**. Below is a breakdown of commonly used `yum` commands, categorized and explained in detail.
+
+---
+
+## 🔄 1. Updating the System
+
+### `yum update`
+
+Fetches the latest package metadata and installs available updates for all packages currently installed on the system.
+
+```bash
+yum update
+```
+
+---
+
+### `yum upgrade`
+
+Performs the same function as `yum update`. In older versions of `yum`, `upgrade` was used for more aggressive upgrades, but in recent versions, they are functionally equivalent.
+
+```bash
+yum upgrade
+```
+
+---
+
+## 📥 2. Installing and Reinstalling Packages
+
+### `yum install <pkg-name>`
+
+Installs a new package along with any required dependencies.
+
+```bash
+yum install <pkg-name>
+```
+
+---
+
+### `yum reinstall <pkg-name>`
+
+Reinstalls an already installed package, which is useful if system files have been corrupted or modified.
+
+```bash
+yum reinstall <pkg-name>
+```
+
+---
+
+### `yum localinstall <file-dir>`
+
+Installs a `.rpm` package from a local file path while resolving dependencies using remote repositories.
+
+```bash
+yum localinstall <file-dir>
+```
+
+---
+
+## ❌ 3. Removing Packages
+
+### `yum remove <pkg-name>`
+
+Uninstalls the specified package from the system, including any dependencies no longer required.
+
+```bash
+yum remove <pkg-name>
+```
+
+---
+
+## 🔍 4. Querying and Searching
+
+### `yum list`
+
+Lists all available, installed, and updatable packages.
+
+```bash
+yum list
+```
+
+---
+
+### `yum info <pkg>`
+
+Displays detailed information about the specified package, including version, repository, summary, and description.
+
+```bash
+yum info <pkg>
+```
+
+---
+
+### `yum search`
+
+Searches for a keyword in package names and descriptions. Add the search term to complete the command.
+
+```bash
+yum search <keyword>
+```
+
+Example:
+
+```bash
+yum search python
+```
+
+---
+
+### `yum deplist <pkg>`
+
+Shows the list of dependencies for a given package.
+
+```bash
+yum deplist <pkg>
+```
+
+---
+
+## 🕓 5. Package History and Transactions
+
+### `yum history`
+
+Displays a history of all yum transactions (installs, updates, removals), which can be reviewed or undone if needed.
+
+```bash
+yum history
+```
+
+---
+
+## 💾 6. Downloading Packages (Without Installing)
+
+### `yum download <pkg>`
+
+Downloads an RPM package file without installing it. Useful for transferring or offline installations. Requires the `yum-utils` package.
+
+```bash
+yum download <pkg>
+```
+
+> 💡 **Note:** If you get an error, try installing `yum-utils`:
+>
+> ```bash
+> yum install yum-utils
+> ```
+
+---
+
+## ✅ Final Notes
+
+* `yum` has been replaced by `dnf` in newer distributions (e.g., RHEL 8+), but still widely used in older systems.
+* Always run `yum update` before installing new packages.
+* Combine with `yum history` to review or undo changes when troubleshooting.
+

From d239ea3cde3e5370e79a7a5453566ea27455e9ef Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 4 Jun 2025 18:57:22 +0330
Subject: [PATCH 014/116] rpm doc

---
 Linux/LPIC1/7-rpm.md       | 172 +++++++++++++++++++++++++++++++++++++
 Linux/LPIC1/8-setup-ssh.md |   0
 2 files changed, 172 insertions(+)
 create mode 100644 Linux/LPIC1/7-rpm.md
 create mode 100644 Linux/LPIC1/8-setup-ssh.md

diff --git a/Linux/LPIC1/7-rpm.md b/Linux/LPIC1/7-rpm.md
new file mode 100644
index 0000000..9d5ce28
--- /dev/null
+++ b/Linux/LPIC1/7-rpm.md
@@ -0,0 +1,172 @@
+# 📦 Managing Packages with `rpm` on RHEL/CentOS
+
+The `rpm` command (RPM Package Manager) is the **low-level package management tool** used on **Red Hat-based** systems such as RHEL, CentOS, Fedora, and others. Unlike `yum`, `rpm` does not resolve dependencies automatically and is best used for advanced or manual package management.
+
+Below are the core `rpm` commands categorized and explained.
+
+---
+
+## 📥 1. Installing Packages
+
+### `rpm -i <file.rpm>`
+
+### `rpm --install <file.rpm>`
+
+Installs a new `.rpm` package file. This command will **fail if the package's dependencies are not already installed**.
+
+```bash
+rpm -i <file.rpm>
+```
+
+or
+
+```bash
+rpm --install <file.rpm>
+```
+
+> 💡 Tip: Use `yum localinstall` or `dnf install` instead for dependency resolution.
+
+---
+
+## 🔄 2. Upgrading Packages
+
+### `rpm -U <file.rpm>`
+
+### `rpm --upgrade <file.rpm>`
+
+Upgrades an existing package if it is already installed. If the package is not already present, this command will install it.
+
+```bash
+rpm -U <file.rpm>
+```
+
+or
+
+```bash
+rpm --upgrade <file.rpm>
+```
+
+---
+
+## ❌ 3. Removing Packages
+
+### `rpm -e <package>`
+
+### `rpm --erase <package>`
+
+Removes a package from the system by name (not the filename). Note that this command also does **not resolve dependencies**, so it may break things if you're not careful.
+
+```bash
+rpm -e <package>
+```
+
+or
+
+```bash
+rpm --erase <package>
+```
+
+> ⚠️ Caution: Always check what depends on a package before removing it.
+
+---
+
+## 🔍 4. Querying Packages
+
+### `rpm -q <package>`
+
+Query whether a package is installed, and show its version.
+
+```bash
+rpm -q <package>
+```
+
+---
+
+### `rpm -qa`
+
+List **all installed packages**.
+
+```bash
+rpm -qa
+```
+
+---
+
+### `rpm -qi <package>`
+
+Displays detailed **information** about a specific installed package.
+
+```bash
+rpm -qi <package>
+```
+
+---
+
+### `rpm -ql <package>`
+
+Lists all files installed by a package.
+
+```bash
+rpm -ql <package>
+```
+
+---
+
+### `rpm -qf <file>`
+
+Finds out **which package** owns a specific file.
+
+```bash
+rpm -qf /usr/bin/wget
+```
+
+---
+
+### `rpm -qp <file.rpm>`
+
+Query a package file (without installing it) to see its metadata.
+
+```bash
+rpm -qp <file.rpm>
+```
+
+---
+
+### `rpm -K <file.rpm>`
+
+Verifies the **signature and integrity** of an RPM package file.
+
+```bash
+rpm -K <file.rpm>
+```
+
+---
+
+## 🛠️ 5. Verifying and Checking
+
+### `rpm -V <package>`
+
+Verifies installed package files against their original metadata (modifications, corruption, etc.).
+
+```bash
+rpm -V <package>
+```
+
+---
+
+### `rpm --test -i <file.rpm>`
+
+Simulates an install without actually installing the package — useful for testing.
+
+```bash
+rpm --test -i <file.rpm>
+```
+
+---
+
+## ✅ Final Notes
+
+* `rpm` is a **powerful low-level tool**, but not recommended for resolving dependencies.
+* For **automated dependency handling**, prefer using `yum` or `dnf`.
+* Use `rpm` when you need precise control over the package management process or are working with standalone `.rpm` files.
+
diff --git a/Linux/LPIC1/8-setup-ssh.md b/Linux/LPIC1/8-setup-ssh.md
new file mode 100644
index 0000000..e69de29

From 1976655ed30f04c4040f584a52fe76e40f86c080 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Wed, 4 Jun 2025 19:08:45 +0330
Subject: [PATCH 015/116] ssh doc

---
 Linux/LPIC1/8-setup-ssh.md | 114 +++++++++++++++++++++++++++++++++++++
 1 file changed, 114 insertions(+)

diff --git a/Linux/LPIC1/8-setup-ssh.md b/Linux/LPIC1/8-setup-ssh.md
index e69de29..b02cde2 100644
--- a/Linux/LPIC1/8-setup-ssh.md
+++ b/Linux/LPIC1/8-setup-ssh.md
@@ -0,0 +1,114 @@
+# 🔐 Secure Shell (SSH) – Remote Access & Management
+
+**SSH (Secure Shell)** is a cryptographic network protocol that allows users to **securely access and control remote machines** over a network. It's a foundational tool for system administrators, developers, and anyone managing remote systems.
+
+---
+
+## 🧠 What SSH Does
+
+* **🔒 Encrypts Communication**
+  All data transmitted between the client and the remote server is encrypted, protecting it from eavesdropping and man-in-the-middle attacks.
+
+* **🧑‍💻 Authenticates Users**
+  Supports both password-based and public key-based authentication to ensure that only authorized users gain access.
+
+* **💻 Enables Remote Command Execution**
+  Run commands on a remote machine as if you're using its terminal directly.
+
+* **📁 Supports Secure File Transfers**
+  Tools like `scp` (Secure Copy) and `sftp` (SSH File Transfer Protocol) allow encrypted file transfers between machines.
+
+---
+
+## 🚀 Installing the SSH Server
+
+To accept SSH connections on a machine, you must install and start the **OpenSSH server**.
+
+### On Debian/Ubuntu systems
+
+```bash
+sudo apt install openssh-server
+```
+
+* This installs the OpenSSH daemon (`sshd`), which listens for incoming SSH connections.
+* To enable and start the service:
+
+```bash
+sudo systemctl enable ssh
+sudo systemctl start ssh
+```
+
+---
+
+### On RHEL/CentOS systems
+
+```bash
+sudo yum install openssh-server
+```
+
+* Start and enable the SSH service:
+
+```bash
+sudo systemctl enable sshd
+sudo systemctl start sshd
+```
+
+---
+
+## 🛠️ Common SSH Usage Examples
+
+### 🔗 Connect to a Remote Server
+
+```bash
+ssh username@remote_host
+```
+
+### 📁 Copy a File to a Remote Server Using `scp`
+
+```bash
+scp file.txt user@remote_host:/path/to/destination/
+```
+
+### 📥 Copy a File from a Remote Server
+
+```bash
+scp user@remote_host:/path/to/file.txt .
+```
+
+### 🗂️ Use Interactive File Transfer with `sftp`
+
+```bash
+sftp user@remote_host
+```
+
+---
+
+## 🔐 Key-Based Authentication (Optional but Recommended)
+
+To use SSH without typing a password every time, you can set up key-based authentication:
+
+1. **Generate SSH key pair on your local machine:**
+
+```bash
+ssh-keygen
+```
+
+2. **Copy the public key to the remote server:**
+
+```bash
+ssh-copy-id user@remote_host
+```
+
+3. Now you can SSH without a password prompt:
+
+```bash
+ssh user@remote_host
+```
+
+---
+
+## ✅ Final Notes
+
+* SSH is a vital tool for managing servers securely.
+* Always **disable root login** and **use key authentication** for better security.
+* You can configure SSH behavior in `/etc/ssh/sshd_config`.

From a02861266961dd552bfbe5db0440f7091471ee33 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 22 Jun 2025 21:59:29 +0330
Subject: [PATCH 016/116] update kuber doc

---
 .../Kubernetes/1-Information.md               |  97 ++++++----
 .../Kubernetes/2-Installtion.md               | 180 +++++++++++++-----
 2 files changed, 194 insertions(+), 83 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/1-Information.md b/Containerization & Orchestration/Kubernetes/1-Information.md
index aca5679..f2b5cc9 100755
--- a/Containerization & Orchestration/Kubernetes/1-Information.md	
+++ b/Containerization & Orchestration/Kubernetes/1-Information.md	
@@ -1,65 +1,82 @@
-# Kubernetes (K8s) Documentation
+# 🚢 Kubernetes (K8s) Documentation
 
-## Overview  
+## 🌐 Overview
 **Kubernetes (K8s)** is an open-source container orchestration platform designed to automate the deployment, scaling, and operation of containerized applications.
 
 ---
 
-## Control Plane (CP)  
-The **Control Plane** is the core management component of a Kubernetes cluster. It makes global decisions about the cluster (e.g., scheduling), and it maintains the desired state of the cluster by managing workloads and directing communication within the system.  
-> **Note:** By default, the Control Plane does not directly manage or run application containers.
+## 🧠 Control Plane (CP)
+The **Control Plane** is the core management component of a Kubernetes cluster. It makes global decisions about the cluster (e.g., scheduling) and maintains the desired state of the cluster by managing workloads and directing communication within the system.
 
-### Key Components of the Control Plane:
-- **API Server (`kube-apiserver`)**:  
-  Exposes the Kubernetes API and serves as the entry point to the cluster. It handles communication between internal components and external clients.
-  
-- **Scheduler (`kube-scheduler`)**:  
-  Assigns work (e.g., pods) to nodes based on resource availability and policies.
+> 💡 **Note:** By default, the Control Plane does not directly manage or run application containers.
 
-- **Controller Manager (`kube-controller-manager`)**:  
-  Runs controllers that regulate the state of the cluster (e.g., Node Controller, Replication Controller, etc.).
+### 🔑 Key Components of the Control Plane
 
-- **etcd**:  
-  A consistent, highly-available key-value store that stores all cluster data, configurations, and states. This is the "database" of Kubernetes.
+- **API Server (`kube-apiserver`)**  
+  Exposes the Kubernetes API and serves as the cluster's entry point. It handles communication between internal components and external clients.
+
+- **Scheduler (`kube-scheduler`)**  
+  Assigns workloads (e.g., Pods) to nodes based on resource availability and defined policies.
+
+- **Controller Manager (`kube-controller-manager`)**  
+  Runs controllers that monitor and regulate the cluster's state, such as the Node Controller and Replication Controller.
+
+- **etcd**  
+  A consistent and highly available key-value store that stores all cluster data, configurations, and state. This is the "database" of Kubernetes.
 
 ---
 
-## Worker Nodes  
-Worker nodes are the machines where containerized applications run. Each worker node contains essential components for managing containers.
+## 🧱 Worker Nodes
+**Worker nodes** are the machines where containerized applications run. Each node contains essential components for managing containers.
 
-### Key Components of a Worker Node:
-- **Kubelet**:  
-  An agent that ensures containers are running as specified in their Pod definitions. It communicates with the Control Plane to receive and execute tasks.
+### 🔧 Key Components of a Worker Node
 
-- **Kube Proxy**:  
-  Maintains network rules and handles routing for communication between services within the cluster and with external traffic.
+- **Kubelet**  
+  An agent that ensures containers run as specified in their Pod definitions. It communicates with the Control Plane to execute assigned tasks.
+
+- **Kube Proxy**  
+  Maintains network rules and manages routing for communication within the cluster and with external systems.
 
 ---
 
-## Data Flow  
-- **Kubelet** and **Kube Proxy** on each worker node communicate with the **API Server** in the Control Plane for task execution and resource updates.
-- The **Scheduler** assigns pods to nodes based on resource requirements, while the **Controller Manager** ensures that the cluster state remains consistent.
+## 🔄 Data Flow
+- **Kubelet** and **Kube Proxy** on each worker node interact with the **API Server** to perform operations and update resource states.
+- The **Scheduler** selects suitable nodes for pod placement based on available resources.
+- The **Controller Manager** ensures the actual state of the cluster matches the desired state.
 
 ---
 
-## Administration Tools  
-- **`kubeadm`**:  
-  A tool for bootstrapping Kubernetes clusters. It simplifies the setup and configuration of the Control Plane and worker nodes.
+## 🛠️ Administration Tools
 
-- **`kubectl`**:  
-  The command-line interface (CLI) for interacting with the Kubernetes API. It is used to manage resources, deploy applications, and inspect cluster components.
+- **`kubeadm`**  
+  A command-line tool to bootstrap and configure Kubernetes clusters. It streamlines the setup of both the Control Plane and worker nodes.
+
+- **`kubectl`**  
+  The CLI for interacting with the Kubernetes API. It's used to deploy apps, inspect cluster resources, and manage configurations.
 
 ---
 
-## Kubernetes Version Compatibility  
-### Kubernetes and Container Runtimes:
-- **Kubernetes ≤ 1.23**:  
-  Compatible with Docker as the default container runtime.
-  
-- **Kubernetes 1.24 to 1.25**:  
-  Docker is not supported as a runtime. These versions require `containerd` or another Container Runtime Interface (CRI) implementation.
-  
-- **Kubernetes ≥ 1.25**:  
-  Docker can be installed on the server but must be used indirectly through `containerd` or another CRI-compliant runtime. Docker itself is not a supported runtime.
+## 🧩 Kubernetes Version Compatibility
 
+### Kubernetes and Container Runtimes
 
+- **Kubernetes ≤ 1.23**  
+  ✅ Compatible with **Docker** as the default container runtime.
+
+- **Kubernetes 1.24 – 1.25**  
+  ❌ Docker is **not supported** directly. Use `containerd` or another CRI-compliant runtime.
+
+- **Kubernetes ≥ 1.25**  
+  ⚠️ Docker may be installed on the system but must be used **indirectly** through `containerd` or another supported CRI.
+
+---
+
+## 👥 Kubernetes Roles
+
+- **Control Plane (Manager)**  
+  Requires an **odd number** of nodes for high availability (e.g., 1, 3, 5, ...). This ensures quorum in distributed consensus.
+
+- **Worker (none)**  
+  These nodes run application workloads and do not participate in control decisions.
+
+---
diff --git a/Containerization & Orchestration/Kubernetes/2-Installtion.md b/Containerization & Orchestration/Kubernetes/2-Installtion.md
index 130dba3..d7fc5b7 100755
--- a/Containerization & Orchestration/Kubernetes/2-Installtion.md	
+++ b/Containerization & Orchestration/Kubernetes/2-Installtion.md	
@@ -1,67 +1,161 @@
+# 🐳 Containerd and Kubernetes Installation Guide
+
+A comprehensive step-by-step guide for setting up a Kubernetes cluster using **Containerd** as the container runtime. This guide is intended for Ubuntu-based systems.
 
 ---
 
-# Containerd and Kubernetes Installation Guide
+## ⚙️ 1. Disable Swap
 
-## 1. Disable Swap
-Turn off swap and disable it permanently.
+Kubernetes requires swap to be disabled for proper scheduling and memory management.
 
 ```bash
-swapoff -a
-sed -i '/swap/d' /etc/fstab
+sudo swapoff -a
+sudo sed -i '/swap/d' /etc/fstab
 ```
-## 2. Enable Required Kernel Modules
-Create a configuration file to load necessary kernel modules and load them temporarily.
+
+---
+
+## 🧩 2. Enable Required Kernel Modules
+
+Load the necessary kernel modules for networking and overlay file systems.
+
 ```bash
-echo -e "overlay\nbr_netfilter" | sudo tee /etc/modules-load.d/containerd.conf
+cat <<EOF | sudo tee /etc/modules-load.d/containerd.conf
+overlay
+br_netfilter
+EOF
+
 sudo modprobe overlay
 sudo modprobe br_netfilter
 ```
-## 3. Enable IPv4 Forwarding
-Enable IPv4 forwarding in the sysctl configuration and apply the changes.
+
+---
+
+## 🌐 3. Enable IPv4 Forwarding
+
+Enable packet forwarding to allow pods to communicate across the network.
+
 ```bash
-sed -i 's/#net.ipv4.ip_forward=1/net.ipv4.ip_forward=1/' /etc/sysctl.conf
-sysctl -p
-```
-## 4. Configure Containerd
-Generate the default configuration for Containerd and modify it to use systemd as the cgroup driver.
-```bash
-containerd config default | sudo tee /etc/containerd/config.toml
-sudo sed -i 's/SystemdCgroup = false/SystemdCgroup = true/' /etc/containerd/config.toml
+sudo tee /etc/sysctl.d/99-kubernetes-cri.conf <<EOF
+net.bridge.bridge-nf-call-iptables  = 1
+net.ipv4.ip_forward                 = 1
+net.bridge.bridge-nf-call-ip6tables = 1
+EOF
+
+sudo sysctl --system
 ```
 
-## 5. Install Kubernetes
-Add the Kubernetes package repository and install the required packages.
+---
+
+## 📦 4. Install and Configure Containerd
+
+Install and configure **Containerd** with `systemd` as the cgroup driver.
+
+```bash
+sudo apt-get update && sudo apt-get install -y containerd
+
+sudo mkdir -p /etc/containerd
+containerd config default | sudo tee /etc/containerd/config.toml
+
+sudo sed -i 's/SystemdCgroup = false/SystemdCgroup = true/' /etc/containerd/config.toml
+
+sudo systemctl restart containerd
+sudo systemctl enable containerd
+```
+
+---
+
+## ⎈ 5. Install Kubernetes Components
+
+Add the Kubernetes repository and install the core components: `kubelet`, `kubeadm`, and `kubectl`.
+
 ```bash
 sudo mkdir -p /etc/apt/keyrings
 curl -fsSL https://pkgs.k8s.io/core:/stable:/v1.30/deb/Release.key | sudo gpg --dearmor -o /etc/apt/keyrings/kubernetes-apt-keyring.gpg
-echo 'deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.30/deb/ /' | sudo tee /etc/apt/sources.list.d/kubernetes.list
+
+echo "deb [signed-by=/etc/apt/keyrings/kubernetes-apt-keyring.gpg] https://pkgs.k8s.io/core:/stable:/v1.30/deb/ /" | sudo tee /etc/apt/sources.list.d/kubernetes.list
+
 sudo apt-get update
 sudo apt-get install -y kubelet kubeadm kubectl
 sudo apt-mark hold kubelet kubeadm kubectl
 ```
-## 6. Enable kubelet
-Enable and start the kubelet service.
-```bash
-sudo systemctl enable --now kubelet
-```
-## 7. Initialize the Kubernetes Cluster
-Initialize the Kubernetes control plane with the specified parameters.
-```bash
-sudo kubeadm init --control-plane-endpoint 192.168.2.100 --apiserver-advertise-address 192.168.2.100 --pod-network-cidr 10.244.0.0/16 | tee kuber-install.log
-```
-## 8. Create Control Plane Join Command
-Create the control plane join command and save it for later use.
-```bash
-sudo kubeadm init phase upload-certs --upload-certs
-
-Copy the output certificate key and run the following command, replacing <CERTIFICATE_KEY> with the copied key.
-
-sudo kubeadm token create --certificate-key <CERTIFICATE_KEY> --print-join-command | tee cp-command.txt
-```
-## 9. Join Control Plane and Worker Nodes
-Use the command from cp-command.txt on your control plane nodes to join them. Additionally, get the join command for worker nodes from kuber-install.log and run it on each worker node.
 
 ---
 
-This revised guide provides clear, step-by-step instructions, making it easier to follow and ensuring all necessary actions are covered.
\ No newline at end of file
+## 🔁 6. Enable Kubelet Service
+
+Start and enable the kubelet to run on system boot.
+
+```bash
+sudo systemctl enable --now kubelet
+```
+
+---
+
+## 🚀 7. Initialize the Kubernetes Control Plane
+
+Initialize the cluster. Replace the IP with your master node's IP address.
+
+```bash
+sudo kubeadm init \
+  --control-plane-endpoint 192.168.2.100 \
+  --apiserver-advertise-address 192.168.2.100 \
+  --pod-network-cidr 10.244.0.0/16 | tee kuber-install.log
+```
+
+---
+
+## 🛠 8. Configure kubectl Access
+
+Set up `kubectl` for the current (non-root) user.
+
+```bash
+mkdir -p $HOME/.kube
+sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
+sudo chown $(id -u):$(id -g) $HOME/.kube/config
+```
+
+---
+
+## 🧾 9. Create Control Plane Join Command
+
+Generate a command for other control plane nodes to join the cluster.
+
+```bash
+sudo kubeadm init phase upload-certs --upload-certs
+```
+
+Copy the **certificate key** from the output above and run:
+
+```bash
+sudo kubeadm token create --certificate-key <CERTIFICATE_KEY> --print-join-command | tee cp-command.txt
+```
+
+Replace `<CERTIFICATE_KEY>` with the actual key.
+
+---
+
+## 🧑‍🤝‍🧑 10. Join Control Plane and Worker Nodes
+
+* **Control Plane Nodes**: Use the command from `cp-command.txt` on each node.
+* **Worker Nodes**: Use the `kubeadm join` command printed at the end of the `kubeadm init` output or found in `kuber-install.log`.
+
+---
+
+## ✅ Final Step: Install a Pod Network Add-on
+
+Choose and apply a pod network add-on (e.g., Flannel, Calico, Cilium). Here's an example with Flannel:
+
+```bash
+kubectl apply -f https://raw.githubusercontent.com/flannel-io/flannel/master/Documentation/kube-flannel.yml
+```
+
+---
+
+🎉 **Your Kubernetes cluster is now up and running!**
+Ensure all nodes are ready by running:
+
+```bash
+kubectl get nodes
+```
+

From b0cf699d745cef5a0c5965e21f71181ed90c755b Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 24 Jun 2025 20:47:06 +0330
Subject: [PATCH 017/116] update kuber to working

---
 .../Kubernetes/1-Information.md               |   3 +-
 .../Kubernetes/3-Commands.md                  | 172 +-----------------
 .../Kubernetes/4-BasicSetup.md                |  13 ++
 .../Kubernetes/components/1-NameSpace.md      |  72 ++++++++
 .../Kubernetes/components/2-Pod.md            |  95 ++++++++++
 .../Kubernetes/components/3-Replicaset.md     |   0
 .../Kubernetes/label.md                       |   9 +
 .../Kubernetes/log-debug.md                   |  27 +++
 .../Kubernetes/node-manage.md                 |  44 +++++
 README.md                                     |   2 +-
 10 files changed, 265 insertions(+), 172 deletions(-)
 create mode 100644 Containerization & Orchestration/Kubernetes/4-BasicSetup.md
 create mode 100644 Containerization & Orchestration/Kubernetes/components/1-NameSpace.md
 create mode 100644 Containerization & Orchestration/Kubernetes/components/2-Pod.md
 create mode 100644 Containerization & Orchestration/Kubernetes/components/3-Replicaset.md
 create mode 100644 Containerization & Orchestration/Kubernetes/label.md
 create mode 100644 Containerization & Orchestration/Kubernetes/log-debug.md
 create mode 100644 Containerization & Orchestration/Kubernetes/node-manage.md

diff --git a/Containerization & Orchestration/Kubernetes/1-Information.md b/Containerization & Orchestration/Kubernetes/1-Information.md
index f2b5cc9..5d6c9c0 100755
--- a/Containerization & Orchestration/Kubernetes/1-Information.md	
+++ b/Containerization & Orchestration/Kubernetes/1-Information.md	
@@ -79,4 +79,5 @@ The **Control Plane** is the core management component of a Kubernetes cluster.
 - **Worker (none)**  
   These nodes run application workloads and do not participate in control decisions.
 
----
+
+image pull policy in kubernetes:
diff --git a/Containerization & Orchestration/Kubernetes/3-Commands.md b/Containerization & Orchestration/Kubernetes/3-Commands.md
index c28e7cf..a0f3ca5 100755
--- a/Containerization & Orchestration/Kubernetes/3-Commands.md	
+++ b/Containerization & Orchestration/Kubernetes/3-Commands.md	
@@ -2,34 +2,6 @@
 
 This guide provides a concise reference for common `kubectl` commands used to manage Kubernetes clusters. Whether you’re managing nodes, namespaces, pods, deployments, or autoscaling, the examples below will help you perform everyday tasks with confidence.
 
----
-
-## Table of Contents
-
-- [Kubernetes Command Reference](#kubernetes-command-reference)
-  - [Table of Contents](#table-of-contents)
-  - [General Commands](#general-commands)
-  - [Node Management](#node-management)
-    - [Listing Nodes](#listing-nodes)
-    - [Labeling Nodes](#labeling-nodes)
-    - [Node Maintenance (Cordon/Drain)](#node-maintenance-cordondrain)
-  - [Namespace Management](#namespace-management)
-  - [Pod Management](#pod-management)
-    - [Listing Pods](#listing-pods)
-    - [Running a Pod](#running-a-pod)
-    - [Deleting a Pod](#deleting-a-pod)
-  - [API Resources \& Documentation](#api-resources--documentation)
-  - [Logs \& Pod Information](#logs--pod-information)
-  - [Applying YAML Files](#applying-yaml-files)
-  - [Viewing Cluster Resources](#viewing-cluster-resources)
-  - [ReplicaSet \& Deployment Management](#replicaset--deployment-management)
-    - [Scaling and Rollouts](#scaling-and-rollouts)
-    - [Autoscaling](#autoscaling)
-  - [Port Forwarding](#port-forwarding)
-  - [Additional Information](#additional-information)
-
----
-
 ## General Commands
 
 - **List API Resources**  
@@ -40,136 +12,6 @@ This guide provides a concise reference for common `kubectl` commands used to ma
   ```
 
 ---
-
-## Node Management
-
-### Listing Nodes
-
-- **Show All Nodes**
-
-  ```bash
-  kubectl get nodes
-  ```
-
-### Labeling Nodes
-
-- **Set a Custom Label on a Node**
-
-  ```bash
-  kubectl label node <node-name> kubernetes.io/<label-key>=<label-value>
-  ```
-
-  > **Note:** Replace `<node-name>`, `<label-key>`, and `<label-value>` with your desired values.
-
-### Node Maintenance (Cordon/Drain)
-
-- **Cordon a Node**  
-  Prevent new pods from being scheduled on the node.
-
-  ```bash
-  kubectl cordon <node-name>
-  ```
-
-- **Uncordon a Node**  
-  Mark the node as schedulable again.
-
-  ```bash
-  kubectl uncordon <node-name>
-  ```
-
-- **Drain a Node**  
-  Evict all pods from the node (excluding those managed by DaemonSets).
-
-  ```bash
-  kubectl drain <node-name> --ignore-daemonsets --delete-local-data
-  ```
-
-  > **Warning:** Draining a node will evict running pods. Ensure that you plan this action to avoid service disruption.
-
----
-
-## Namespace Management
-
-- **List All Namespaces**
-
-  ```bash
-  kubectl get namespaces
-  # Or the shorthand:
-  kubectl get ns
-  ```
-
-- **Create a New Namespace**
-
-  ```bash
-  kubectl create namespace <namespace-name>
-  ```
-
----
-
-## Pod Management
-
-### Listing Pods
-
-- **List Pods in the Default Namespace**
-
-  ```bash
-  kubectl get pods
-  ```
-
-- **List Pods with Detailed Information (Wide Output)**
-
-  ```bash
-  kubectl get pods -o wide
-  ```
-
-- **List Pods in a Specific Namespace**
-
-  ```bash
-  kubectl get pods -o wide -n <namespace-name>
-  ```
-
-### Running a Pod
-
-> **Note:** The `kubectl run` command is best suited for running single pods. For more complex deployments, consider using YAML manifests.
-
-- **Basic Example:**
-
-  ```bash
-  kubectl run <pod-name> --image=<image-name> --port=<port-number> -n <namespace-name>
-  ```
-
-- **Advanced Example with Multiple Options:**
-
-  ```bash
-  kubectl run mypod --image=nginx --port=80 -n mynamespace \
-    --env="ENV_VAR_NAME=VALUE" --command -- nginx -g "daemon off;" \
-    --restart=Always --dry-run=client \
-    --labels="app=myapp,env=prod" \
-    --limits=cpu=100m,memory=256Mi --requests=cpu=50m,memory=128Mi
-  ```
-
-  **Common Options Explained:**
-
-  - `--image`: Container image to use.
-  - `--port`: Port exposed by the container.
-  - `-n` or `--namespace`: Namespace in which to run the pod.
-  - `--env`: Set environment variables.
-  - `--command`: Treat the following arguments as the command to run.
-  - `--restart`: Pod restart policy (`Always`, `OnFailure`, or `Never`).
-  - `--labels`: Assign labels to the pod.
-  - `--dry-run`: Validate the command without creating the pod.
-  - `--limits` and `--requests`: Define resource limits and requests for the container.
-
-### Deleting a Pod
-
-- **Delete a Pod in a Specific Namespace**
-
-  ```bash
-  kubectl delete pod <pod-name> -n <namespace-name>
-  ```
-
----
-
 ## API Resources & Documentation
 
 - **Get Detailed Documentation for an API Resource**
@@ -184,21 +26,10 @@ This guide provides a concise reference for common `kubectl` commands used to ma
   kubectl explain pod
   ```
 
----
-
-## Logs & Pod Information
-
-- **Stream Logs for a Running Pod**
-
   ```bash
-  kubectl logs -f -n <namespace-name> <pod-name>
+  kubectl explain pod.metadata
   ```
 
-- **Get Detailed Information About a Pod**
-
-  ```bash
-  kubectl describe pod <pod-name> -n <namespace-name>
-  ```
 
 ---
 
@@ -296,3 +127,4 @@ kubectl port-forward -n <namespace-name> svc/<service-name> <local-port>:<target
 - **Static Manifest Files**  
   Any YAML files placed in `/etc/kubernetes/manifests/` are automatically loaded when the kubelet starts (for example, after a server reboot).
 
+
diff --git a/Containerization & Orchestration/Kubernetes/4-BasicSetup.md b/Containerization & Orchestration/Kubernetes/4-BasicSetup.md
new file mode 100644
index 0000000..e6af910
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/4-BasicSetup.md	
@@ -0,0 +1,13 @@
+
+```bash
+kubectl complation <shell>
+```
+
+exapmles:
+```bash
+kubectl completion zsh > "${fpath[1]}/_kubectl"
+```
+```bash
+kubectl completion bash > ~/.kube/completion.bash.inc
+```
+
diff --git a/Containerization & Orchestration/Kubernetes/components/1-NameSpace.md b/Containerization & Orchestration/Kubernetes/components/1-NameSpace.md
new file mode 100644
index 0000000..8985578
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/1-NameSpace.md	
@@ -0,0 +1,72 @@
+# Kubernetes Namespaces Guide
+
+Kubernetes **namespaces** allow you to organize and isolate resources within your cluster.
+
+---
+
+## 🧾 Listing Namespaces
+
+To list all namespaces:
+
+```bash
+kubectl get namespaces
+```
+
+or the shorthand:
+
+```bash
+kubectl get ns
+```
+
+---
+
+## 🛠️ Creating a Namespace
+
+Create a new namespace:
+
+```bash
+kubectl create namespace <namespace-name>
+```
+
+or:
+
+```bash
+kubectl create ns <namespace-name>
+```
+
+---
+
+## 🗑️ Deleting a Namespace
+
+Delete a namespace:
+
+```bash
+kubectl delete ns <namespace-name>
+```
+
+---
+
+## ⚠️ Best Practices & Notes
+
+* **Namespaces are isolated**, but they **can still communicate** with each other by default.
+* It is **not recommended to create namespaces that start with `kube-`**, as those are typically reserved for system components.
+
+---
+
+## 📄 Creating a Namespace with a Manifest
+
+You can define a namespace using a YAML manifest:
+
+```yaml
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: namespace-test
+```
+
+Apply it using:
+
+```bash
+kubectl apply -f namespace.yaml
+```
+
diff --git a/Containerization & Orchestration/Kubernetes/components/2-Pod.md b/Containerization & Orchestration/Kubernetes/components/2-Pod.md
new file mode 100644
index 0000000..6b77500
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/2-Pod.md	
@@ -0,0 +1,95 @@
+
+## Pod Management
+
+### Listing Pods
+
+- **List Pods in the Default Namespace**
+
+  ```bash
+  kubectl get pods
+  ```
+
+- **List Pods with Detailed Information (Wide Output)**
+
+  ```bash
+  kubectl get pods -o wide
+  ```
+
+- **List Pods in a Specific Namespace**
+
+  ```bash
+  kubectl get pods -o wide -n <namespace-name>
+  ```
+
+### Running a Pod
+
+> **Note:** The `kubectl run` command is best suited for running single pods. For more complex deployments, consider using YAML manifests.
+
+
+```bash
+kubectl run <pod-name> --image=<image-name>
+```
+
+```bash
+kubectl run <pod-name> --image=<image-name> -n <namespace>
+```
+
+
+```bash
+kubectl delete pod <pod-name> -n <namespace-name>
+```
+
+
+```bash
+kubectl delete pod <pod-name> -n <namespace-name> --force
+```
+
+
+```bash
+kubectl delete pod <pod-name> -n <namespace-name> --force --grace-period 0
+```
+
+```bash
+kubectl edit pod -n <namepsace> <podname>
+```
+Pod Can not been edit (not editable)
+
+
+```bash
+kubectl exec -it -n <namespace> <podname> -- <command or shell>
+```
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  namespace: dev
+  name: pod-1
+  labels:
+    label1: test
+    label2: test2
+    app.kubernetes.io/label3: test3
+    app.kubernetes.io/label4: test4
+spec:
+  containers:
+    - name: nginx-server
+      image: nginx
+    
+    - name: nginx-exporter
+      image: nginx-exporter
+
+    - name: ubuntu-c0
+      image: ubuntu
+      command: ["/bin/bash","-c","while true; do echo hello-world; sleep 5; done"]
+      resources:
+        limits:
+          memory: "256Mi"
+          cpu: "250m"
+        requests:
+          memory: "128Mi"
+          cpu: "125m"
+  nodeSelector:
+    hostname: k3s
+    app.kubernetes.io/disk: ssd
+```
+
diff --git a/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md b/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md
new file mode 100644
index 0000000..e69de29
diff --git a/Containerization & Orchestration/Kubernetes/label.md b/Containerization & Orchestration/Kubernetes/label.md
new file mode 100644
index 0000000..4d87e2c
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/label.md	
@@ -0,0 +1,9 @@
+- **Set a Custom Label on a Node**
+
+  ```bash
+  kubectl label node <node-name> kubernetes.io/<label-key>=<label-value>
+  ```
+
+  > **Note:** Replace `<node-name>`, `<label-key>`, and `<label-value>` with your desired values.
+
+
diff --git a/Containerization & Orchestration/Kubernetes/log-debug.md b/Containerization & Orchestration/Kubernetes/log-debug.md
new file mode 100644
index 0000000..da807ba
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/log-debug.md	
@@ -0,0 +1,27 @@
+
+- **Stream Logs for a Running Pod**
+
+  ```bash
+  kubectl logs -f -n <namespace-name> <pod-name>
+  ```
+
+
+
+  ```bash
+  kubectl logs -f -n <namespace-name> <pod-name> -c <container-name>
+  ```
+
+
+
+- **Get Detailed Information About a Pod**
+
+  ```bash
+  kubectl describe pod <pod-name> -n <namespace-name>
+  ```
+
+
+in log swith the pod need to be up 
+
+but in describe dont need to pod be up
+
+describe work on all components
\ No newline at end of file
diff --git a/Containerization & Orchestration/Kubernetes/node-manage.md b/Containerization & Orchestration/Kubernetes/node-manage.md
new file mode 100644
index 0000000..2472b09
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/node-manage.md	
@@ -0,0 +1,44 @@
+
+## Node Management
+
+### Listing Nodes
+
+- **Show All Nodes**
+
+  ```bash
+  kubectl get nodes
+  ```
+
+
+  ```bash
+    kubectl get nodes --show-lables
+  ```
+
+### Node Maintenance (Cordon/Drain)
+
+- **Cordon a Node**  
+  Prevent new pods from being scheduled on the node.
+
+  ```bash
+  kubectl cordon <node-name>
+  ```
+
+- **Uncordon a Node**  
+  Mark the node as schedulable again.
+
+  ```bash
+  kubectl uncordon <node-name>
+  ```
+
+- **Drain a Node**  
+  Evict all pods from the node (excluding those managed by DaemonSets).
+
+  ```bash
+  kubectl drain <node-name> --ignore-daemonsets --delete-local-data
+  ```
+
+  > **Warning:** Draining a node will evict running pods. Ensure that you plan this action to avoid service disruption.
+
+
+---
+
diff --git a/README.md b/README.md
index b07ff94..55bced6 100755
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ A curated collection of scripts, configuration files, and guides for managing an
 
 ### 🐳 Containerization & Orchestration
 - [Docker](./Containerization%20&%20Orchestration/Docker)
-- [Kubernetes](./Containerization%20&%20Orchestration/Kubernetes)
+- [Kubernetes(On Working)](./Containerization%20&%20Orchestration/Kubernetes)
 
 ### 🗄️ Databases
 - [Postgresql](./Databases/Postgresql)

From 9f661b1335958abc55789732750138bc546204ba Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 26 Jun 2025 22:56:20 +0330
Subject: [PATCH 018/116] update kubernetes doc

---
 .../Kubernetes/components/2-Pod.md            |  87 ++++++++++----
 .../Kubernetes/components/3-Replicaset.md     |  80 +++++++++++++
 .../Kubernetes/components/4-Deployment.md     | 107 ++++++++++++++++++
 3 files changed, 252 insertions(+), 22 deletions(-)
 create mode 100644 Containerization & Orchestration/Kubernetes/components/4-Deployment.md

diff --git a/Containerization & Orchestration/Kubernetes/components/2-Pod.md b/Containerization & Orchestration/Kubernetes/components/2-Pod.md
index 6b77500..f5c0bf9 100644
--- a/Containerization & Orchestration/Kubernetes/components/2-Pod.md	
+++ b/Containerization & Orchestration/Kubernetes/components/2-Pod.md	
@@ -1,64 +1,107 @@
+# 🌐 Kubernetes Pod Management Guide
 
-## Pod Management
+A concise guide for managing Kubernetes Pods using `kubectl` and YAML manifests.
 
-### Listing Pods
+---
 
-- **List Pods in the Default Namespace**
+## 📋 Listing Pods
 
-  ```bash
-  kubectl get pods
-  ```
+### 🔹 Default Namespace
 
-- **List Pods with Detailed Information (Wide Output)**
+List all Pods in the **default** namespace:
 
-  ```bash
-  kubectl get pods -o wide
-  ```
+```bash
+kubectl get pods
+```
 
-- **List Pods in a Specific Namespace**
+### 🔹 Wide Output (More Info)
 
-  ```bash
-  kubectl get pods -o wide -n <namespace-name>
-  ```
+List Pods with extended details (e.g., IP, node, etc.):
 
-### Running a Pod
+```bash
+kubectl get pods -o wide
+```
 
-> **Note:** The `kubectl run` command is best suited for running single pods. For more complex deployments, consider using YAML manifests.
+### 🔹 Specific Namespace
 
+List Pods in a specific namespace:
+
+```bash
+kubectl get pods -o wide -n <namespace-name>
+```
+
+---
+
+## 🚀 Running a Pod
+
+> **Note:** `kubectl run` is ideal for quick tests or running **single** Pods. For production workloads, use **YAML manifests** or **Deployments**.
+
+### 🔹 Run a Pod in Default Namespace
 
 ```bash
 kubectl run <pod-name> --image=<image-name>
 ```
 
+### 🔹 Run a Pod in a Specific Namespace
+
 ```bash
 kubectl run <pod-name> --image=<image-name> -n <namespace>
 ```
 
+---
+
+## ❌ Deleting Pods
+
+### 🔹 Standard Delete
 
 ```bash
 kubectl delete pod <pod-name> -n <namespace-name>
 ```
 
+### 🔹 Force Delete
 
 ```bash
 kubectl delete pod <pod-name> -n <namespace-name> --force
 ```
 
+### 🔹 Immediate Force Delete (No Grace Period)
 
 ```bash
-kubectl delete pod <pod-name> -n <namespace-name> --force --grace-period 0
+kubectl delete pod <pod-name> -n <namespace-name> --force --grace-period=0
 ```
 
+---
+
+## ✏️ Editing a Pod
+
+> **Warning:** Pods are **not directly editable**. Attempting to edit a running pod will result in a temporary patch but not persistent changes.
+
 ```bash
-kubectl edit pod -n <namepsace> <podname>
+kubectl edit pod -n <namespace> <pod-name>
 ```
-Pod Can not been edit (not editable)
 
+---
+
+## 🔧 Executing into a Pod
+
+Use this to start a shell or run commands inside a container:
 
 ```bash
-kubectl exec -it -n <namespace> <podname> -- <command or shell>
+kubectl exec -it -n <namespace> <pod-name> -- <command>
 ```
 
+Example for a shell:
+
+```bash
+kubectl exec -it -n dev my-pod -- /bin/bash
+```
+
+---
+
+## 🧾 Example Pod YAML Manifest
+
+A multi-container Pod with resource limits and node selector:
+
 ```yaml
 apiVersion: v1
 kind: Pod
@@ -74,13 +117,13 @@ spec:
   containers:
     - name: nginx-server
       image: nginx
-    
+
     - name: nginx-exporter
       image: nginx-exporter
 
     - name: ubuntu-c0
       image: ubuntu
-      command: ["/bin/bash","-c","while true; do echo hello-world; sleep 5; done"]
+      command: ["/bin/bash", "-c", "while true; do echo hello-world; sleep 5; done"]
       resources:
         limits:
           memory: "256Mi"
diff --git a/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md b/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md
index e69de29..13f8bbd 100644
--- a/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md	
+++ b/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md	
@@ -0,0 +1,80 @@
+# 🧩 Kubernetes ReplicaSet Management
+
+A guide to working with **ReplicaSets** in Kubernetes, including inspection, editing behavior, and configuration examples.
+
+---
+
+## 📦 Listing Pods and ReplicaSets
+
+### 🔹 List Pods in a Namespace
+
+```bash
+kubectl get pod -n <namespace>
+```
+
+### 🔹 List ReplicaSets in a Namespace
+
+```bash
+kubectl get rs -n <namespace>
+```
+
+---
+
+## ✏️ Editing a ReplicaSet
+
+You can attempt to edit a ReplicaSet:
+
+```bash
+kubectl edit rs -n <namespace> <replica-set-name>
+```
+
+> ⚠️ **Note:**
+> Editing the **image** in a ReplicaSet directly will not automatically update existing Pods.
+> This is because ReplicaSets do not perform **rolling updates**.
+> Pods will only use the new image **after the old ones are deleted and new ones are created**.
+
+**To apply image changes effectively:**
+
+1. **Delete existing Pods** manually:
+
+   ```bash
+   kubectl delete pod -l <label-selector> -n <namespace>
+   ```
+
+2. **Or**, use a higher-level controller like a **Deployment** for image updates and rolling behavior.
+
+---
+
+## 🧾 Example ReplicaSet YAML
+
+Below is a minimal and clear ReplicaSet configuration:
+
+```yaml
+apiVersion: apps/v1
+kind: ReplicaSet
+metadata:
+  name: app-1
+  namespace: dev
+  labels:
+    label1: test1
+    app.kubernetes.io/label2: test2
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app.kubernetes.io/label2: test2
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/label2: test2
+        os: linux
+    spec:
+      containers:
+        - name: nginx
+          image: nginx
+```
+
+> ✅ **Tip:**
+> Ensure that the `template.metadata.labels` **matches exactly** with `spec.selector.matchLabels`.
+> This is critical for proper ReplicaSet Pod matching.
+
diff --git a/Containerization & Orchestration/Kubernetes/components/4-Deployment.md b/Containerization & Orchestration/Kubernetes/components/4-Deployment.md
new file mode 100644
index 0000000..3654a78
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/4-Deployment.md	
@@ -0,0 +1,107 @@
+# 🚀 Kubernetes Deployment Management
+
+A guide to managing **Deployments** in Kubernetes, including listing, editing, scaling, rollbacks, and version history.
+
+---
+
+## 📋 Listing & Editing Deployments
+
+### 🔹 List Deployments in a Namespace
+
+```bash
+kubectl get deploy -n <namespace>
+```
+
+### 🔹 Edit a Deployment
+
+```bash
+kubectl edit deployment.apps -n <namespace> <deployment-name>
+```
+
+> 🛠️ **Note:**
+> Unlike ReplicaSets, Deployments **automatically update** existing Pods when the image or spec is changed. This makes Deployments ideal for rolling updates and version control.
+
+---
+
+## 📈 Scaling a Deployment
+
+Scale the number of replicas (Pods) for a Deployment:
+
+```bash
+kubectl scale -n <namespace> deployment <deployment-name> --replicas=<number>
+```
+
+---
+
+## 🔁 Rollout Management
+
+### 🔹 View Rollout History
+
+```bash
+kubectl rollout history deployment -n <namespace> <deployment-name>
+```
+
+### 🔹 View Specific Revision
+
+```bash
+kubectl rollout history deployment -n <namespace> <deployment-name> --revision=<revision-number>
+```
+
+### 🔹 Roll Back to a Previous Revision
+
+```bash
+kubectl rollout undo deployment -n <namespace> <deployment-name> --to-revision=<revision-number>
+```
+
+> ✅ **Tip:**
+> Deployments maintain revision history. This allows you to **roll back to a previous working version** in case of failure.
+
+---
+
+## 🧾 Example Deployment YAML
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-1
+  namespace: dev
+  labels:
+    label1: test1
+    app.kubernetes.io/label2: test2
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app.kubernetes.io/label2: test2
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/label2: test2
+        os: linux
+    spec:
+      containers:
+        - name: nginx
+          image: nginx
+```
+
+> 🎯 **Why use Deployments?**
+> They offer:
+
+* Rolling updates
+* Rollbacks
+* Declarative Pod management
+* History tracking
+
+---
+
+## ✅ Summary
+
+| Feature          | Pod | ReplicaSet | Deployment |
+| ---------------- | --- | ---------- | ---------- |
+| Manual creation  | ✅   | 🚫         | 🚫         |
+| Scales Pods      | ❌   | ✅          | ✅          |
+| Self-healing     | ❌   | ✅          | ✅          |
+| Rolling updates  | ❌   | ❌          | ✅          |
+| Revision history | ❌   | ❌          | ✅          |
+

From 64af745244caa793b7522b6bcae39824a58d3581 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 29 Jun 2025 16:56:28 +0330
Subject: [PATCH 019/116] update kuber doc

---
 .../Kubernetes/components/5-hpa.md            | 67 ++++++++++++++++
 .../Kubernetes/components/6-DaemonSet.md      | 40 ++++++++++
 .../Kubernetes/node-manage.md                 | 77 ++++++++++++-------
 3 files changed, 155 insertions(+), 29 deletions(-)
 create mode 100644 Containerization & Orchestration/Kubernetes/components/5-hpa.md
 create mode 100644 Containerization & Orchestration/Kubernetes/components/6-DaemonSet.md

diff --git a/Containerization & Orchestration/Kubernetes/components/5-hpa.md b/Containerization & Orchestration/Kubernetes/components/5-hpa.md
new file mode 100644
index 0000000..ffa1844
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/5-hpa.md	
@@ -0,0 +1,67 @@
+# 📈 Horizontal Pod Autoscaler (HPA)
+
+The Horizontal Pod Autoscaler automatically scales the number of pods in a deployment based on observed CPU utilization (or other select metrics).
+
+---
+
+## ⚙️ Basic Commands
+
+### 🚀 Create an HPA
+Create an HPA for a deployment, scaling based on CPU usage:
+
+```bash
+kubectl -n <namespace> autoscale deployment <deployment-name> --cpu-percent=20 --min=4 --max=10
+````
+
+### 📊 View Existing HPAs
+
+List all HPAs in a specific namespace:
+
+```bash
+kubectl get hpa -n <namespace>
+```
+
+### ❌ Delete an HPA
+
+Remove a Horizontal Pod Autoscaler:
+
+```bash
+kubectl delete hpa -n <namespace> <hpa-name>
+```
+
+### 🛠️ Edit an HPA
+
+Manually edit an existing HPA configuration:
+
+```bash
+kubectl edit hpa -n <namespace> <hpa-name>
+```
+
+---
+
+## 🧾 Example HPA Manifest
+
+You can define an HPA using a YAML file for more control:
+
+```yaml
+apiVersion: autoscaling/v2
+kind: HorizontalPodAutoscaler
+metadata:
+  name: hpa-test
+  namespace: dev
+spec:
+  minReplicas: 1
+  maxReplicas: 10
+  metrics:
+  - type: Resource
+    resource:
+      name: cpu
+      target:
+        type: Utilization
+        averageUtilization: 50
+```
+
+> ℹ️ **Note:** The above manifest uses API version `autoscaling/v2` for enhanced metric support.
+
+---
+
diff --git a/Containerization & Orchestration/Kubernetes/components/6-DaemonSet.md b/Containerization & Orchestration/Kubernetes/components/6-DaemonSet.md
new file mode 100644
index 0000000..3664ae8
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/6-DaemonSet.md	
@@ -0,0 +1,40 @@
+# 🧩 DaemonSet in Kubernetes
+
+A **DaemonSet** ensures that a copy of a specific pod runs on **every (or some) node** in the cluster. It’s typically used for background system-level services like log collection, monitoring, or networking tools.
+
+---
+
+## 📌 Key Characteristics
+
+- Automatically deploys one pod per worker node.
+- Ensures the pod stays on each node as long as the DaemonSet exists.
+- Automatically adds pods to new nodes when they join the cluster.
+
+---
+
+## 📄 Example DaemonSet YAML
+
+Below is a simple DaemonSet example that deploys `nginx` to every node in the `web` namespace:
+
+```yaml
+apiVersion: apps/v1
+kind: DaemonSet
+metadata:
+  name: nginx
+  namespace: web
+  labels:
+    app: web-servers
+spec:
+  selector:
+    matchLabels:
+      app: web-servers
+  template:
+    metadata:
+      labels:
+        app: web-servers
+    spec:
+      containers:
+        - name: nginx
+          image: nginx:1.27
+````
+
diff --git a/Containerization & Orchestration/Kubernetes/node-manage.md b/Containerization & Orchestration/Kubernetes/node-manage.md
index 2472b09..f877634 100644
--- a/Containerization & Orchestration/Kubernetes/node-manage.md	
+++ b/Containerization & Orchestration/Kubernetes/node-manage.md	
@@ -1,44 +1,63 @@
+# 🌐 Node Management with Kubernetes
 
-## Node Management
+Efficient management of Kubernetes nodes ensures cluster stability and workload flexibility. Below are key commands for listing and maintaining nodes.
 
-### Listing Nodes
+---
 
-- **Show All Nodes**
+## 📋 Listing Nodes
+
+### 🔹 Show All Nodes
+```bash
+kubectl get nodes
+````
+
+### 🔹 Show Nodes with Labels
+
+```bash
+kubectl get nodes --show-labels
+```
+
+---
+
+## 🔧 Node Maintenance (Cordon / Drain)
+
+### 🚫 Cordon a Node
+
+Prevent new pods from being scheduled on the node.
+
+```bash
+kubectl cordon <node-name>
+```
+
+### ✅ Uncordon a Node
+
+Mark the node as schedulable again.
+
+```bash
+kubectl uncordon <node-name>
+```
+
+### 🧹 Drain a Node
+
+Evict all pods from the node (excluding those managed by DaemonSets).
+
+* Forcefully drain the node:
 
   ```bash
-  kubectl get nodes
+  kubectl drain <node-name> --ignore-daemonsets --force
   ```
 
-
-  ```bash
-    kubectl get nodes --show-lables
-  ```
-
-### Node Maintenance (Cordon/Drain)
-
-- **Cordon a Node**  
-  Prevent new pods from being scheduled on the node.
-
-  ```bash
-  kubectl cordon <node-name>
-  ```
-
-- **Uncordon a Node**  
-  Mark the node as schedulable again.
-
-  ```bash
-  kubectl uncordon <node-name>
-  ```
-
-- **Drain a Node**  
-  Evict all pods from the node (excluding those managed by DaemonSets).
+* Drain and delete local data:
 
   ```bash
   kubectl drain <node-name> --ignore-daemonsets --delete-local-data
   ```
 
-  > **Warning:** Draining a node will evict running pods. Ensure that you plan this action to avoid service disruption.
+#### 🔄 Undo Drain (Uncordon)
 
+```bash
+kubectl uncordon <node-name>
+```
 
----
+> ⚠️ **Warning:** Draining a node will evict running pods. Ensure that this is planned to avoid service disruption.
 

From 1b7774ebab37c74d77ecd5ae534d7b036f9b2481 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 29 Jun 2025 22:55:44 +0330
Subject: [PATCH 020/116] update kuber doc

---
 .../Kubernetes/1-Information.md               |  4 ++
 .../Kubernetes/components/7-Jobs.md           | 48 +++++++++++++++++
 .../Kubernetes/components/8-Cronjobs.md       | 51 +++++++++++++++++++
 3 files changed, 103 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/components/7-Jobs.md
 create mode 100644 Containerization & Orchestration/Kubernetes/components/8-Cronjobs.md

diff --git a/Containerization & Orchestration/Kubernetes/1-Information.md b/Containerization & Orchestration/Kubernetes/1-Information.md
index 5d6c9c0..869e7ba 100755
--- a/Containerization & Orchestration/Kubernetes/1-Information.md	
+++ b/Containerization & Orchestration/Kubernetes/1-Information.md	
@@ -81,3 +81,7 @@ The **Control Plane** is the core management component of a Kubernetes cluster.
 
 
 image pull policy in kubernetes:
+
+
+example of all work loads:
+https://k8s-examples.container-solutions.com/
\ No newline at end of file
diff --git a/Containerization & Orchestration/Kubernetes/components/7-Jobs.md b/Containerization & Orchestration/Kubernetes/components/7-Jobs.md
new file mode 100644
index 0000000..e145099
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/7-Jobs.md	
@@ -0,0 +1,48 @@
+# ⏳ Kubernetes Jobs
+
+A **Job** in Kubernetes runs a pod to completion. It ensures that a specified number of pods successfully terminate.
+
+Use Jobs for **batch processing**, **one-off tasks**, or **short-lived workloads**.
+
+---
+
+## 🔍 Job Commands
+
+### 📄 List Jobs in a Namespace
+```bash
+kubectl get jobs.batch -n <namespace>
+````
+
+### ❌ Delete a Job
+
+```bash
+kubectl delete jobs.batch -n <namespace> <job-name>
+```
+
+---
+
+## 🧾 Example Job Manifest
+
+Here’s a minimal example of a Job that runs a simple `echo` command:
+
+```yaml
+apiVersion: batch/v1
+kind: Job
+metadata:
+  name: myjob
+  namespace: ns
+spec:
+  template:
+    spec:
+      containers:
+        - name: job1
+          image: alpine
+          command:
+            - echo 
+            - "hello world"
+      restartPolicy: Never
+```
+
+> 💡 **Note:** Always set `restartPolicy` to `Never` or `OnFailure` for jobs.
+> 📌 Jobs are useful for tasks like backups, report generation, or database migrations.
+
diff --git a/Containerization & Orchestration/Kubernetes/components/8-Cronjobs.md b/Containerization & Orchestration/Kubernetes/components/8-Cronjobs.md
new file mode 100644
index 0000000..3bc64ee
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/components/8-Cronjobs.md	
@@ -0,0 +1,51 @@
+# ⏰ Kubernetes CronJobs
+
+A **CronJob** in Kubernetes allows you to run jobs on a recurring schedule, similar to traditional UNIX `cron` jobs. Ideal for periodic tasks like backups, reports, or scheduled notifications.
+
+---
+
+## 🔍 CronJob Commands
+
+### 📄 List CronJobs in a Namespace
+```bash
+kubectl get cronjobs.batch -n <namespace>
+````
+
+### ❌ Delete a CronJob
+
+```bash
+kubectl delete cronjobs.batch -n <namespace> <cronjob-name>
+```
+
+---
+
+## 🧾 Example CronJob Manifest
+
+This CronJob runs every minute and prints the date followed by "Kubernetes":
+
+```yaml
+apiVersion: batch/v1
+kind: CronJob
+metadata:
+  name: cronjob1
+  namespace: ns
+spec:
+  schedule: "* * * * *"
+  jobTemplate:
+    spec:
+      template:
+        spec:
+          containers:
+            - name: cronjob
+              image: debian:bookworm
+              command:
+                - /bin/bash
+                - -c
+                - date; echo Kubernetes
+          restartPolicy: Never
+```
+
+> 🛠 **Fix:** Changed `JobTemplate` to `jobTemplate` (YAML keys are case-sensitive).
+> 🕐 The `schedule` field follows standard cron format: `minute hour day-of-month month day-of-week`.
+> 🧠 **Tip:** Always test cron timing carefully to avoid unintentional frequent runs.
+

From fba77d8bf6b44a3d0899069e32f70149cc91ef2d Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 30 Jun 2025 13:21:52 +0330
Subject: [PATCH 021/116] kubernetes doc

---
 .../{4-BasicSetup.md => 3-BasicSetup.md}      |   0
 .../Kubernetes/{ => Commands}/3-Commands.md   |   0
 .../Kubernetes/{ => Commands}/label.md        |   0
 .../Kubernetes/{ => Commands}/log-debug.md    |   0
 .../Kubernetes/{ => Commands}/node-manage.md  |   0
 .../{components => workloads}/1-NameSpace.md  |   0
 .../workloads/10-Deployment-With-Services.md  | 189 ++++++++++++++++
 .../{components => workloads}/2-Pod.md        |   0
 .../{components => workloads}/3-Replicaset.md |   0
 .../{components => workloads}/4-Deployment.md |   0
 .../{components => workloads}/5-hpa.md        |   0
 .../{components => workloads}/6-DaemonSet.md  |   0
 .../{components => workloads}/7-Jobs.md       |   0
 .../{components => workloads}/8-Cronjobs.md   |   0
 .../Kubernetes/workloads/9-Services.md        |  73 ++++++
 .../Kubernetes/workloads/all.md               | 208 ------------------
 .../workloads/deployment-with-service.yaml    |  23 --
 .../workloads/{ => manifests}/cronjob.yaml    |   0
 .../manifests/deployment-with-service.yaml    |  52 +++++
 .../workloads/{ => manifests}/deployment.yaml |   0
 .../workloads/{ => manifests}/ds.yml          |   0
 .../workloads/{ => manifests}/job.yaml        |   0
 .../workloads/{ => manifests}/namespace.yaml  |   0
 .../workloads/{ => manifests}/pod.yaml        |   0
 .../workloads/{ => manifests}/replicaset.yml  |   0
 .../workloads/{ => manifests}/service.yaml    |   0
 26 files changed, 314 insertions(+), 231 deletions(-)
 rename Containerization & Orchestration/Kubernetes/{4-BasicSetup.md => 3-BasicSetup.md} (100%)
 rename Containerization & Orchestration/Kubernetes/{ => Commands}/3-Commands.md (100%)
 rename Containerization & Orchestration/Kubernetes/{ => Commands}/label.md (100%)
 rename Containerization & Orchestration/Kubernetes/{ => Commands}/log-debug.md (100%)
 rename Containerization & Orchestration/Kubernetes/{ => Commands}/node-manage.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/1-NameSpace.md (100%)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/2-Pod.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/3-Replicaset.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/4-Deployment.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/5-hpa.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/6-DaemonSet.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/7-Jobs.md (100%)
 rename Containerization & Orchestration/Kubernetes/{components => workloads}/8-Cronjobs.md (100%)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/9-Services.md
 delete mode 100755 Containerization & Orchestration/Kubernetes/workloads/all.md
 delete mode 100644 Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/cronjob.yaml (100%)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/deployment.yaml (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/ds.yml (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/job.yaml (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/namespace.yaml (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/pod.yaml (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/replicaset.yml (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{ => manifests}/service.yaml (100%)

diff --git a/Containerization & Orchestration/Kubernetes/4-BasicSetup.md b/Containerization & Orchestration/Kubernetes/3-BasicSetup.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/4-BasicSetup.md
rename to Containerization & Orchestration/Kubernetes/3-BasicSetup.md
diff --git a/Containerization & Orchestration/Kubernetes/3-Commands.md b/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/3-Commands.md
rename to Containerization & Orchestration/Kubernetes/Commands/3-Commands.md
diff --git a/Containerization & Orchestration/Kubernetes/label.md b/Containerization & Orchestration/Kubernetes/Commands/label.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/label.md
rename to Containerization & Orchestration/Kubernetes/Commands/label.md
diff --git a/Containerization & Orchestration/Kubernetes/log-debug.md b/Containerization & Orchestration/Kubernetes/Commands/log-debug.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/log-debug.md
rename to Containerization & Orchestration/Kubernetes/Commands/log-debug.md
diff --git a/Containerization & Orchestration/Kubernetes/node-manage.md b/Containerization & Orchestration/Kubernetes/Commands/node-manage.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/node-manage.md
rename to Containerization & Orchestration/Kubernetes/Commands/node-manage.md
diff --git a/Containerization & Orchestration/Kubernetes/components/1-NameSpace.md b/Containerization & Orchestration/Kubernetes/workloads/1-NameSpace.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/1-NameSpace.md
rename to Containerization & Orchestration/Kubernetes/workloads/1-NameSpace.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md b/Containerization & Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md
new file mode 100644
index 0000000..91bbf6c
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md	
@@ -0,0 +1,189 @@
+### **1st Document: Namespace**
+
+```yaml
+apiVersion: v1
+```
+
+* Specifies the API version used. Here, it's version 1 of the core Kubernetes API.
+
+```yaml
+kind: Namespace
+```
+
+* Declares the resource type. This is a **Namespace**, which logically isolates groups of resources.
+
+```yaml
+metadata:
+  name: ns
+```
+
+* Metadata block.
+
+  * `name: ns` sets the name of the namespace to `ns`.
+
+---
+
+### **2nd Document: Service**
+
+```yaml
+---
+```
+
+* Separates multiple documents in the YAML file.
+
+```yaml
+apiVersion: v1
+```
+
+* Uses the core v1 API again.
+
+```yaml
+kind: Service
+```
+
+* Declares a **Service** resource, which provides stable networking to access pods.
+
+```yaml
+metadata:
+  name: nginx-service
+  namespace: ns
+  labels:
+    app: nginx
+```
+
+* Metadata block:
+
+  * `name: nginx-service`: name of the Service.
+  * `namespace: ns`: places this service in the previously created `ns` namespace.
+  * `labels`: key-value pairs used for organizing and selecting resources. Here, `app: nginx`.
+
+```yaml
+spec:
+  type: ClusterIP
+```
+
+* `spec` describes the behavior.
+
+  * `type: ClusterIP`: exposes the service internally within the cluster using a virtual IP.
+
+```yaml
+  selector:
+    app: nginx
+```
+
+* This selects pods with the label `app: nginx` to receive traffic from this service.
+
+```yaml
+  ports:
+    - name: http
+      port: 80
+      targetPort: 8080
+```
+
+* Defines port configuration:
+
+  * `name: http`: a name for the port (optional but useful for readability).
+  * `port: 80`: the port that the service exposes internally.
+  * `targetPort: 8080`: the port on the pod that receives the traffic.
+
+---
+
+### **3rd Document: Deployment**
+
+```yaml
+---
+```
+
+* Separates from the previous document.
+
+```yaml
+apiVersion: apps/v1
+```
+
+* Uses the `apps/v1` API group, suitable for deployments and other controllers.
+
+```yaml
+kind: Deployment
+```
+
+* Declares a **Deployment**, which ensures a specified number of pod replicas are running.
+
+```yaml
+metadata:
+  name: nginx-deployment
+  namespace: ns
+  labels:
+    app: nginx
+```
+
+* Metadata block:
+
+  * `name: nginx-deployment`: name of the deployment.
+  * `namespace: ns`: places this in the `ns` namespace.
+  * `labels: app: nginx`: used for matching with selectors.
+
+```yaml
+spec:
+  replicas: 2
+```
+
+* Desired number of pod replicas to run: 2.
+
+```yaml
+  selector:
+    matchLabels:
+      app: nginx
+```
+
+* Tells the deployment which pods to manage, by matching labels (`app: nginx`).
+
+```yaml
+  template:
+    metadata:
+      labels:
+        app: nginx
+```
+
+* Template for creating new pods:
+
+  * Each pod created will have `app: nginx` label.
+
+```yaml
+    spec:
+      containers:
+        - name: nginx
+          image: nginx:latest
+```
+
+* Pod spec:
+
+  * One container named `nginx`, using the latest official Nginx image.
+
+```yaml
+          ports:
+            - containerPort: 8080
+```
+
+* The container exposes port 8080 (must match the `targetPort` in the Service).
+
+```yaml
+          resources:
+            requests:
+              cpu: "100m"
+              memory: "128Mi"
+            limits:
+              cpu: "250m"
+              memory: "256Mi"
+```
+
+* **Resource management**:
+
+  * `requests`: the minimum guaranteed resources.
+
+    * `cpu: 100m` = 0.1 CPU core.
+    * `memory: 128Mi` = 128 MiB RAM.
+  * `limits`: the maximum resources the container can use.
+
+    * `cpu: 250m` = 0.25 CPU core.
+    * `memory: 256Mi` = 256 MiB RAM.
+
diff --git a/Containerization & Orchestration/Kubernetes/components/2-Pod.md b/Containerization & Orchestration/Kubernetes/workloads/2-Pod.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/2-Pod.md
rename to Containerization & Orchestration/Kubernetes/workloads/2-Pod.md
diff --git a/Containerization & Orchestration/Kubernetes/components/3-Replicaset.md b/Containerization & Orchestration/Kubernetes/workloads/3-Replicaset.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/3-Replicaset.md
rename to Containerization & Orchestration/Kubernetes/workloads/3-Replicaset.md
diff --git a/Containerization & Orchestration/Kubernetes/components/4-Deployment.md b/Containerization & Orchestration/Kubernetes/workloads/4-Deployment.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/4-Deployment.md
rename to Containerization & Orchestration/Kubernetes/workloads/4-Deployment.md
diff --git a/Containerization & Orchestration/Kubernetes/components/5-hpa.md b/Containerization & Orchestration/Kubernetes/workloads/5-hpa.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/5-hpa.md
rename to Containerization & Orchestration/Kubernetes/workloads/5-hpa.md
diff --git a/Containerization & Orchestration/Kubernetes/components/6-DaemonSet.md b/Containerization & Orchestration/Kubernetes/workloads/6-DaemonSet.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/6-DaemonSet.md
rename to Containerization & Orchestration/Kubernetes/workloads/6-DaemonSet.md
diff --git a/Containerization & Orchestration/Kubernetes/components/7-Jobs.md b/Containerization & Orchestration/Kubernetes/workloads/7-Jobs.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/7-Jobs.md
rename to Containerization & Orchestration/Kubernetes/workloads/7-Jobs.md
diff --git a/Containerization & Orchestration/Kubernetes/components/8-Cronjobs.md b/Containerization & Orchestration/Kubernetes/workloads/8-Cronjobs.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/components/8-Cronjobs.md
rename to Containerization & Orchestration/Kubernetes/workloads/8-Cronjobs.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/9-Services.md b/Containerization & Orchestration/Kubernetes/workloads/9-Services.md
new file mode 100644
index 0000000..4700b38
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/9-Services.md	
@@ -0,0 +1,73 @@
+# 🔗 Services in Kubernetes (SVC)
+
+A **Service** in Kubernetes provides a stable networking interface to access a set of pods. It allows for decoupling between client applications and the underlying pods by using DNS names and selectors.
+
+---
+
+## 🌐 Service Basics
+
+### 📌 Service Flow
+```
+
+Service ➡️ Endpoint ➡️ Pods
+
+````
+
+- Services abstract access to a group of pods.
+- Services automatically get a DNS name in the cluster.
+- They use selectors to route traffic to matching pods.
+
+---
+
+## 🧭 Service Types
+
+1. **ClusterIP** (default)  
+   - Accessible only within the cluster.
+
+2. **NodePort**  
+   - Exposes the service on a static port on each node.
+
+3. **LoadBalancer**  
+   - Provisions an external IP via a cloud provider to expose the service.
+
+---
+
+## 🧪 Useful Commands
+
+### 🔍 Get Endpoints
+```bash
+kubectl get ep -n <namespace>
+````
+
+### 📄 Get Services
+
+```bash
+kubectl get svc -n <namespace>
+```
+
+---
+
+## 🧾 Example Service Manifest
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx
+  namespace: ns
+  labels:
+    app: web-server
+spec:
+  type: ClusterIP  # Options: ClusterIP, NodePort, LoadBalancer
+  selector:
+    app: nginx
+  ports:
+    - name: http  # Port name is optional but useful
+      port: 80  # Service port
+      targetPort: 8080  # Container port
+```
+
+> 🔍 **Note:** The `selector` must match pod labels for the service to route traffic correctly.
+> 🧠 **Tip:** Use `kubectl describe svc <svc-name>` to troubleshoot or verify service-to-pod connectivity.
+> 🌐 Services are resolved by DNS using the format: `<service-name>.<namespace>.svc.cluster.local`.
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/all.md b/Containerization & Orchestration/Kubernetes/workloads/all.md
deleted file mode 100755
index 3856572..0000000
--- a/Containerization & Orchestration/Kubernetes/workloads/all.md	
+++ /dev/null
@@ -1,208 +0,0 @@
-# Kubernetes YAML Files
-
-This document provides explanations and details for various Kubernetes YAML configurations, describing how different Kubernetes objects such as Namespaces, Pods, and other specifications are defined and utilized. The examples cover creating namespaces, deploying pods, setting resource limits, and using node selectors.
-
-## Namespace Definition
-
-```yaml
-apiVersion: v1
-kind: Namespace
-metadata:
-  name: my-ns
-```
-
-- **apiVersion**: Specifies the version of the Kubernetes API.
-- **kind**: Defines the type of Kubernetes object, here it's a `Namespace`.
-- **metadata**: Contains data that helps uniquely identify the object, including a `name`.
-
-This YAML file creates a namespace named `my-ns` which isolates a group of resources within Kubernetes.
-
-## Pod Definitions
-
-### Nginx Pod
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  namespace: my-ns
-  name: nginx-pod
-  labels:
-    app: app1
-    zone: staging
-    version: v1.0.1
-    app.kubernetes.io/product: nginx-pod
-spec:
-  containers:
-    - name: naginx-container
-      image: nginx:latest
-      ports:
-        - containerPort: 80
-```
-
-- **metadata.namespace**: Specifies the namespace the pod belongs to (`my-ns`).
-- **metadata.name**: The name of the pod (`nginx-pod`).
-- **metadata.labels**: Key-value pairs for organizing and selecting resources.
-- **spec.containers**: Specifies the containers within the pod. Each container has:
-  - **name**: Container name.
-  - **image**: The Docker image to run (`nginx:latest`).
-  - **ports**: List of ports to expose from the container (`containerPort: 80`).
-
-This file defines a pod named `nginx-pod` running the latest Nginx container in the `my-ns` namespace.
-
-### Test Pod 1
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  namespace: my-ns
-  name: testpod1
-spec:
-  containers:
-    - name: c00
-      image: ubuntu
-      command: ["/bin/bash", "-c", "while true; do echo Hello-Coder; sleep 5 ; done"]
-    - name: c01
-      image: ubuntu
-      command: ["/bin/bash", "-c", "while true; do echo Hello-Programmer; sleep 5 ; done"]
-```
-
-- **spec.containers.command**: Overrides the default command for the container, in this case, running a looped bash script that prints a message every 5 seconds.
-
-This defines a pod named `testpod1` with two Ubuntu containers in the `my-ns` namespace, each running a different command.
-
-## Pod with Resource Requests and Limits
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  namespace: my-ns
-  name: testpod1
-spec:
-  containers:
-    - name: c00
-      image: ubuntu
-      command:
-        - /bin/bash
-        - -c
-        - while true; do echo Hello-Coder; sleep 5 ; done
-    - name: c01
-      image: ubuntu
-      command:
-        - /bin/bash
-        - -c
-        - while true; do echo Hello-Programmer; sleep 5 ; done
-      resources:
-        limits:
-          memory: "128Mi"
-          cpu: "500m"
-        requests:
-          memory: "64Mi"
-          cpu: "250m"
-```
-
-- **resources.limits**: Specifies the maximum amount of resources a container can use.
-- **resources.requests**: Specifies the amount of resources a container is guaranteed.
-
-This pod configuration defines resource limits and requests for the containers to ensure they do not exceed specific memory and CPU usage.
-
-## Pod with NodeSelector
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  namespace: my-ns
-  name: testpod3
-spec:
-  containers:
-    - name: c00
-      image: ubuntu
-      command:
-        - /bin/bash
-        - -c
-        - while true; do echo Hello-Coder; sleep 5 ; done
-    - name: c01
-      image: ubuntu
-      command:
-        - /bin/bash
-        - -c
-        - while true; do echo Hello-Programmer; sleep 5 ; done
-      resources:
-        limits:
-          memory: "128Mi"
-          cpu: "500m"
-        requests:
-          memory: "64Mi"
-          cpu: "250m"
-  nodeSelector:
-    kubernetes.io/hostname: k8s2
-    kubernetes.io/disk: ssd
-```
-
-- **nodeSelector**: Ensures the pod is scheduled on nodes with the specified labels (`kubernetes.io/hostname: k8s2` and `kubernetes.io/disk: ssd`).
-
-This configuration places the pod on specific nodes that match the given labels.
-
-## Simple Pod Templates
-
-### Basic Pod
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: myapp
-  labels:
-    name: myapp
-spec:
-  containers:
-  - name: myapp
-    image: <Image>
-    resources:
-      limits:
-        memory: "128Mi"
-        cpu: "500m"
-    ports:
-      - containerPort: <Port>
-```
-
-This is a template for a basic pod named `myapp` with configurable image and port settings.
-
-### Nginx Pod
-
-```yaml
-apiVersion: v1
-kind: Pod
-metadata:
-  name: my-pod
-  labels:
-    app: MyApp
-spec:
-  containers:
-  - name: my-container
-    image: nginx:latest
-    ports:
-    - containerPort: 80
-```
-
-This defines a pod named `my-pod` running an Nginx container exposing port 80.
-
-## Useful Kubernetes Commands
-
-### View Pod Details
-
-```bash
-kubectl get pod -n my-ns <pod-name> -o yaml
-```
-
-This command retrieves and displays the YAML configuration of the pod `testpod1` in the namespace `my-ns`.
-
-### Label a Node
-
-```bash
-kubectl label node <node-name> kubernetes.io/<var-name>=<var-value>
-kubectl get nodes --show-labels
-```
diff --git a/Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml b/Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml
deleted file mode 100644
index 912d9a0..0000000
--- a/Containerization & Orchestration/Kubernetes/workloads/deployment-with-service.yaml	
+++ /dev/null
@@ -1,23 +0,0 @@
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: app-deployment
-  namespace: ns-test
-  labels:
-    name: deployment-test
-    app: nginx
-spec:
-  replicas: 2
-  selector:
-    matchLabels:
-      name: app1
-      app: nginx
-  template:
-    metadata:
-      labels:
-        name: app1
-        app: nginx
-    spec:
-      containers:
-        - name: nginx-deployment
-          image: nginx:1.26
diff --git a/Containerization & Orchestration/Kubernetes/workloads/cronjob.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/cronjob.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/cronjob.yaml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/cronjob.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml
new file mode 100644
index 0000000..b282f0b
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml	
@@ -0,0 +1,52 @@
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: ns
+
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx-service
+  namespace: ns
+  labels:
+    app: nginx
+spec:
+  type: ClusterIP
+  selector:
+    app: nginx
+  ports:
+    - name: http
+      port: 80
+      targetPort: 8080
+
+---
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: nginx-deployment
+  namespace: ns
+  labels:
+    app: nginx
+spec:
+  replicas: 2
+  selector:
+    matchLabels:
+      app: nginx
+  template:
+    metadata:
+      labels:
+        app: nginx
+    spec:
+      containers:
+        - name: nginx
+          image: nginx:latest
+          ports:
+            - containerPort: 8080
+          resources:
+            requests:
+              cpu: "100m"
+              memory: "128Mi"
+            limits:
+              cpu: "250m"
+              memory: "256Mi"
diff --git a/Containerization & Orchestration/Kubernetes/workloads/deployment.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/deployment.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/deployment.yaml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/deployment.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/ds.yml b/Containerization & Orchestration/Kubernetes/workloads/manifests/ds.yml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/ds.yml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/ds.yml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/job.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/job.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/job.yaml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/job.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/namespace.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/namespace.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/namespace.yaml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/namespace.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/pod.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/pod.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/pod.yaml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/pod.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/replicaset.yml b/Containerization & Orchestration/Kubernetes/workloads/manifests/replicaset.yml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/replicaset.yml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/replicaset.yml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/service.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/service.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/service.yaml
rename to Containerization & Orchestration/Kubernetes/workloads/manifests/service.yaml

From bce1b69199f62bc25b06b3c0f98b9d142837f81b Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 1 Jul 2025 17:39:42 +0330
Subject: [PATCH 022/116] update kuber doc

---
 .../Kubernetes/workloads/{1-NameSpace.md => 01-NameSpace.md}      | 0
 .../Kubernetes/workloads/{2-Pod.md => 02-Pod.md}                  | 0
 .../Kubernetes/workloads/{3-Replicaset.md => 03-Replicaset.md}    | 0
 .../Kubernetes/workloads/{4-Deployment.md => 04-Deployment.md}    | 0
 .../Kubernetes/workloads/{5-hpa.md => 05-hpa.md}                  | 0
 .../Kubernetes/workloads/{6-DaemonSet.md => 06-DaemonSet.md}      | 0
 .../Kubernetes/workloads/{7-Jobs.md => 07-Jobs.md}                | 0
 .../Kubernetes/workloads/{8-Cronjobs.md => 08-Cronjobs.md}        | 0
 .../Kubernetes/workloads/{9-Services.md => 09-Services.md}        | 0
 9 files changed, 0 insertions(+), 0 deletions(-)
 rename Containerization & Orchestration/Kubernetes/workloads/{1-NameSpace.md => 01-NameSpace.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{2-Pod.md => 02-Pod.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{3-Replicaset.md => 03-Replicaset.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{4-Deployment.md => 04-Deployment.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{5-hpa.md => 05-hpa.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{6-DaemonSet.md => 06-DaemonSet.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{7-Jobs.md => 07-Jobs.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{8-Cronjobs.md => 08-Cronjobs.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{9-Services.md => 09-Services.md} (100%)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/1-NameSpace.md b/Containerization & Orchestration/Kubernetes/workloads/01-NameSpace.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/1-NameSpace.md
rename to Containerization & Orchestration/Kubernetes/workloads/01-NameSpace.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/2-Pod.md b/Containerization & Orchestration/Kubernetes/workloads/02-Pod.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/2-Pod.md
rename to Containerization & Orchestration/Kubernetes/workloads/02-Pod.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/3-Replicaset.md b/Containerization & Orchestration/Kubernetes/workloads/03-Replicaset.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/3-Replicaset.md
rename to Containerization & Orchestration/Kubernetes/workloads/03-Replicaset.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/4-Deployment.md b/Containerization & Orchestration/Kubernetes/workloads/04-Deployment.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/4-Deployment.md
rename to Containerization & Orchestration/Kubernetes/workloads/04-Deployment.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/5-hpa.md b/Containerization & Orchestration/Kubernetes/workloads/05-hpa.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/5-hpa.md
rename to Containerization & Orchestration/Kubernetes/workloads/05-hpa.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/6-DaemonSet.md b/Containerization & Orchestration/Kubernetes/workloads/06-DaemonSet.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/6-DaemonSet.md
rename to Containerization & Orchestration/Kubernetes/workloads/06-DaemonSet.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/7-Jobs.md b/Containerization & Orchestration/Kubernetes/workloads/07-Jobs.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/7-Jobs.md
rename to Containerization & Orchestration/Kubernetes/workloads/07-Jobs.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/8-Cronjobs.md b/Containerization & Orchestration/Kubernetes/workloads/08-Cronjobs.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/8-Cronjobs.md
rename to Containerization & Orchestration/Kubernetes/workloads/08-Cronjobs.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/9-Services.md b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/9-Services.md
rename to Containerization & Orchestration/Kubernetes/workloads/09-Services.md

From b1ea0ffbb8497283375f77be891040763af62394 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 1 Jul 2025 22:15:26 +0330
Subject: [PATCH 023/116] update doc: added tar doc

---
 .../LPIC1/{1-runlevels.md => 01-runlevels.md} |   0
 .../{2-directorys.md => 02-directorys.md}     |   0
 ...age-managers.md => 03-package-managers.md} |   0
 Linux/LPIC1/{4-dpkg.md => 04-dpkg.md}         |   0
 Linux/LPIC1/{5-apt.md => 05-apt.md}           |   0
 Linux/LPIC1/{6-yum.md => 06-yum.md}           |   0
 Linux/LPIC1/{7-rpm.md => 07-rpm.md}           |   0
 .../LPIC1/{8-setup-ssh.md => 08-setup-ssh.md} |   0
 Linux/LPIC1/10-zip.md                         |   0
 Linux/LPIC1/11-tar.md                         | 143 ++++++++++++++++++
 10 files changed, 143 insertions(+)
 rename Linux/LPIC1/{1-runlevels.md => 01-runlevels.md} (100%)
 rename Linux/LPIC1/{2-directorys.md => 02-directorys.md} (100%)
 rename Linux/LPIC1/{3-package-managers.md => 03-package-managers.md} (100%)
 rename Linux/LPIC1/{4-dpkg.md => 04-dpkg.md} (100%)
 rename Linux/LPIC1/{5-apt.md => 05-apt.md} (100%)
 rename Linux/LPIC1/{6-yum.md => 06-yum.md} (100%)
 rename Linux/LPIC1/{7-rpm.md => 07-rpm.md} (100%)
 rename Linux/LPIC1/{8-setup-ssh.md => 08-setup-ssh.md} (100%)
 create mode 100644 Linux/LPIC1/10-zip.md
 create mode 100644 Linux/LPIC1/11-tar.md

diff --git a/Linux/LPIC1/1-runlevels.md b/Linux/LPIC1/01-runlevels.md
similarity index 100%
rename from Linux/LPIC1/1-runlevels.md
rename to Linux/LPIC1/01-runlevels.md
diff --git a/Linux/LPIC1/2-directorys.md b/Linux/LPIC1/02-directorys.md
similarity index 100%
rename from Linux/LPIC1/2-directorys.md
rename to Linux/LPIC1/02-directorys.md
diff --git a/Linux/LPIC1/3-package-managers.md b/Linux/LPIC1/03-package-managers.md
similarity index 100%
rename from Linux/LPIC1/3-package-managers.md
rename to Linux/LPIC1/03-package-managers.md
diff --git a/Linux/LPIC1/4-dpkg.md b/Linux/LPIC1/04-dpkg.md
similarity index 100%
rename from Linux/LPIC1/4-dpkg.md
rename to Linux/LPIC1/04-dpkg.md
diff --git a/Linux/LPIC1/5-apt.md b/Linux/LPIC1/05-apt.md
similarity index 100%
rename from Linux/LPIC1/5-apt.md
rename to Linux/LPIC1/05-apt.md
diff --git a/Linux/LPIC1/6-yum.md b/Linux/LPIC1/06-yum.md
similarity index 100%
rename from Linux/LPIC1/6-yum.md
rename to Linux/LPIC1/06-yum.md
diff --git a/Linux/LPIC1/7-rpm.md b/Linux/LPIC1/07-rpm.md
similarity index 100%
rename from Linux/LPIC1/7-rpm.md
rename to Linux/LPIC1/07-rpm.md
diff --git a/Linux/LPIC1/8-setup-ssh.md b/Linux/LPIC1/08-setup-ssh.md
similarity index 100%
rename from Linux/LPIC1/8-setup-ssh.md
rename to Linux/LPIC1/08-setup-ssh.md
diff --git a/Linux/LPIC1/10-zip.md b/Linux/LPIC1/10-zip.md
new file mode 100644
index 0000000..e69de29
diff --git a/Linux/LPIC1/11-tar.md b/Linux/LPIC1/11-tar.md
new file mode 100644
index 0000000..d574979
--- /dev/null
+++ b/Linux/LPIC1/11-tar.md
@@ -0,0 +1,143 @@
+# 📦 Linux Compression & Archiving Cheatsheet
+
+## 🔧 Tar Command Basics
+
+The `tar` command is used to create, extract, and manage archive files.
+
+**Syntax:**
+
+```bash
+tar [options] [archive_name.tar] [file(s)/directory]
+```
+
+### 🛠 Create a `.tar` Archive
+
+```bash
+tar -cf archive_file.tar file1 file2 dir1
+```
+
+* `-c`: Create a new archive
+* `-f`: Specify the archive file name
+
+### 🛠 Create with Verbose Output
+
+```bash
+tar -cvf archive_file.tar file1 file2 dir1
+```
+
+* `-v`: Verbose mode (shows progress)
+
+### 📂 Extract a `.tar` Archive
+
+```bash
+tar -xf archive_file.tar
+```
+
+```bash
+tar -xvf archive_file.tar
+```
+
+* `-x`: Extract files
+
+---
+
+## 🗜 Gzip Compression
+
+**Gzip** (GNU zip) is a fast, commonly used compression tool.
+
+### 🔧 Create `.tar.gz` Archive
+
+```bash
+tar -czf archive_file.tar.gz file1 file2 dir1
+```
+
+* `-z`: Compress using gzip
+
+### 🔧 Verbose Creation
+
+```bash
+tar -czvf archive_file.tar.gz file1 file2 dir1
+```
+
+### 📂 Extract `.tar.gz`
+
+```bash
+tar -xzf archive_file.tar.gz
+```
+
+```bash
+tar -xzvf archive_file.tar.gz
+```
+
+---
+
+## 🗜 Bzip2 Compression
+
+**Bzip2** offers better compression than gzip but is slower.
+
+### 🔧 Create `.tar.bz2` Archive
+
+```bash
+tar -cjf archive_file.tar.bz2 file1 file2 dir1
+```
+
+* `-j`: Compress using bzip2
+
+### 🔧 Verbose Creation
+
+```bash
+tar -cjvf archive_file.tar.bz2 file1 file2 dir1
+```
+
+### 📂 Extract `.tar.bz2`
+
+```bash
+tar -xjf archive_file.tar.bz2
+```
+
+```bash
+tar -xjvf archive_file.tar.bz2
+```
+
+---
+
+## 🗜 XZ Compression
+
+**XZ** provides the best compression ratios but is the slowest.
+
+### 🔧 Create `.tar.xz` Archive
+
+```bash
+tar -cJf archive_file.tar.xz file1 file2 dir1
+```
+
+* `-J`: Compress using xz
+
+### 🔧 Verbose Creation
+
+```bash
+tar -cJvf archive_file.tar.xz file1 file2 dir1
+```
+
+### 📂 Extract `.tar.xz`
+
+```bash
+tar -xJf archive_file.tar.xz
+```
+
+```bash
+tar -xJvf archive_file.tar.xz
+```
+
+---
+
+## 📊 Compression Format Comparison
+
+| Feature             | `gzip`       | `bzip2`    | `xz`      |
+| ------------------- | ------------ | ---------- | --------- |
+| Compression Speed   | Fast         | Slow       | Slowest   |
+| Decompression Speed | Fast         | Slower     | Moderate  |
+| Compression Ratio   | Good         | Better     | **Best**  |
+| File Extension      | `.tar.gz`    | `.tar.bz2` | `.tar.xz` |
+| Common Use          | Web, general | Backups    | Archival  |
+

From db28f602bcb440676c74e57e0e4c2441e3cccb8b Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 1 Jul 2025 22:23:40 +0330
Subject: [PATCH 024/116] update doc added zip doc

---
 Linux/LPIC1/10-zip.md | 70 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 70 insertions(+)

diff --git a/Linux/LPIC1/10-zip.md b/Linux/LPIC1/10-zip.md
index e69de29..b278054 100644
--- a/Linux/LPIC1/10-zip.md
+++ b/Linux/LPIC1/10-zip.md
@@ -0,0 +1,70 @@
+# 🗜️ ZIP Compression Cheatsheet
+
+The `zip` command is a widely used tool for compressing files and folders into a `.zip` archive. It is cross-platform and supports features like encryption and customizable compression levels.
+
+---
+
+## 📦 Basic Syntax
+
+```bash
+zip [options] archive.zip files
+```
+
+---
+
+## 🔧 Create a ZIP Archive
+
+```bash
+zip archive.zip file1 file2
+```
+
+* Compresses `file1` and `file2` into `archive.zip`
+
+---
+
+## 📈 Maximum Compression
+
+```bash
+zip -9 archive.zip file1 file2
+```
+
+* `-9`: Use maximum compression (slower, but smaller file size)
+
+---
+
+## 🔐 Create a Password-Protected ZIP
+
+```bash
+zip -e archive.zip file1 file2
+```
+
+* `-e`: Prompts for password encryption on the archive
+
+---
+
+## 📋 List Files in a ZIP Archive
+
+```bash
+unzip -l archive.zip
+```
+
+* `-l`: Lists contents of the ZIP without extracting
+
+---
+
+## 📂 Extract ZIP Archive
+
+```bash
+unzip archive.zip
+```
+
+* Extracts contents into the current directory
+
+### 📁 Extract to Custom Directory
+
+```bash
+unzip archive.zip -d <custom-dir>
+```
+
+* `-d <custom-dir>`: Extracts files into the specified folder
+

From 4789a8f2272da617ef283f9f3ecace95ad1f24f6 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 1 Jul 2025 23:45:21 +0330
Subject: [PATCH 025/116] update doc: added vim

---
 Linux/LPIC1/09-vim.md | 119 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 Linux/LPIC1/09-vim.md

diff --git a/Linux/LPIC1/09-vim.md b/Linux/LPIC1/09-vim.md
new file mode 100644
index 0000000..ecdd92e
--- /dev/null
+++ b/Linux/LPIC1/09-vim.md
@@ -0,0 +1,119 @@
+# Getting Started with Vim 📝
+
+## 1. Installing Vim
+
+To install Vim on a Debian‑based system (like Ubuntu), run:
+
+```bash
+sudo apt update
+sudo apt install vim
+```
+
+---
+
+## 2. Opening Files or Directories
+
+* **Open a file**
+
+  ```bash
+  vim <filename>
+  ```
+
+* **Open a directory**
+
+  ```bash
+  vim <directory_name>
+  ```
+
+  (This opens Vim’s file browser—helpful for navigating and editing multiple files.)
+
+---
+
+## 3. Vim Modes
+
+Vim works in multiple modes—here are the core ones:
+
+1. **Normal mode** – The default mode; used for navigation and commands.
+2. **Insert mode** – For editing text; enter it by pressing `i`, `a`, or `o`.
+3. **Visual mode** – For selecting text; enter it with `v`, `V`, or `Ctrl+v`.
+
+---
+
+## 4. Essential Commands
+
+(Type these in **Normal mode** and then press Enter when needed)
+
+| Command     | Description                               |
+| ----------- | ----------------------------------------- |
+| `:w`        | Save (write changes to the current file)  |
+| `:w <name>` | Save changes to a specified file `<name>` |
+| `:wq`       | Save and quit Vim                         |
+| `:q`        | Quit (only if no unsaved changes exist)   |
+| `:q!`       | Quit without saving (discard all changes) |
+
+---
+
+## 5. Handy Shortcuts
+
+These are core shortcuts used in **Normal mode**:
+
+| Shortcut | Action                           |
+| -------- | -------------------------------- |
+| `dd`     | Delete (cut) the current line    |
+| `yy`     | Yank (copy) the current line     |
+| `p`      | Paste after the cursor           |
+| `u`      | Undo the last change             |
+| `gg`     | Go to the first line of the file |
+
+---
+
+## 6. Quick Usage Flow
+
+1. **Start Vim**:
+
+   ```bash
+   vim example.txt
+   ```
+
+2. **Insert text**:
+   Press `i` → type your content → press `Esc` to return to **Normal mode**.
+
+3. **Save your work**:
+   Type `:w` in Normal mode and press Enter.
+
+4. **Make edits**:
+
+   * Use `dd` to delete a line
+   * Use `yy` to copy (yank) a line
+   * Move the cursor to a new location, then hit `p` to paste
+   * Press `u` to undo any mistake
+
+5. **Navigate quickly**:
+
+   * `gg` to jump to the beginning
+   * Use arrow keys or `h`, `j`, `k`, `l` for navigation
+
+6. **Finish editing**:
+
+   * `:wq` to save and exit
+   * `:q!` to exit without saving
+
+---
+
+## 7. Tips & Tricks
+
+* **Visual mode**:
+  Press `v` to start selecting character by character, `V` for line selection, or `Ctrl+v` for block-wise selection.
+
+* **Other navigation**:
+
+  * Use `G` to go to the end of the file
+  * Use a number before a command, e.g., `5dd` deletes 5 lines
+
+---
+
+### Summary
+
+Vim may feel different at first, but once you get comfortable switching between **Insert**, **Normal**, and **Visual** modes, you'll find it’s a powerful and efficient editor.
+Happy Vimming! 😊
+

From bc6a3c581f923dfa608449aba797e3005336e1dc Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 1 Jul 2025 23:56:42 +0330
Subject: [PATCH 026/116] remove somthings

---
 .../TelegramBot/GettingStarted.md             | 172 ---------------
 .../TelegramBot/LocalTelegramBotServer.md     |  41 ----
 .../TelegramBot/WebHooks.md                   |  53 -----
 .../db.sqlite3 => Linux/LPIC1/12-grep.md      |   0
 .../__init__.py => Linux/LPIC1/13-less.md     |   0
 .../LPIC1/14-head-tail.md                     |   0
 Linux/LPIC1/15-wc.md                          |   0
 .../info/__pycache__/__init__.cpython-39.pyc  | Bin 134 -> 0 bytes
 .../__pycache__/serializers.cpython-39.pyc    | Bin 973 -> 0 bytes
 .../info/__pycache__/urls.cpython-39.pyc      | Bin 349 -> 0 bytes
 .../info/__pycache__/views.cpython-39.pyc     | Bin 1635 -> 0 bytes
 .../Django/info/admin.py                      |   3 -
 .../Django/info/apps.py                       |   6 -
 .../Django/info/models.py                     |   3 -
 .../Django/info/serializers.py                |  24 --
 .../Django/info/tests.py                      |   3 -
 .../Django/info/urls.py                       |   7 -
 .../Django/info/views.py                      |  34 ---
 Web Development & Frameworks/Django/manage.py |  22 --
 .../Django/sys_info.md                        |  40 ----
 Web Development & Frameworks/nginx/Laravel.md | 153 -------------
 Web Development & Frameworks/nginx/django.md  | 206 ------------------
 Web Development & Frameworks/nginx/dotnet.md  | 114 ----------
 23 files changed, 881 deletions(-)
 delete mode 100755 Bots & Automation Tools/TelegramBot/GettingStarted.md
 delete mode 100755 Bots & Automation Tools/TelegramBot/LocalTelegramBotServer.md
 delete mode 100755 Bots & Automation Tools/TelegramBot/WebHooks.md
 rename Web Development & Frameworks/Django/db.sqlite3 => Linux/LPIC1/12-grep.md (100%)
 mode change 100755 => 100644
 rename Web Development & Frameworks/Django/info/__init__.py => Linux/LPIC1/13-less.md (100%)
 mode change 100755 => 100644
 rename Web Development & Frameworks/Django/info/migrations/__init__.py => Linux/LPIC1/14-head-tail.md (100%)
 mode change 100755 => 100644
 create mode 100644 Linux/LPIC1/15-wc.md
 delete mode 100755 Web Development & Frameworks/Django/info/__pycache__/__init__.cpython-39.pyc
 delete mode 100755 Web Development & Frameworks/Django/info/__pycache__/serializers.cpython-39.pyc
 delete mode 100755 Web Development & Frameworks/Django/info/__pycache__/urls.cpython-39.pyc
 delete mode 100755 Web Development & Frameworks/Django/info/__pycache__/views.cpython-39.pyc
 delete mode 100755 Web Development & Frameworks/Django/info/admin.py
 delete mode 100755 Web Development & Frameworks/Django/info/apps.py
 delete mode 100755 Web Development & Frameworks/Django/info/models.py
 delete mode 100755 Web Development & Frameworks/Django/info/serializers.py
 delete mode 100755 Web Development & Frameworks/Django/info/tests.py
 delete mode 100755 Web Development & Frameworks/Django/info/urls.py
 delete mode 100755 Web Development & Frameworks/Django/info/views.py
 delete mode 100755 Web Development & Frameworks/Django/manage.py
 delete mode 100755 Web Development & Frameworks/Django/sys_info.md
 delete mode 100755 Web Development & Frameworks/nginx/Laravel.md
 delete mode 100755 Web Development & Frameworks/nginx/django.md
 delete mode 100755 Web Development & Frameworks/nginx/dotnet.md

diff --git a/Bots & Automation Tools/TelegramBot/GettingStarted.md b/Bots & Automation Tools/TelegramBot/GettingStarted.md
deleted file mode 100755
index 14d5501..0000000
--- a/Bots & Automation Tools/TelegramBot/GettingStarted.md	
+++ /dev/null
@@ -1,172 +0,0 @@
-# کد نویسی برای بات تلگرام
-ربات **تلگرام** (**telegram** bot) یک نوع حساب کاربری ویژه در **تلگرام** است که به صورت اتوماتیک پیام ها را ارسال و دریافت می نماید . کاربران از طریق ارسال دستورات گوناگون با ربات ها در ارتباط هستند و امکان مدیریت ربات ها از طریق API **تلگرام** و درخواست های HTTPS وجود دارد . عبارت bot برای ربات ها نمایش داده می شود.
-
-## ساخت بات با BotFather
-اولین مرحله برای کد نویسی بات تلگرام ساختن بات است. از طریق [BotFather](https://telegram.me/BotFather) بات را خواهیم ساخت. پیام `start/` را در BotFather وارد کنید سپس روی **newbot - create a new bot/** کلیک کنید. بعد از مشاهده پیام **Alright, a new bot. How are we going to call it? Please choose a name for your bot.** یک اسم برای بات خود وارد کنید. 
-سپس بعد از مشاهده پیام **Good. Now let's choose a username for your bot. It must end in bot. Like this, for example: TetrisBot or tetris_bot.** یک نام **خاص و Unique انگلیسی** که حتما در آخرش کلمه **bot** را دارد وارد کنید.
-
-زمانی که بات شما ساخته شد توکن بات را که زیر **Use this token to access the HTTP API** قرار دارد را کپی کنید و در محل امنی قرار دهید.
-
-## آماده سازی محیط کد نویسی
-به طور کلی از دو روش می توان برای بات های تلگرام برنامه نویسی کرد. 
-**روش اول: استفاده از Rest API رسمی تلگرام که نحوه استفاده از در سایت core.telegram.org/bots/api قابل دسترس است**
-**روش دوم: استفاده از پکیج هایی که کد های پایه بات را برای زبان برنامه نویسی مورد نظر شما ساخته اند**
-برخی از این پکیج های عبارت اند از:
-برای سی شارپ ([Telegram.Bot](https://www.nuget.org/packages/Telegram.Bot)) 
-	این پکیج از طریق کامند زیر در **Dotnet CLI** نصب می شود
-
-	dotnet add package Telegram.Bot --version 19.0.0
-
-برای پایتون ( [python-telegram-bot](https://pypi.org/project/python-telegram-bot/2.4/))
-این پکیج نیز از طریق کامند زیر قابل نصب است
-
-    pip install python-telegram-bot==2.4
-
-برای اینکه این آموزش بر Core و Universal بودن تاکید دارد ما از از طریق روش اول برای بات خود کد نویسی هر چند این روش کمی سخت تر است اما اگر به خوبی این روش را یادبگرید خود می توانید کتابخانه مانند دو نمونه بالا بنوسید
-
-## کد نویسی برای بات
-پروژه ای با زبان مورد نظر خود ایجاد کنید و کتابخانه هایی مورد نیاز برای **Rest API** را روی پروژه نصب یا Import کنید. 
-برای مثال اگر از زبان برنامه نویسی سی شارپ استفاده می کنید باید **RestSharp** را نصب کنید و نحوه کار با آن را بلد باشید و اگر از پایتون استفاده می کنید باید کتابخانه **Request** را نصب و Import کنید.
-
-**قبل از شروع به این نکات درباره API تلگرام توجه کنید.**
-
-+ تلگرام به حروف بزرگ و کوچک در API حساس است
-+ تلگرام فقط از **POST** و **GET** پشتیبانی می کند
-+ همه درخواست ها باید کاملا با **UTF-8** باشند
-+ تلگرام از هر 4 روش رایج ارسال درخواست **(application/json, multipart/form-data ,QueryString, application/x-www-form-urlencoded)** پشتیبانی می کند
-**پیشنهاد:** من به شما پیشنهاد می کنم از QueryString یا application/json استفاده کنید.
-
-### روش QueryString چیست؟
-در این روش پارامتر های تابع که می خواهیم اجرا کنیم به عنوان QueryString در Url گذاشته می شوند مانند:
-
-	https://test.ir/APIFunction?param1=inp1&param2=inp2
-
-همانطور که در مثال بالا آشکار است هر چه بعد از **?** قرا ر می گیرد **Query String** است. 
-پارامتر 1 یا **param1** اسم متغیر اول ماست و **inp1** ورودی متغیر **param1** است.
-سپس پارامتر های ورودی با علامت **&** جدا شده اند. و پارمتر دوم یا **param2** و ورود آن قرار گرفته است.
-
-### روش application/json
-در این روش Url فقط به آدرس تابع اشاره دارد نه به ورود های آن مانند:
-
-    https://test.ir/APIFunction
-
-   در این روش پارامتر ها به عنوان Json در بدنه ارسال می شوند. مانند زیر 
-
-    {
-        "Body":{
-            "param1":"inp1",
-            "param2":"inp2",
-    },
-
-البته ارسال بدنه با توجه به کتابخانه که برای API استفاده می کنید. متفاوت مثلا برای **RestSharp** از Request.AddBody باید استفاده کنید.
-
-## استاندارد های استفاده از API تلگرام
-**آدرس پایه API:** 
-
-    https://api.telegram.org/bot<token>/<FuncName>
-
-**توکن:** به جای **<token>** توکنی را که از بات فادر گرفتید قرار دهید
-**نام تابع:** تابعی که می خواهید فراخوانی کنید را به جای **<Funcname>** قرار دهید
-
-**موفق بودن یا نا موفق بودن درخواست**
-اگر درخواست شما **موفقیت آمیز** باشد با **OK:True**  مواجه می شوید و جواب درخواست را به عنوان **Result** به شما برگردانده می شود
-**مثال:**
-
-	{
-	"ok":true,
-	"result":[]
-	}
-
-اگر درخواست شما **ناموفق** باشد. **OK: False** می شود و شما پارامتر به عنوان **Result** نخواهید داشت همچنین **error_code** و **description** را به ترتیب برای شماره خطا و توصیف خطا دریافت خواهید کرد. 
-**مثال: **
-
-	{
-	"ok":false,
-	"error_code":404,
-	"description":"Not Found" 
-	}
-
-**بروزرسانی بات:**
-هر بار که پیامی برای بات ارسال می شود را می توان با **getUpdate** بدست آورد. برای بدست آوردن لیست آپدیت می توانید Url زیر را GET کنید
-
-	https://api.telegram.org/bot<token>/getUpdates
-
-این درخواست لیستی از Update ها بر می گرداند. 
-برای مشاهده شئ Update به https://core.telegram.org/bots/api#update مراجعه کنید
-
-**دریافت اطلاعات کلی بات:**
-برای دریافت اطلاعات کلی از آدرس زیر استفاده کنید
-
-    https://api.telegram.org/bot<token>/getMe
-
-**جواب:**
-
-    {
-      "ok": true,
-      "result": {
-        "id": 6775339167,
-        "is_bot": true,
-        "first_name": "ForDocumentPack",
-        "username": "ForDocumentPackBot",
-        "can_join_groups": true,
-        "can_read_all_group_messages": false,
-        "supports_inline_queries": false
-      }
-    }
-
-## ساخت پروژه ساده
-می خواهیم یک پروژه کد نویسی کنیم که زمانی که بات روشن می شود یک پیام خوش آمد گویی ارسال کند.
-برای این کار از طریق تابع **getUpdates** پیام هایی که بات داده شده است را مشاهده می کنیم مانند زیر:
-
-	{
-      "ok": true,
-      "result": [
-        {
-          "update_id": 529754041,
-          "message": {
-            "message_id": 1,
-            "from": {
-              "id": 407692495,
-              "is_bot": false,
-              "first_name": "Mahdiyar",
-              "last_name": "Abdollahi",
-              "username": "Mdr_abdollahi",
-              "language_code": "en"
-            },
-            "chat": {
-              "id": 407692495,
-              "first_name": "Mahdiyar",
-              "last_name": "Abdollahi",
-              "username": "Mdr_abdollahi",
-              "type": "private"
-            },
-            "date": 1697995311,
-            "text": "/start",
-            "entities": [
-              {
-                "offset": 0,
-                "length": 6,
-                "type": "bot_command"
-              }
-            ]
-          }
-        }
-      ]
-    }
-
-**نکته: get_updates را در حلقه بی نهایت بی اندازید تا همیشه بروزرسانی شود**
-**نکته: بررسی کنید تا به کسانی که به آنها پاسخ داده اید دوباره پاسخ ندهید.**
-**نکته: اگر به جای getUpdates از** [WebHooks](https://core.telegram.org/bots/api#getting-updates) **استفاده کنید نیاز به بررسی پاسخ های تکراری نیست**
-
-برای ارسال پیام نیاز به **chat_id** داریم.
-
-	result => message => chat => id
-
-بعد از دریافت **chat_id** می توانیم با تابع **sendMessage** پیام برای کاربر ارسال کنید. 
-
-	https://api.telegram.org/bot<token>/sendMessage
-
-**نکته: حتما باید پارامتر chat_id و text ارسال شود**
-**نکته: حتما باید بصورت POST ارسال شود و پارامتر ها به صورت application/json باشد**
-
-شما می توانید تمامی تابع های API تلگرام را از سایت تلگرام مشاهده کنید -> https://core.telegram.org/bots/api
diff --git a/Bots & Automation Tools/TelegramBot/LocalTelegramBotServer.md b/Bots & Automation Tools/TelegramBot/LocalTelegramBotServer.md
deleted file mode 100755
index 333bbb0..0000000
--- a/Bots & Automation Tools/TelegramBot/LocalTelegramBotServer.md	
+++ /dev/null
@@ -1,41 +0,0 @@
-# آموزش اجرای سرور بات تلگرام 
-در این سند قصد داریم که سرور بات تلگرام را به  صورت لوکال بالا بیاوریم. توجه داشته باشید که شما می توانید از سرور های پیشفرض تلگرام به آدرس **api.telegram.org** استفاده کنید اما اگر قصد دارید که از قابلیت های ویژه مانند اتصال webhook لوکال استفاده نیاز به این سند دارید.
-[کاربرد های سرور لوکال تلگرام](https://github.com/tdlib/telegram-bot-api#usage)
-
-**این آموزش فقط برای سیستم های بر پایه Ubuntu 22.04 تست شده است**
-
-## مرحله اول: نصب وابستگی ها
-یک سری نرم افزار ها و پکیج ها را باید قبل از اجرای سرور نصب کرد
-**اوپن اس اس ال - Open SSL**
-
-	sudo apt-get install libssl-dev
-
-**کامپایلر سی پلاس پلاس نسخه 14 ما از g++ 14 استفاده خواهیم کرد**
-
-    sudo add-apt-repository ppa:ubuntu-toolchain-r/test
-    sudo apt update
-    sudo apt install g++
-
-**زی لیب - zlib**
-
-	sudo apt install zlib1g
-
-**جی پرف - gperf**
-
-	sudo apt install gperf
-
-**سی میک - cmake**
-
-	sudo apt install cmake
-
-## مرحله دوم: نصب
-برای نصب دستورات زیر را در ترمینال وارد کنید
-
-	git clone --recursive https://github.com/tdlib/telegram-bot-api.git
-    cd telegram-bot-api
-    mkdir build
-    cd build
-    cmake -DCMAKE_BUILD_TYPE=Release ..
-    cmake --build . --target install
-
-```
diff --git a/Bots & Automation Tools/TelegramBot/WebHooks.md b/Bots & Automation Tools/TelegramBot/WebHooks.md
deleted file mode 100755
index 96a2be6..0000000
--- a/Bots & Automation Tools/TelegramBot/WebHooks.md	
+++ /dev/null
@@ -1,53 +0,0 @@
-
-# استفاده از Web Hooks در گرفتن پیام های بات تلگرام
-**توجه: پیش نیاز این سند Getting Started.MD است**
-
-دو روش برای دریافت پیام ارسالی به بات در تلگرام وجود دارد. **Get Updates Function** و **Web Hooks** روش **Get Updates Function** را در سند قبلی استفاده و بررسی کردیم. برای درک Web Hook باید اول Get Updates را خوب متوجه شویم
-
-## روش اول: Get Updates
-در این روش که در سندی قبل از آن استفاده کردیم. شما به تلگرام مراجعه می کنید و تلگرام همه پیام هایی تاریخ بات را برای شما می فرستد در این روش چند چالش وجود دارد
-
-+ **در هر درخواست تمامی پیام ها ارسال می شود این به معنی  است که در یک بات با مخاطبان متوسط هر درخواست شامل صد ها هزار پیام است که قبلا به آن پاسخ داده اید و به آن ها دیگر نیازی ندارید**
-
-+ **باید بررسی کنید که به کدام پیام پاسخ داده شده و به کدام پاسخ نداده شده است**
-
-+ **باید از حلقه بی نهایت استفاده کنید تا همیشه از تلگرام درخواست کند. پیاده سازی حلقه بی نهاییت در بسیاری از نرم افزار ها مانند وب سایت بسیار چالش بر انگیز یا غیر ممکن است.**
-
-راه کار بهتر روش Web Hooks است.
-
-## روش دوم: Web Hooks
-در این روش به جای اینکه مانند روش **Get Updates** شما به تلگرام مراجعه کنید. تلگرام به شما مراجعه می کند. **پیام های جدید را که قبلا دریافت نکرده اید** به شما می دهد. این روش هر سه مشکل **Get Updates** را بر طرف می کند. البته این روش نیز بی نقص نیست و چالش به همراه دارد. مانند:
-
-+ **چون تلگرام باید برای شما چیزی ارسال کند نمی توان از این روش در فضای Local استفاده کرد**
-
-+ **محدودیت توسط تلگرام برای این روش اعمال شده است که ممکن است رفع این محدودیت ها هزینه بر یا وقت گیر باشد**
-
-
-### محدودیت های Web Hooks
-
-+ **اگر از وب هوکس استفاده کنید دیگر نمی توانید از getUpdates استفاده کنید**
-+ **فقط پورت های 443, 80, 88, 8443 برای اینکار قابل استفاده اند**
-+ **فقط تلگرام به سایت هایی که دارای SSL هستند. پیام ها را ارسال می کند**
-
-## تنظیم از Web Hooks
-برای تنظیم وب هوک از طریق  تابع **setWebhook** آدرسی که می خواهیم به آن پیام ها ارسال شود را به عنوان **Url** ارسال می کنیم
-
-	https://api.telegram.org/bot<token>/setWebhook
-
-**نکنه: حتما از متد POST استفاده کنید و Url را با روش application/json بفرستید**
-
-برای مشاهده پارامتر های اختیاری Web Hooks به لینک زیر مراجعه کنید 
-[https://core.telegram.org/bots/api#setwebhook](Web%20Hooks)
-
-## پاک کردن Web Hooks
-اگر به هر دلیلی خواستید وب هوک را پاک کنید یا از get Updates استفاده کنید با استفاده از تابع زیر وب هوکس پاک شده و Get Updates دوباره فعال می شود
-
-	https://api.telegram.org/bot<token>/deleteWebhook
-
-## مشاهده وضعیت Web Hooks
-با تابع زیر می توان وضعیت وب هوک، سرعت پاسخ دهی، آخرین خطا ها، آخرین هشدار ها و... را مشاهده کرد
-
-	https://api.telegram.org/bot<token>/getwebhookinfo
-
-[برای مشاهده اطلاعات دریافتی از این تابع کلیک کنید](https://core.telegram.org/bots/api#webhookinfo)
-
diff --git a/Web Development & Frameworks/Django/db.sqlite3 b/Linux/LPIC1/12-grep.md
old mode 100755
new mode 100644
similarity index 100%
rename from Web Development & Frameworks/Django/db.sqlite3
rename to Linux/LPIC1/12-grep.md
diff --git a/Web Development & Frameworks/Django/info/__init__.py b/Linux/LPIC1/13-less.md
old mode 100755
new mode 100644
similarity index 100%
rename from Web Development & Frameworks/Django/info/__init__.py
rename to Linux/LPIC1/13-less.md
diff --git a/Web Development & Frameworks/Django/info/migrations/__init__.py b/Linux/LPIC1/14-head-tail.md
old mode 100755
new mode 100644
similarity index 100%
rename from Web Development & Frameworks/Django/info/migrations/__init__.py
rename to Linux/LPIC1/14-head-tail.md
diff --git a/Linux/LPIC1/15-wc.md b/Linux/LPIC1/15-wc.md
new file mode 100644
index 0000000..e69de29
diff --git a/Web Development & Frameworks/Django/info/__pycache__/__init__.cpython-39.pyc b/Web Development & Frameworks/Django/info/__pycache__/__init__.cpython-39.pyc
deleted file mode 100755
index 5b44c4f93b81a9f4572cf36ed49a05370b0b73c7..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 134
zcmYe~<>g`k0%=K=R1p0bL?8o3AjbiSi&=m~3PUi1CZpd<h9ZzKg7~GapOK%Ns-KvX
zsh^USn3tX(Z>V2fS)7@dmah*c;^Q;(GE3s)^$IF)aoFVMr<CTT+JOxD48#loT!$P4

diff --git a/Web Development & Frameworks/Django/info/__pycache__/serializers.cpython-39.pyc b/Web Development & Frameworks/Django/info/__pycache__/serializers.cpython-39.pyc
deleted file mode 100755
index 81b9344b9aea0386fabd195901a365a69a10c5fc..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 973
zcmZ`%&2H2%5VrHb*`$=E;>H6+LK|^Ms1njb5A@PogcP~!NjD`wi=Az?T;W0B$Se8E
ziC5snOxCokrFG=*^UT=s=a~^{8Z#X3JcAc5W53AQA08T~IQ0TSGRYg(@`7{rj!8$l
z-<WiPUprsj!bOiKef0R&<Dn;zA$mgV@nv+uvdM4!7t6SrYEZRk>Mx-5l6?EaLE{vs
z{)hmq;F1*%xZk}Wtne)d$RXO1wI`Ni%TvpV<<#<#<tLJ(9><(~fVNlLv##nd?j)UO
z$0jPvPP9;#CN9gimz##xNm+j0h-Md2B-A8l-2hjh7Bw`|_(MO4#!SSGs2g$FfQc7P
zFNR$-T!UIdHyCfDK^m`8045O2p}qkV)tz01mz%1>%$Q&)mMf4&pjSeH{K?b|uN>je
zJYV%K<e0=<UW@LkFJI+)t808oKEhs#=j*M)8Z(;u1R>)8f8&nFi$TW@i(!-a^zC|c
zn883%11X;%AfRL^YB}SPy!)5zR?jF*cO2u?v^nCV{kWo+xam-lEibhPwM&Q`Ay2H*
z*?Xbnq15<6sUiMdMFa^!N<i|}l;Exod+MKKfS#f0)W7^H@}6gbIZ~j9vQpSox4rtb
hYo7SN>BjVrFCLFPbc2ar?>g}fr)wy!i8D)Q?q6s-)7Jn1

diff --git a/Web Development & Frameworks/Django/info/__pycache__/urls.cpython-39.pyc b/Web Development & Frameworks/Django/info/__pycache__/urls.cpython-39.pyc
deleted file mode 100755
index 6f97f530e6e518882f98a69411245709cd262daf..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 349
zcmYk2&q~BF5XO`KOSQY=TS!H=coz}8D5w|3LoQ2j#%-l(OR`n^5Wa&ReWhHzxUV1x
zPP)6W6Y>qe8RnZ1HJ$D=3UiX<59MzUyCDcJ=-L|+V8Cmpx#XNd0AU?GFys(n_z`_F
zh#-Csi4%-RPBtts8CiH<gi=6y&+@$$IkKF)s8h>w#n-@(Wuj5HX7HUxX_Vnp*UP9>
z2JZ6IW$>b!MLX+FZB0N!E`F`>&B}w@aqPNzZXc=OgtBwrk=bR}Z>w^0MLt_{8M)B*
zC7Q;5G2_2tl;5MGY&90Du8Q@(`DtMXTakG&ieEqL2A7`c7Wx{`{rjyqnD8_><aGZ2
E0SyUV?*IS*

diff --git a/Web Development & Frameworks/Django/info/__pycache__/views.cpython-39.pyc b/Web Development & Frameworks/Django/info/__pycache__/views.cpython-39.pyc
deleted file mode 100755
index c73472b96b69db297dd61751ee842bea275cceb1..0000000000000000000000000000000000000000
GIT binary patch
literal 0
HcmV?d00001

literal 1635
zcmbVM&2Aev5GMDByOP$9;<!!!&;~tai$p>$JrqHZqK7tzszqG%z{_GG()QXbtuo}=
za3G(OYk)k0ee^5w(nC*vg`PS?S(Xww2oM6Comp}?!|$76xv|k@IR1H<>ruqmzhtZr
z{KuZ+G&2;6DPFS)mz<Lx)WIZ_q1VGYn#3|jJyLNk{-SkJCo=KhRHnZ&m8kSJQ>hML
zg|dToM|IKedb^8uPi1Il-tH-}!}5(wjLLHE1n8;KfLikNpU?iT^f9XGb8TkL)aXmT
z*u{Ssjmcqs1ZX_PX|_>lCb?oVP+SGCnG98kK_a*LyPh;~@@%@>(9vV^Sq^~;f$#@T
z^CJq&&iFYy3(nbTWW#x+_#1v2&*QV`oWXsI+JSh*cbL}_6{zq{u){8*(FJ#rDs6fB
z7SlyT7+c!b<f#)g)7q+*n@1JcwycYZ&&MT2X;d|~a(k8Fj)tnNtCt#FTAAVqbp@0l
z5Rp!3fCfx1Tx4{;>k`l}T5YV0O4u__93InGb|^wo;e}}*R2K~HqWgdMhx^S$5Ao2U
zIw+@mP4Q@GP7G}vdU1sKn8EDCg?rjkMC0p+XS~Z(oG-UlsS=h0+%~$1Tv`;<a-xgE
zb&F!ssJ13OD~cC*-^B`iNw=Uh*2EWNCMY^M4H1)aZ+{Zey<cYSjVx1yYnFdPW5Mz%
zvOA9|<ktrCSOv(mn2WOznSNlSxj2YD)1(O%s)(4*<B^L9E1;C2M<PR!C$Nbh*&EN=
zVy0oNr&iv+N@&F@^vU6xP`JHt-J-vDNKhTaXDDP!C;3R<(ZA10tl;y=5v1g0C<BHJ
z5l5b<TWe5wlHe=cvF7hj@`rqj3lx6|KiQuIfA(7m>PGzE>9WUoKH+ZzLi(IjXJN0!
zYrQ6rfq_l1*HX^_X`N-SL5c_DT@SbGs>&P|ttt1k3mWVIEXeV(f?K#pZY>k~2>t?Y
z!oRbR*I5woA?&}wC|4b_wM4$Z40_!kABO%O`hQJlTva~Vc_#ad<{X&)2JE=C254Pw
z19p0`3)pDK4IB=9vqDHqci&q=(?6ZQ(p-<;fW@m~JZ$hiI{7{WVjJ#}Sk=~bZMgLD
YqM4u26Ktq<Gkgm&UukLB@ANzW1Kd_(qW}N^

diff --git a/Web Development & Frameworks/Django/info/admin.py b/Web Development & Frameworks/Django/info/admin.py
deleted file mode 100755
index 8c38f3f..0000000
--- a/Web Development & Frameworks/Django/info/admin.py	
+++ /dev/null
@@ -1,3 +0,0 @@
-from django.contrib import admin
-
-# Register your models here.
diff --git a/Web Development & Frameworks/Django/info/apps.py b/Web Development & Frameworks/Django/info/apps.py
deleted file mode 100755
index 7da20ee..0000000
--- a/Web Development & Frameworks/Django/info/apps.py	
+++ /dev/null
@@ -1,6 +0,0 @@
-from django.apps import AppConfig
-
-
-class InfoConfig(AppConfig):
-    default_auto_field = "django.db.models.BigAutoField"
-    name = "info"
diff --git a/Web Development & Frameworks/Django/info/models.py b/Web Development & Frameworks/Django/info/models.py
deleted file mode 100755
index 71a8362..0000000
--- a/Web Development & Frameworks/Django/info/models.py	
+++ /dev/null
@@ -1,3 +0,0 @@
-from django.db import models
-
-# Create your models here.
diff --git a/Web Development & Frameworks/Django/info/serializers.py b/Web Development & Frameworks/Django/info/serializers.py
deleted file mode 100755
index ec839fa..0000000
--- a/Web Development & Frameworks/Django/info/serializers.py	
+++ /dev/null
@@ -1,24 +0,0 @@
-from rest_framework import serializers
-
-class MemoryInfoSerializer(serializers.Serializer):
-    total = serializers.IntegerField()
-    available = serializers.IntegerField()
-    percent = serializers.FloatField()
-    used = serializers.IntegerField()
-    free = serializers.IntegerField()
-    active = serializers.IntegerField()
-    inactive = serializers.IntegerField()
-    buffers = serializers.IntegerField()
-    cached = serializers.IntegerField()
-    shared = serializers.IntegerField()
-    
-    
-class CpuInfoSerializer(serializers.Serializer):
-    info = serializers.FloatField()
-
-class HardInfoSerializer(serializers.Serializer):
-    total = serializers.IntegerField()
-    used = serializers.IntegerField()
-    free = serializers.IntegerField()
-    percent = serializers.FloatField()
-    
diff --git a/Web Development & Frameworks/Django/info/tests.py b/Web Development & Frameworks/Django/info/tests.py
deleted file mode 100755
index 7ce503c..0000000
--- a/Web Development & Frameworks/Django/info/tests.py	
+++ /dev/null
@@ -1,3 +0,0 @@
-from django.test import TestCase
-
-# Create your tests here.
diff --git a/Web Development & Frameworks/Django/info/urls.py b/Web Development & Frameworks/Django/info/urls.py
deleted file mode 100755
index a9ac88a..0000000
--- a/Web Development & Frameworks/Django/info/urls.py	
+++ /dev/null
@@ -1,7 +0,0 @@
-from django.urls import path
-from .views import *
-urlpatterns = [
-    path("memory",  MemoryInfoView.as_view(),name="memory"),
-    path("cpu", CpuInfoView.as_view(),name="cpu"),
-    path("hard",HardInfoView.as_view(),name='hard'),
-]
\ No newline at end of file
diff --git a/Web Development & Frameworks/Django/info/views.py b/Web Development & Frameworks/Django/info/views.py
deleted file mode 100755
index a80027b..0000000
--- a/Web Development & Frameworks/Django/info/views.py	
+++ /dev/null
@@ -1,34 +0,0 @@
-from django.shortcuts import render
-from rest_framework.views import APIView
-from rest_framework.response import Response
-from .serializers import *
-import psutil
-import os
-# Create your views here.
-
-class MemoryInfoView(APIView):
-    def get(self, request, *args, **kwargs):
-        memo_info = psutil.virtual_memory()._asdict()
-        seri = MemoryInfoSerializer(data=memo_info)
-        if seri.is_valid():
-            return Response(seri.data)
-        return Response(seri.errors,status=400)
-
-
-class CpuInfoView(APIView):
-    def get(self, request, *args, **kwargs):
-        cpu_info = psutil.cpu_percent()
-        info = {"info":cpu_info}
-        seri= CpuInfoSerializer(data=info)
-        if seri.is_valid():
-            return Response(seri.data)
-        return Response(seri.errors,status=400)
-
-class HardInfoView(APIView):
-    def get(self,request,*args,**kwargs):
-        hard_info = psutil.disk_usage(os.getcwd())._asdict()
-        seri = HardInfoSerializer(data=hard_info)
-        if seri.is_valid():
-            return Response(seri.data)
-        return Response(seri.errors,status=400)
-
diff --git a/Web Development & Frameworks/Django/manage.py b/Web Development & Frameworks/Django/manage.py
deleted file mode 100755
index 8e9accf..0000000
--- a/Web Development & Frameworks/Django/manage.py	
+++ /dev/null
@@ -1,22 +0,0 @@
-#!/usr/bin/env python
-"""Django's command-line utility for administrative tasks."""
-import os
-import sys
-
-
-def main():
-    """Run administrative tasks."""
-    os.environ.setdefault("DJANGO_SETTINGS_MODULE", "sysinfo.settings")
-    try:
-        from django.core.management import execute_from_command_line
-    except ImportError as exc:
-        raise ImportError(
-            "Couldn't import Django. Are you sure it's installed and "
-            "available on your PYTHONPATH environment variable? Did you "
-            "forget to activate a virtual environment?"
-        ) from exc
-    execute_from_command_line(sys.argv)
-
-
-if __name__ == "__main__":
-    main()
diff --git a/Web Development & Frameworks/Django/sys_info.md b/Web Development & Frameworks/Django/sys_info.md
deleted file mode 100755
index ba5df9f..0000000
--- a/Web Development & Frameworks/Django/sys_info.md	
+++ /dev/null
@@ -1,40 +0,0 @@
-جمع‌آوری اطلاعات سیستم با استفاده از Django و Django Rest Framework
-مقدمه
-در این پروژه، از Django و Django Rest Framework استفاده شده‌است تا اطلاعاتی از سیستم مانند CPU، حافظه و ... جمع‌آوری شود.
-
-راه‌اندازی
-نصب مورد نیازها
-برای نصب وابستگی‌های مورد نیاز:
-
-bash
-Copy code
-pip install -r requirements.txt
-راه‌اندازی دیتابیس
-برای مهاجرت دیتابیس، دستورات زیر را اجرا کنید:
-
-bash
-Copy code
-python manage.py makemigrations
-python manage.py migrate
-اجرای سرور
-برای اجرای سرور توسط Django:
-
-bash
-Copy code
-python manage.py runserver
-API ها
-دریافت اطلاعات CPU
-
-URL: /api/cpu_info/
-روش: GET
-خروجی: اطلاعات مربوط به CPU
-دریافت اطلاعات حافظه
-
-URL: /api/memory_info/
-روش: GET
-خروجی: اطلاعات مربوط به حافظه
-... (و همین طور برای سایر API ها)
-
-جمع‌بندی
-این پروژه به شما امکان می‌دهد تا با استفاده از یک وب API ساده، اطلاعات مختلف سیستم را مشاهده کنید.
-
diff --git a/Web Development & Frameworks/nginx/Laravel.md b/Web Development & Frameworks/nginx/Laravel.md
deleted file mode 100755
index 12a8103..0000000
--- a/Web Development & Frameworks/nginx/Laravel.md	
+++ /dev/null
@@ -1,153 +0,0 @@
-
-# Deploying a Laravel Application on Nginx
-
-This guide covers the steps to deploy a Laravel application on an Nginx web server. You’ll configure Nginx, install PHP and required extensions, set up Composer, and secure your Laravel application.
-
----
-
-## Prerequisites
-
-- **A Linux server** with root or sudo privileges.
-- **Nginx installed** or installation instructions are provided below.
-- **PHP and required extensions** for running Laravel applications.
-- **Composer installed** for managing Laravel dependencies.
-  
----
-
-## Step 1: Install Nginx
-
-1. **Update the package list**:
-   ```bash
-   sudo apt update
-   ```
-
-2. **Install Nginx**:
-   ```bash
-   sudo apt install nginx
-   ```
-
----
-
-## Step 2: Configure Nginx for Laravel
-
-1. **Open the default Nginx configuration file**:
-   ```bash
-   sudo nano /etc/nginx/sites-available/default
-   ```
-
-2. **Replace the existing content** with the following configuration. Make sure to replace `your_domain.com` with your domain or server’s IP address.
-
-   ```nginx
-   server {
-       listen 80;
-       server_name your_domain.com;
-       root /var/www/html/your_laravel_project/public;
-
-       index index.php index.html index.htm;
-
-       location / {
-           try_files $uri $uri/ /index.php?$query_string;
-       }
-
-       location ~ \.php$ {
-           include snippets/fastcgi-php.conf;
-           fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;  # Adjust PHP version if necessary
-       }
-
-       location ~ /\.ht {
-           deny all;
-       }
-   }
-   ```
-
-3. **Save and close the file**.
-
-4. **Test the Nginx configuration** for syntax errors:
-   ```bash
-   sudo nginx -t
-   ```
-
-5. **Restart Nginx** to apply the new configuration:
-   ```bash
-   sudo systemctl restart nginx
-   ```
-
----
-
-## Step 3: Install PHP and Required Extensions
-
-1. **Add the PHP PPA repository**:
-   ```bash
-   sudo add-apt-repository ppa:ondrej/php
-   sudo apt update
-   ```
-
-2. **Install PHP and required extensions** for Laravel:
-   ```bash
-   sudo apt install php7.4-fpm php7.4-mbstring php7.4-xml php7.4-zip php7.4-mysql php7.4-curl php7.4-gd
-   ```
-
----
-
-## Step 4: Install Composer
-
-1. **Download and install Composer globally**:
-   ```bash
-   curl -sS https://getcomposer.org/installer | sudo php -- --install-dir=/usr/local/bin --filename=composer
-   ```
-
----
-
-## Step 5: Deploy the Laravel Application
-
-1. **Clone or upload your Laravel project** to the Nginx web root:
-   ```bash
-   sudo mkdir -p /var/www/html/your_laravel_project
-   # Clone or upload your project files here
-   ```
-
-2. **Set appropriate permissions** for the Laravel `storage` and `bootstrap/cache` directories:
-   ```bash
-   cd /var/www/html/your_laravel_project
-   sudo chown -R www-data:www-data storage bootstrap/cache
-   sudo chmod -R 775 storage bootstrap/cache
-   ```
-
-3. **Install Laravel dependencies** with Composer:
-   ```bash
-   cd /var/www/html/your_laravel_project
-   composer install --no-dev --optimize-autoloader
-   ```
-
-4. **Generate an application key** for Laravel:
-   ```bash
-   php artisan key:generate
-   ```
-
----
-
-## Step 6: Restart PHP-FPM
-
-Restart PHP-FPM to apply any changes:
-```bash
-sudo systemctl restart php7.4-fpm  # Adjust PHP version as needed
-```
-
----
-
-## Summary and Final Checks
-
-Your Laravel application should now be deployed and accessible through Nginx. Visit `http://your_domain.com` in a browser to confirm that the application is working.
-
----
-
-## Additional Notes
-
-- **Security**: Ensure the `APP_ENV` in your `.env` file is set to `production` for live applications.
-- **Permissions**: For added security, periodically review file and folder permissions, particularly within the `storage` and `bootstrap/cache` directories.
-- **SSL/TLS**: For a production environment, set up SSL using [Certbot](https://certbot.eff.org/) for secure HTTPS access.
-
-This guide provides the foundational steps to deploy a Laravel application on Nginx. Customize configurations further as per your project requirements.
-
-## Author
-[alinuxist](https://github.com/alinuxist)
diff --git a/Web Development & Frameworks/nginx/django.md b/Web Development & Frameworks/nginx/django.md
deleted file mode 100755
index dfd31d4..0000000
--- a/Web Development & Frameworks/nginx/django.md	
+++ /dev/null
@@ -1,206 +0,0 @@
-### Installing Packages from Ubuntu Repositories
-
-1. Update your Ubuntu system:
-    ```bash
-    sudo apt update
-    ```
-
-2. Install necessary packages:
-    ```bash
-    sudo apt install python3-venv python3-dev libpq-dev postgresql postgresql-contrib nginx curl
-    ```
-
-### Creating the PostgreSQL Database and User
-
-3. Log into an interactive Postgres session:
-    ```bash
-    sudo -u postgres psql
-    ```
-
-4. Inside the PostgreSQL prompt, create a database for your project:
-    ```sql
-    CREATE DATABASE myproject;
-    ```
-
-5. Create a database user for your project with a secure password:
-    ```sql
-    CREATE USER myprojectuser WITH PASSWORD 'password';
-    ```
-
-6. Modify connection parameters for the user:
-    ```sql
-    ALTER ROLE myprojectuser SET client_encoding TO 'utf8';
-    ALTER ROLE myprojectuser SET default_transaction_isolation TO 'read committed';
-    ALTER ROLE myprojectuser SET timezone TO 'UTC';
-    ```
-
-7. Grant the new user access to administer the new database:
-    ```sql
-    GRANT ALL PRIVILEGES ON DATABASE myproject TO myprojectuser;
-    ```
-
-8. Exit the PostgreSQL prompt:
-    ```sql
-    \q
-    ```
-
-### Creating a Python Virtual Environment for Your Project
-
-9. Create a directory for your project files:
-    ```bash
-    mkdir ~/myprojectdir
-    cd ~/myprojectdir
-    ```
-
-10. Create a Python virtual environment:
-    ```bash
-    python3 -m venv myprojectenv
-    ```
-
-11. Activate the virtual environment:
-    ```bash
-    source myprojectenv/bin/activate
-    ```
-
-12. Install Django, Gunicorn, and psycopg2:
-    ```bash
-    pip install django gunicorn psycopg2-binary
-    ```
-
-### Creating and Configuring a New Django Project
-
-13. Create a new Django project with a defined directory:
-    ```bash
-    django-admin startproject myproject ~/myprojectdir
-    ```
-
-14. Adjust settings in the `settings.py` file:
-    - Set `ALLOWED_HOSTS` to `['*']`
-    - Configure `DATABASES` with PostgreSQL details
-
-15. Add static root configuration to `settings.py`:
-    ```python
-    import os
-    STATIC_ROOT = os.path.join(BASE_DIR, 'static/')
-    ```
-
-16. Migrate initial database schema:
-    ```bash
-    ~/myprojectdir/manage.py makemigrations
-    ~/myprojectdir/manage.py migrate
-    ```
-
-17. Create an administrative user:
-    ```bash
-    ~/myprojectdir/manage.py createsuperuser
-    ```
-
-18. Collect static content:
-    ```bash
-    ~/myprojectdir/manage.py collectstatic
-    ```
-
-19. Allow port 8000:
-    ```bash
-    sudo ufw allow 8000
-    ```
-
-20. Start Django development server:
-    ```bash
-    ~/myprojectdir/manage.py runserver 0.0.0.0:8000
-    ```
-
-21. Access your application in a web browser.
-
-22. Stop Apache2 service:
-    ```bash
-    sudo /etc/init.d/apache2 restart
-    ```
-
-### Testing Gunicorn
-
-23. Test Gunicorn to ensure it can serve the application:
-    ```bash
-    cd ~/myprojectdir
-    gunicorn --bind 0.0.0.0:8000 myproject.wsgi
-    ```
-
-24. Stop Gunicorn:
-    - Press `CTRL-C`
-
-### Creating systemd Socket and Service Files for Gunicorn
-
-25. Create a systemd socket file for Gunicorn:
-    ```bash
-    sudo nano /etc/systemd/system/gunicorn.socket
-    ```
-
-26. Create and open a systemd service file for Gunicorn:
-    ```bash
-    sudo nano /etc/systemd/system/gunicorn.service
-    ```
-
-27. Configure the service file with appropriate details.
-
-### Checking for the Gunicorn Socket File
-
-28. Check the status of the Gunicorn socket:
-    ```bash
-    sudo systemctl status gunicorn.socket
-    ```
-
-29. Check for the existence of the Gunicorn socket file:
-    ```bash
-    file /run/gunicorn.sock
-    ```
-
-30. Check Gunicorn socket logs:
-    ```bash
-    sudo journalctl -u gunicorn.socket
-    ```
-
-### Testing Socket Activation
-
-31. Test the socket activation mechanism:
-    ```bash
-    sudo systemctl status gunicorn
-    ```
-
-32. Send a connection to the socket through curl:
-    ```bash
-    curl --unix-socket /run/gunicorn.sock localhost
-    ```
-
-### Configuring Nginx to Proxy Pass to Gunicorn
-
-33. Create and open a new server block in Nginx's sites-available directory:
-    ```bash
-    sudo nano /etc/nginx/sites-available/myproject
-    ```
-
-34. Configure the server block with appropriate settings.
-
-35. Enable the server block:
-    ```bash
-    sudo ln -s /etc/nginx/sites-available/myproject /etc/nginx/sites-enabled
-    ```
-
-36. Test Nginx configuration for syntax errors:
-    ```bash
-    sudo nginx -t
-    ```
-
-37. Restart Nginx:
-    ```bash
-    sudo systemctl restart nginx
-    ```
-
-38. Open firewall to normal traffic on port 80:
-    ```bash
-    sudo ufw delete allow 8000
-    sudo ufw allow 'Nginx Full'
-    ```
-
-### Conclusion
-
-You should now be able to access your Django application via your server's domain or IP address.
diff --git a/Web Development & Frameworks/nginx/dotnet.md b/Web Development & Frameworks/nginx/dotnet.md
deleted file mode 100755
index 3916112..0000000
--- a/Web Development & Frameworks/nginx/dotnet.md	
+++ /dev/null
@@ -1,114 +0,0 @@
-# Deploying .NET on Linux
-
-This tutorial has been tested only on .NET 7 and Ubuntu 22.04.
-
-## Getting the Output
-
-First, let's install .NET:
-```bash
-sudo apt install dotnet-sdk-7.0
-```
-*Note: You can create a .NET project using `dotnet new mvc` command.*
-
-Then, we need to publish our project:
-```bash
-dotnet publish
-```
-The location of the output file will be displayed after the command finishes. Typically, the project output will be placed in:
-**bin/Debug/net7.0/publish**
-
-## Installing Nginx
-
-**Nginx** is a high-performance web server with low resource usage, distributed under the terms of the BSD license. It runs on Unix-like operating systems and is widely used, currently powering 12.07% of the internet's domains.
-
-To install **Nginx** via `apt`, use the following command:
-```bash
-sudo apt install nginx
-```
-
-Then, disable the firewall with:
-```bash
-sudo ufw disable
-```
-If you encounter an error with this command, it means you don't have a firewall. In that case, skip this part.
-
-If the installation is successful, you should see "Welcome to Nginx" when typing `localhost` in your browser.
-
-## Configuring Nginx
-
-Create a directory for your site:
-```bash
-sudo mkdir /var/www/app1 
-```
-
-Copy the contents of the `publish` directory to the newly created directory:
-```bash
-sudo cp yourprojectFolder/bin/Debug/net7.0/publish /var/www/app1
-```
-
-Then, navigate to the Nginx configuration:
-```bash
-sudo vim /etc/nginx/sites-available/default
-```
-
-Replace the contents of the file with the following:
-```nginx
-server {
-    listen        80;
-    server_name   example.com *.example.com;
-    location / {
-        proxy_pass         http://localhost:5000;
-        proxy_http_version 1.1;
-        proxy_set_header   Upgrade $http_upgrade;
-        proxy_set_header   Connection keep-alive;
-        proxy_set_header   Host $host;
-        proxy_cache_bypass $http_upgrade;
-        proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
-        proxy_set_header   X-Forwarded-Proto $scheme;
-    }
-}
-```
-*Note: Replace `example.com` with your site address.*
-
-Check the configuration file syntax:
-```bash
-sudo nginx -t
-```
-
-If no errors are reported, reload Nginx to apply the changes:
-```bash
-sudo nginx -s reload
-```
-
-## Adding the Site as a Service
-
-Create a service file for your site:
-```bash
-sudo vim /etc/systemd/system/app1.service
-```
-
-Copy the following code into the file:
-```plaintext
-[Unit] 
-Description=dotnet webapp
-[Service] 
-WorkingDirectory=/var/www/app1
-ExecStart=/usr/bin/dotnet /var/www/app/projectname.dll 
-Restart=always
-RestartSec=10
-SyslogIdentifier=projectname
-Environment=ASPNETCORE_ENVIRONMENT=Production
-    
-[Install]
-WantedBy=multi-user.target
-```
-*Note: Replace `projectname` with your project's name.*
-
-Enable and start the site, and check its status:
-```bash
-sudo systemctl enable app1.service
-sudo systemctl start app1.service
-sudo systemctl status app1.service
-```
-## Author
-[Mahdiyar Abdollahi](https://github.com/IAmMahdiyar)

From b289bd1d6c86cd7f46c850ece3a5203412669885 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 2 Jul 2025 00:02:21 +0330
Subject: [PATCH 027/116] update lpic: grep doc

---
 Linux/LPIC1/12-grep.md | 85 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 85 insertions(+)

diff --git a/Linux/LPIC1/12-grep.md b/Linux/LPIC1/12-grep.md
index e69de29..94b84ae 100644
--- a/Linux/LPIC1/12-grep.md
+++ b/Linux/LPIC1/12-grep.md
@@ -0,0 +1,85 @@
+# 📘 **Using `grep` in Linux/Unix**
+
+`grep` (Global Regular Expression Print) is a powerful command-line utility used to search for text patterns in files. Below are common variations of the `grep` command with examples and explanations.
+
+---
+
+## 🔍 Basic Search
+
+```bash
+grep "hello" file1
+```
+
+**Description**:
+Searches for lines containing the word `hello` in `file1`. The search is **case-sensitive**.
+
+---
+
+## 🔍 Case-Insensitive Search
+
+```bash
+grep -i "hello" file1
+```
+
+**Description**:
+Performs a **case-insensitive** search for `hello` in `file1`. Matches `hello`, `Hello`, `HELLO`, etc.
+
+---
+
+## 🔢 Show Line Numbers
+
+```bash
+grep -n "hello" file1
+```
+
+**Description**:
+Displays matching lines **with their line numbers**.
+
+---
+
+## 🔢 Case-Insensitive with Line Numbers
+
+```bash
+grep -in "hello" file1
+```
+
+**Description**:
+Combines `-i` and `-n` to show line numbers and ignore case.
+
+---
+
+## 🚫 Invert Match
+
+```bash
+grep -v "hello" file1
+```
+
+**Description**:
+Shows lines that **do NOT** contain the word `hello`.
+
+---
+
+## 🚫 Invert, Ignore Case, and Show Line Numbers
+
+```bash
+grep -ivn "hello" file1
+```
+
+**Description**:
+Combines all the above:
+
+* `-i`: Ignore case
+* `-v`: Invert match
+* `-n`: Show line numbers
+  Shows all lines that **don’t contain** `hello`, regardless of case, and includes line numbers.
+
+---
+
+## ✅ Summary of Flags
+
+| Flag | Description                |
+| ---- | -------------------------- |
+| `-i` | Ignore case                |
+| `-n` | Show line numbers          |
+| `-v` | Invert the match (exclude) |
+

From 06d3798339acf00e5104e682f40031b10d14a535 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 2 Jul 2025 00:08:13 +0330
Subject: [PATCH 028/116] update lpic: less doc

---
 Linux/LPIC1/13-less.md | 45 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 45 insertions(+)

diff --git a/Linux/LPIC1/13-less.md b/Linux/LPIC1/13-less.md
index e69de29..c7cfa4d 100644
--- a/Linux/LPIC1/13-less.md
+++ b/Linux/LPIC1/13-less.md
@@ -0,0 +1,45 @@
+# 📘 **Using `less` in Linux/Unix**
+
+`less` is a terminal pager program used to view the content of files one screen at a time. It's especially useful for viewing large files or logs.
+
+---
+
+## 📂 Basic Usage
+
+```bash
+less file
+```
+
+**Description**:
+Opens `file` for viewing.
+
+```bash
+less /var/log/syslog
+```
+
+**Description**:
+Opens the system log file for reading. Useful for examining system logs line by line.
+
+---
+
+## ⌨️ Common Keyboard Shortcuts
+
+Here are the most frequently used keyboard shortcuts when using `less`:
+
+| Key/Command | Action                               |
+| ----------- | ------------------------------------ |
+| `space`     | Scroll **down** one screen           |
+| `b`         | Scroll **up** one screen             |
+| `q`         | **Quit** `less`                      |
+| `/pattern`  | **Search** forward for `pattern`     |
+| `n`         | Go to the **next** match of pattern  |
+| `N`         | Go to the **previous** match         |
+| `g`         | Go to the **first line** of the file |
+| `G`         | Go to the **last line** of the file  |
+
+---
+
+## ✅ Summary
+
+`less` is a vital tool for system administrators, developers, and anyone dealing with large text files. With simple navigation and powerful search capabilities, it makes file reading efficient and user-friendly.
+

From 18d704e2d5f41a979715d7730e2c101046513eff Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 2 Jul 2025 01:09:17 +0330
Subject: [PATCH 029/116] update lpic: head,tail,wc doc

---
 Linux/LPIC1/14-head-tail.md | 77 +++++++++++++++++++++++++++++++++++++
 Linux/LPIC1/15-wc.md        | 52 +++++++++++++++++++++++++
 2 files changed, 129 insertions(+)

diff --git a/Linux/LPIC1/14-head-tail.md b/Linux/LPIC1/14-head-tail.md
index e69de29..764a709 100644
--- a/Linux/LPIC1/14-head-tail.md
+++ b/Linux/LPIC1/14-head-tail.md
@@ -0,0 +1,77 @@
+# 📘 **Using `head` and `tail` Commands in Linux/Unix**
+
+Both `head` and `tail` are essential commands for viewing specific portions of a file quickly, without opening the entire file.
+
+---
+
+## 🔝 `head` — Show the Top of a File
+
+The `head` command displays the beginning part of a file.
+
+### Syntax
+
+```bash
+head [options] file
+```
+
+### Examples
+
+```bash
+head file1
+```
+
+**Description**:
+Displays the first 10 lines of `file1` (default behavior).
+
+```bash
+head -n 5 file1
+```
+
+**Description**:
+Shows the first 5 lines of `file1`.
+
+---
+
+## 🔚 `tail` — Show the Bottom of a File
+
+The `tail` command displays the end part of a file.
+
+### Syntax
+
+```bash
+tail [options] file
+```
+
+### Examples
+
+```bash
+tail file1
+```
+
+**Description**:
+Displays the last 10 lines of `file1` (default behavior).
+
+```bash
+tail -n 20 file1
+```
+
+**Description**:
+Shows the last 20 lines of `file1`.
+
+```bash
+tail -f file1
+```
+
+**Description**:
+Follows the file as it grows — useful for watching logs in real-time.
+
+---
+
+## ✅ Summary of Options
+
+| Command | Option        | Description                                 |
+| ------- | ------------- | ------------------------------------------- |
+| `head`  | `-n <number>` | Show the first `<number>` lines             |
+| `tail`  | `-n <number>` | Show the last `<number>` lines              |
+| `tail`  | `-f`          | Follow the file in real-time (live updates) |
+
diff --git a/Linux/LPIC1/15-wc.md b/Linux/LPIC1/15-wc.md
index e69de29..283841d 100644
--- a/Linux/LPIC1/15-wc.md
+++ b/Linux/LPIC1/15-wc.md
@@ -0,0 +1,52 @@
+# 📘 **Using the `wc` Command in Linux/Unix**
+
+`wc` (word count) is a utility that counts lines, words, and bytes or characters in files. It’s useful for quickly getting file size details in text terms.
+
+---
+
+## ⚙️ Syntax
+
+```bash
+wc [option] file
+```
+
+---
+
+## 🔎 Basic Usage
+
+```bash
+wc file
+```
+
+**Example output:**
+
+```
+ 5  6 43 file1
+```
+
+This output means:
+
+| Number | Meaning             |
+| ------ | ------------------- |
+| `5`    | Number of **lines** |
+| `6`    | Number of **words** |
+| `43`   | Number of **bytes** |
+
+---
+
+## 📋 Common Options
+
+| Option | Description               | Example      |
+| ------ | ------------------------- | ------------ |
+| `-l`   | Count **lines** only      | `wc -l file` |
+| `-w`   | Count **words** only      | `wc -w file` |
+| `-c`   | Count **bytes** only      | `wc -c file` |
+| `-m`   | Count **characters** only | `wc -m file` |
+
+---
+
+## 📌 Notes
+
+* `bytes (-c)` counts raw bytes, which might differ from characters (`-m`) in multibyte encodings like UTF-8.
+* Without options, `wc` outputs lines, words, and bytes by default.
+

From 148698fcc0aab617cde7011cca42a04626aae33d Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sat, 5 Jul 2025 21:26:54 +0330
Subject: [PATCH 030/116] updated kuber: svc doc

---
 .../Kubernetes/Commands/3-Commands.md         | 13 ---
 .../Kubernetes/workloads/09-Services.md       | 82 +++++++++++++------
 2 files changed, 55 insertions(+), 40 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md b/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md
index a0f3ca5..02f0118 100755
--- a/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md	
+++ b/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md	
@@ -106,19 +106,6 @@ This guide provides a concise reference for common `kubectl` commands used to ma
 
 ---
 
-## Port Forwarding
-
-Sometimes you need to access a service or pod directly from your local machine. Use the following command to forward a port:
-
-```bash
-kubectl port-forward -n <namespace-name> svc/<service-name> <local-port>:<target-port>
-```
-
-> **Example:** Forward local port 8080 to port 80 of the service named `my-service` in the `mynamespace` namespace:
->
-> ```bash
-> kubectl port-forward -n mynamespace svc/my-service 8080:80
-> ```
 
 ---
 
diff --git a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md
index 4700b38..aa5f782 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md	
@@ -1,43 +1,46 @@
-# 🔗 Services in Kubernetes (SVC)
+# 🔗 **Kubernetes Services (SVC)**
 
-A **Service** in Kubernetes provides a stable networking interface to access a set of pods. It allows for decoupling between client applications and the underlying pods by using DNS names and selectors.
+A **Service** in Kubernetes provides a stable network endpoint to access a set of Pods. It abstracts access through selectors and DNS names, enabling loose coupling between client applications and Pods.
 
 ---
 
-## 🌐 Service Basics
+## 🌐 **Service Basics**
 
-### 📌 Service Flow
+### 📌 **Service Flow**
+
+```
+Service ➡️ Endpoint ➡️ Pods
 ```
 
-Service ➡️ Endpoint ➡️ Pods
-
-````
-
-- Services abstract access to a group of pods.
-- Services automatically get a DNS name in the cluster.
-- They use selectors to route traffic to matching pods.
+* Services **group Pods** behind a single access point.
+* They get a **cluster-wide DNS name** automatically.
+* Use **label selectors** to forward traffic to matching Pods.
 
 ---
 
-## 🧭 Service Types
+## 🧭 **Types of Services**
 
-1. **ClusterIP** (default)  
-   - Accessible only within the cluster.
+1. **ClusterIP** (default)
 
-2. **NodePort**  
-   - Exposes the service on a static port on each node.
+   * Only reachable within the cluster.
 
-3. **LoadBalancer**  
-   - Provisions an external IP via a cloud provider to expose the service.
+2. **NodePort**
+
+   * Exposes the service via a static port on each node.
+
+3. **LoadBalancer**
+
+   * Creates an external IP address using a cloud provider.
 
 ---
 
-## 🧪 Useful Commands
+## 🧪 **Useful Commands**
 
 ### 🔍 Get Endpoints
+
 ```bash
 kubectl get ep -n <namespace>
-````
+```
 
 ### 📄 Get Services
 
@@ -47,7 +50,33 @@ kubectl get svc -n <namespace>
 
 ---
 
-## 🧾 Example Service Manifest
+## 🔁 **Port Forwarding**
+
+To access a service from your local machine, forward a local port to the service port:
+
+```bash
+kubectl port-forward -n <namespace> svc/<service-name> <local-port>:<target-port>
+```
+
+> **Example:**
+> Forward local port `8080` to port `80` of `my-service` in the `mynamespace` namespace:
+>
+> ```bash
+> kubectl port-forward -n mynamespace svc/my-service 8080:80
+> ```
+
+You can also bind to all network interfaces:
+
+```bash
+kubectl port-forward -n <namespace> svc/nginx 80:80 --address 0.0.0.0
+```
+
+> 🌐 **DNS format:**
+> `<service-name>.<namespace>.svc.cluster.local`
+
+---
+
+## 🧾 **Example Service Manifest**
 
 ```yaml
 apiVersion: v1
@@ -62,12 +91,11 @@ spec:
   selector:
     app: nginx
   ports:
-    - name: http  # Port name is optional but useful
-      port: 80  # Service port
-      targetPort: 8080  # Container port
+    - name: http
+      port: 80
+      targetPort: 8080
 ```
 
-> 🔍 **Note:** The `selector` must match pod labels for the service to route traffic correctly.
-> 🧠 **Tip:** Use `kubectl describe svc <svc-name>` to troubleshoot or verify service-to-pod connectivity.
-> 🌐 Services are resolved by DNS using the format: `<service-name>.<namespace>.svc.cluster.local`.
+> 🔍 **Note:** The `selector` must match the labels of the target Pods.
+> 🧠 **Tip:** Use `kubectl describe svc <service-name>` to inspect the service and verify connectivity.
 

From bbb5e2f7c24abd83261e2a19925430367ccb8d52 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 7 Jul 2025 19:59:00 +0330
Subject: [PATCH 031/116] update kuber: pv doc

---
 .../Kubernetes/workloads/11-Pv.md             | 127 ++++++++++++++++++
 1 file changed, 127 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/11-Pv.md

diff --git a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md b/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md
new file mode 100644
index 0000000..c749197
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md	
@@ -0,0 +1,127 @@
+Here's a clean, organized, and visually appealing document version of your input on **Persistent Volumes (PV) in Kubernetes**:
+
+---
+
+# 🌐 Kubernetes: Persistent Volumes (PV) Cheat Sheet
+
+## 📦 What is a Persistent Volume (PV)?
+
+A **Persistent Volume** is a piece of storage in a Kubernetes cluster that has been provisioned by an administrator or dynamically provisioned using **StorageClasses**.
+
+---
+
+## 📁 PV Storage Options
+
+1. **HostPath**
+
+   * Mounts a file or directory from the host node’s filesystem into your Pod.
+
+2. **Using PV and PVC**
+
+   * **PV (Persistent Volume):** The actual storage resource.
+   * **PVC (Persistent Volume Claim):** A request for storage by a user.
+
+---
+
+## 🧱 Kubernetes Storage Layers
+
+1. **Persistent Volume (PV)**
+2. **Persistent Volume Claim (PVC)**
+
+---
+
+## 🔄 PV Lifecycle States
+
+| State        | Description                                          |
+| ------------ | ---------------------------------------------------- |
+| Provisioning | Kubernetes is preparing the PV.                      |
+| Binding      | The PV is bound to a PVC.                            |
+| Using        | The bound PV is being used by a Pod.                 |
+| Releasing    | PVC is deleted; PV is no longer bound.               |
+| Reclaiming   | PV is reclaimed using one of the following policies: |
+|              |     • `Delete` – Remove the storage                  |
+|              |     • `Recycle` – Basic scrub (deprecated)           |
+|              |     • `Retain` – Manual reclaim                      |
+
+---
+
+## 🔒 PV Access Modes
+
+| Mode   | Description                                 |
+| ------ | ------------------------------------------- |
+| `RWO`  | **ReadWriteOnce** – One node can read/write |
+| `ROX`  | **ReadOnlyMany** – Many nodes read-only     |
+| `RWX`  | **ReadWriteMany** – Many nodes read/write   |
+| `RWOP` | **ReadWriteOncePod** – One Pod only         |
+
+---
+
+## 🛠️ Check PVs via CLI
+
+```bash
+kubectl get pv
+```
+
+---
+
+## 🚀 Example: Deployment using HostPath Volume
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-1
+  namespace: dev
+  labels:
+    label1: test1
+    app.kubernetes.io/label2: test2
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app.kubernetes.io/label2: test2
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/label2: test2
+        os: linux
+    spec:
+      containers:
+        - name: nginx
+          image: nginx
+          ports:
+            - containerPort: 80
+          volumeMounts:
+            - name: nginx-log
+              mountPath: /var/log/nginx  
+      volumes:
+        - name: nginx-log
+          hostPath:
+            path: /root/nginx/logs
+```
+
+---
+
+## 📂 Example: PersistentVolume with NFS
+
+```yaml
+apiVersion: v1
+kind: PersistentVolume
+metadata:
+  name: pv1
+spec:
+  capacity: 
+    storage: 5Gi
+  volumeMode: Filesystem
+  accessModes: 
+    - ReadWriteMany
+  persistentVolumeReclaimPolicy: Recycle
+  storageClassName: custom-name
+  mountOptions:
+    - hard
+    - nfsvers=4.1
+  nfs:
+    path: /nfs/data
+    server: 192.168.1.10
+```
+

From 7f69a7a8780fdf93dd0833f2689f6a948a833dd3 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 7 Jul 2025 20:13:03 +0330
Subject: [PATCH 032/116] echo and opreators

---
 Linux/Bash Script/1-Echo.md      | 60 +++++++++++++++++++++++
 Linux/Bash Script/2-Operators.md | 81 ++++++++++++++++++++++++++++++++
 2 files changed, 141 insertions(+)
 create mode 100644 Linux/Bash Script/1-Echo.md
 create mode 100644 Linux/Bash Script/2-Operators.md

diff --git a/Linux/Bash Script/1-Echo.md b/Linux/Bash Script/1-Echo.md
new file mode 100644
index 0000000..fc78d07
--- /dev/null
+++ b/Linux/Bash Script/1-Echo.md	
@@ -0,0 +1,60 @@
+### 📌 Echo Basic Usage
+
+```bash
+echo Hello, world!
+```
+
+**Output:**
+
+```
+Hello, world!
+```
+
+---
+
+### 💡 Common Use Cases
+
+1. **Print plain text:**
+
+   ```bash
+   echo This is a message
+   ```
+
+2. **Print environment variables (Linux/macOS):**
+
+   ```bash
+   echo $HOME
+   ```
+
+3. **Print environment variables (Windows):**
+
+   ```cmd
+   echo %USERNAME%
+   ```
+
+4. **Write to a file:**
+
+   ```bash
+   echo "Log entry" >> logfile.txt
+   ```
+
+5. **Suppress newline (Unix/Linux):**
+
+   ```bash
+   echo -n "No newline"
+   ```
+
+6. **Use with escape characters (Unix/Linux):**
+
+   ```bash
+   echo -e "Line1\nLine2"
+   ```
+
+---
+
+### ⚠️ Notes
+
+* On **Unix-like systems**, `echo` is a shell builtin (e.g., in `bash`, `sh`).
+* On **Windows**, it’s a command in `cmd.exe`.
+* Behavior may vary slightly between environments. For complex text handling, consider using `printf` instead in Unix/Linux.
+
diff --git a/Linux/Bash Script/2-Operators.md b/Linux/Bash Script/2-Operators.md
new file mode 100644
index 0000000..d97fa74
--- /dev/null
+++ b/Linux/Bash Script/2-Operators.md	
@@ -0,0 +1,81 @@
+
+# 🖥️ Bash Opreators
+
+A quick reference guide to essential bash command operators and their usage.
+
+---
+
+## `>` — **Write to File (Overwrite)**
+
+This operator **creates a new file** or **overwrites** the contents of an existing file.
+
+```bash
+echo "Hi" > file1
+```
+
+📄 *Creates* `file1` and writes `"Hi"` into it. If `file1` already exists, its content is replaced.
+
+---
+
+## `>>` — **Append to File**
+
+Adds content to the **end of an existing file** without deleting what's already there.
+
+```bash
+echo "Hi" >> file1
+```
+
+📝 *Appends* `"Hi"` to the end of `file1`.
+
+---
+
+## `&&` — **AND Operator**
+
+Runs the **second command only if the first succeeds**.
+
+```bash
+apt update && apt upgrade
+```
+
+🔗 `apt upgrade` runs only if `apt update` completes successfully.
+
+---
+
+## `;` — **Run Multiple Commands**
+
+Executes **commands sequentially**, regardless of success or failure.
+
+```bash
+echo "Hi" > file1 ; cat file1
+```
+
+🔄 Both commands are executed one after the other.
+
+---
+
+## `*` — **Wildcard (All Matching Files)**
+
+Matches **all files** that meet the pattern.
+
+```bash
+cat file*
+```
+
+🌐 Displays the contents of all files starting with `file`.
+
+---
+
+## `[ ... ]` — **Specific Character Matching**
+
+Reads files that match specific characters at the position defined in brackets.
+
+```bash
+cat file[1,2,3]
+```
+
+📚 Reads `file1`, `file2`, and `file3` (if they exist). Equivalent to:
+
+```bash
+cat file1 file2 file3
+```
+

From 89de2b1a0af504434b8d400be7405ef325f3acc2 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 7 Jul 2025 20:22:58 +0330
Subject: [PATCH 033/116] exit codes

---
 Linux/Bash Script/3-Exit-Codes.md | 95 +++++++++++++++++++++++++++++++
 1 file changed, 95 insertions(+)
 create mode 100644 Linux/Bash Script/3-Exit-Codes.md

diff --git a/Linux/Bash Script/3-Exit-Codes.md b/Linux/Bash Script/3-Exit-Codes.md
new file mode 100644
index 0000000..0f004e6
--- /dev/null
+++ b/Linux/Bash Script/3-Exit-Codes.md	
@@ -0,0 +1,95 @@
+# 🧾 Linux Exit Codes Cheat Sheet
+
+Every command in Linux returns an **exit status code** upon completion. You can check this code using:
+
+```bash
+command
+echo $?
+```
+
+These codes are helpful for debugging scripts or understanding command behavior.
+
+---
+
+## ✅ Common Exit Codes & Their Meanings
+
+| Exit Code | Meaning                                         |
+| --------- | ----------------------------------------------- |
+| `0`       | ✅ Success                                       |
+| `1`       | ❌ General Error                                 |
+| `2`       | ⚠️ Misuse of Shell Built-in (bad options, etc.) |
+| `126`     | 🚫 Command Found but Cannot Execute             |
+| `127`     | ❓ Command Not Found                             |
+| `130`     | ⌨️ Terminated by `Ctrl+C`                       |
+| `137`     | 💀 Killed (e.g., `kill -9`)                     |
+
+---
+
+## 🔍 Exit Code Examples
+
+### `0` — Success
+
+```bash
+echo "Hello"
+echo $?    # ➜ 0
+```
+
+---
+
+### `1` — General Error
+
+```bash
+grep "text" non_existing_file.txt
+echo $?    # ➜ 1
+```
+
+---
+
+### `2` — Misuse of Shell Built-in
+
+```bash
+ls --wrongoption
+echo $?    # ➜ 2
+```
+
+---
+
+### `126` — Command Found but Not Executable
+
+```bash
+touch myscript.sh
+chmod -x myscript.sh
+./myscript.sh
+echo $?    # ➜ 126
+```
+
+---
+
+### `127` — Command Not Found
+
+```bash
+nonexistentcommand
+echo $?    # ➜ 127
+```
+
+---
+
+### `130` — Script Terminated by `Ctrl+C`
+
+```bash
+sleep 10
+# Press Ctrl+C while it sleeps
+echo $?    # ➜ 130
+```
+
+---
+
+### `137` — Killed by `kill -9`
+
+```bash
+sleep 100 &
+kill -9 $!
+wait
+echo $?    # ➜ 137
+```
+

From eb764127302c23af19616098cbfc148c019a8a0c Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 7 Jul 2025 21:38:01 +0330
Subject: [PATCH 034/116] lipc1 doc: ps command

---
 Linux/LPIC1/16-ps.md | 65 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 65 insertions(+)
 create mode 100644 Linux/LPIC1/16-ps.md

diff --git a/Linux/LPIC1/16-ps.md b/Linux/LPIC1/16-ps.md
new file mode 100644
index 0000000..36b1d94
--- /dev/null
+++ b/Linux/LPIC1/16-ps.md
@@ -0,0 +1,65 @@
+# ⚙️ PS Command
+
+The `ps` (process status) command is used to **view running processes** on a Linux system. It’s useful for monitoring and troubleshooting tasks.
+
+---
+
+## 🧾 Basic Usage
+
+### 🔍 Show tasks in the current shell
+
+```bash
+ps
+```
+
+### 🔍 Show tasks in the current shell with **full info**
+
+```bash
+ps -f
+```
+
+---
+
+## 🌍 View System-Wide Processes
+
+### 📋 Show **all** processes
+
+```bash
+ps -A
+# or
+ps -e
+```
+
+---
+
+### 👤 Show tasks by **specific user**
+
+```bash
+ps -u <username>
+```
+
+📌 Replace `<username>` with the actual user name.
+
+---
+
+### 📊 Show **detailed info for all** tasks
+
+```bash
+ps aux
+```
+
+---
+
+## 📘 Output Fields Explained
+
+| Column    | Description                                        |
+| --------- | -------------------------------------------------- |
+| `USER`    | Owner of the process (often `root` or your user)   |
+| `PID`     | Process ID                                         |
+| `%CPU`    | CPU usage percentage                               |
+| `%MEM`    | Memory usage percentage                            |
+| `STAT`    | Process state: `R` (running), `S` (sleeping), etc. |
+| `START`   | Time when the process started                      |
+| `TIME`    | Total CPU time used                                |
+| `COMMAND` | Command that started the process                   |
+

From 89029fbee88b40d6f2ddc54a5e6ecfe4a646ade2 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 7 Jul 2025 21:51:41 +0330
Subject: [PATCH 035/116] lipc1 doc: kill command

---
 Linux/LPIC1/17-kill.md | 68 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 68 insertions(+)
 create mode 100644 Linux/LPIC1/17-kill.md

diff --git a/Linux/LPIC1/17-kill.md b/Linux/LPIC1/17-kill.md
new file mode 100644
index 0000000..38f8bac
--- /dev/null
+++ b/Linux/LPIC1/17-kill.md
@@ -0,0 +1,68 @@
+# 🗡️ Kill Command
+
+The `kill` command is used to **send signals to processes**, typically to terminate or control them.
+
+```bash
+kill [options] <PID>
+```
+
+📌 Replace `<PID>` with the Process ID of the target process.
+
+---
+
+## 🚦 Common `kill` Usage Examples
+
+### 💤 Graceful Termination — `SIGTERM` (Signal 15)
+
+```bash
+kill 123
+```
+
+✅ Politely asks the process to terminate.
+*Allows the process to clean up before exiting.*
+
+---
+
+### 🪓 Force Kill — `SIGKILL` (Signal 9)
+
+```bash
+kill -9 123
+```
+
+💥 **Immediate termination**.
+*Doesn’t allow cleanup — use only when necessary.*
+🗡️ *Think of it as the "katana" of kill commands.*
+
+---
+
+### ⌨️ Interrupt — `SIGINT` (Signal 2)
+
+```bash
+kill -2 123
+```
+
+🛑 Mimics pressing `Ctrl + C`.
+*Often used to stop processes gracefully from the terminal.*
+
+---
+
+### 🔄 Hangup — `SIGHUP` (Signal 1)
+
+```bash
+kill -1 123
+```
+
+♻️ Requests the process to **reload or restart**.
+*Commonly used for daemons or services to reload configs.*
+
+---
+
+## 📋 Summary of Signals
+
+| Signal | Name      | Description                    |
+| ------ | --------- | ------------------------------ |
+| `1`    | `SIGHUP`  | Reload configuration / restart |
+| `2`    | `SIGINT`  | Interrupt (like Ctrl + C)      |
+| `9`    | `SIGKILL` | Force kill (cannot be ignored) |
+| `15`   | `SIGTERM` | Graceful termination (default) |
+

From 5cf3e5ad97797167c2833716305b417fe49e4079 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 8 Jul 2025 15:23:31 +0330
Subject: [PATCH 036/116] bash script:shebang doc

---
 Linux/Bash Script/4-Shebang.md | 80 ++++++++++++++++++++++++++++++++++
 1 file changed, 80 insertions(+)
 create mode 100644 Linux/Bash Script/4-Shebang.md

diff --git a/Linux/Bash Script/4-Shebang.md b/Linux/Bash Script/4-Shebang.md
new file mode 100644
index 0000000..2ce1b34
--- /dev/null
+++ b/Linux/Bash Script/4-Shebang.md	
@@ -0,0 +1,80 @@
+
+# 🌟 Understanding the **Shebang** (`#!`)
+
+A **shebang** (also known as a **hashbang**) is the character sequence:
+
+```
+#!<interpreter_path>
+```
+
+It appears **at the very top** of a script file and tells the operating system **which interpreter** should execute the file.
+
+---
+
+## 📌 What It Looks Like
+
+```bash
+#!/usr/bin/python3
+print("Hello, world!")
+```
+
+### Breakdown:
+
+* `#!` — This is the **shebang**.
+* `/usr/bin/python3` — This tells the OS to use **Python 3** to run the script.
+
+---
+
+## 🧠 Why It Matters
+
+When you make a script **executable**:
+
+```bash
+chmod +x script.py
+```
+
+And run it directly:
+
+```bash
+./script.py
+```
+
+The OS reads the **shebang line** and uses the specified interpreter to execute the file. This works for any script type, like:
+
+```bash
+./script.sh   # for a Bash script
+./script.py   # for a Python script
+```
+
+---
+
+## 💡 Common Shebang Examples
+
+| Language | Shebang               |
+| -------- | --------------------- |
+| Bash     | `#!/bin/bash`         |
+| Python   | `#!/usr/bin/python3`  |
+| Node.js  | `#!/usr/bin/env node` |
+| Perl     | `#!/usr/bin/perl`     |
+
+---
+
+## 🚀 Pro Tip: Use `env` for Portability
+
+Instead of hardcoding the interpreter path, use:
+
+```bash
+#!/usr/bin/env python3
+```
+
+This makes your script more **portable**, as it locates `python3` using the user's `PATH` environment.
+
+---
+
+## ✅ Summary
+
+* The **shebang** defines the script interpreter.
+* Place it on **the first line** of your script.
+* Make the script executable with `chmod +x`.
+* Use `/usr/bin/env` for better portability across systems.
+

From 96010b181d8bbdf6886b372f81c9b89c53233223 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 8 Jul 2025 15:30:11 +0330
Subject: [PATCH 037/116] bash script:var doc

---
 Linux/Bash Script/5-Variables.md | 77 ++++++++++++++++++++++++++++++++
 Linux/Bash Script/6-Read.md      |  0
 2 files changed, 77 insertions(+)
 create mode 100644 Linux/Bash Script/5-Variables.md
 create mode 100644 Linux/Bash Script/6-Read.md

diff --git a/Linux/Bash Script/5-Variables.md b/Linux/Bash Script/5-Variables.md
new file mode 100644
index 0000000..9652010
--- /dev/null
+++ b/Linux/Bash Script/5-Variables.md	
@@ -0,0 +1,77 @@
+# 🧮 Bash Variables
+
+In **Bash scripting**, **variables** are used to store values like text or numbers. They allow scripts to be dynamic and reusable.
+
+---
+
+## ✍️ Defining Variables
+
+Variables are created **without spaces** around the `=` sign:
+
+```bash
+user="ali"
+age=21
+```
+
+* `user` is assigned the value `"ali"`.
+* `age` is assigned the value `21`.
+
+> ✅ Tip: No `let` or `var` is needed like in other programming languages.
+
+---
+
+## 📢 Using Variables
+
+You can **access variables** by prefixing them with `$`:
+
+```bash
+user="radin"
+echo "Welcome, $user"
+```
+
+**Output:**
+
+```
+Welcome, radin
+```
+
+---
+
+## 🧪 Full Script Example
+
+Here's a complete Bash script using variables:
+
+```bash
+#!/bin/bash
+
+user="mmd"
+age=25
+
+echo "$user is $age years old."
+```
+
+**Output:**
+
+```
+mmd is 25 years old.
+```
+
+---
+
+## 📌 Notes
+
+* Variable names are **case-sensitive** (`User` and `user` are different).
+* Avoid spaces around `=` when assigning.
+* Enclose variable values in quotes if they contain spaces.
+
+---
+
+## ✅ Summary
+
+| Task            | Syntax                       |
+| --------------- | ---------------------------- |
+| Define variable | `name="value"`               |
+| Use variable    | `$name`                      |
+| Print value     | `echo "$name"`               |
+| With script     | Use `#!/bin/bash` at the top |
+
diff --git a/Linux/Bash Script/6-Read.md b/Linux/Bash Script/6-Read.md
new file mode 100644
index 0000000..e69de29

From 467518687f80afc3c7cee165f732eec047b1a557 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 8 Jul 2025 15:36:46 +0330
Subject: [PATCH 038/116] bash script:read doc

---
 Linux/Bash Script/6-Read.md | 77 +++++++++++++++++++++++++++++++++++++
 1 file changed, 77 insertions(+)

diff --git a/Linux/Bash Script/6-Read.md b/Linux/Bash Script/6-Read.md
index e69de29..46b5973 100644
--- a/Linux/Bash Script/6-Read.md	
+++ b/Linux/Bash Script/6-Read.md	
@@ -0,0 +1,77 @@
+# 📝 Bash `read` Command
+
+The `read` command in **Bash** is used to **take user input** from the terminal. It stores the input into one or more **variables**.
+
+---
+
+## 🔤 Basic Syntax
+
+```bash
+read [options] variable
+```
+
+---
+
+## 📘 Simple Example
+
+```bash
+echo "What is your name?"
+read name
+echo "Hello, $name!"
+```
+
+* `read name` takes input from the user and stores it in the variable `name`.
+* The script then greets the user with the stored input.
+
+---
+
+## 🎯 Prompt Inline with `-p`
+
+```bash
+read -p "What is your name? " name
+echo "Hello, $name!"
+```
+
+* `-p` allows you to show the prompt **on the same line** as the user input.
+
+---
+
+## 🔒 Silent Input with `-s` (e.g., Passwords)
+
+```bash
+read -sp "Enter your password: " password
+echo $password >> pass.txt
+```
+
+* `-s` hides the user’s input while typing (useful for passwords).
+* `>> pass.txt` appends the password to a file (⚠️ For demonstration only—**avoid storing passwords in plain text**!).
+
+---
+
+## ⏳ Set a Timeout with `-t`
+
+```bash
+read -t 5 -p "Enter something in 5 seconds: " data
+```
+
+* `-t 5` gives the user **5 seconds** to input something.
+* If no input is given in time, the script moves on.
+
+---
+
+## 🧠 Summary Table
+
+| Option | Description           | Example                      |
+| ------ | --------------------- | ---------------------------- |
+| `-p`   | Show prompt inline    | `read -p "Name: " name`      |
+| `-s`   | Silent (hidden input) | `read -sp "Password: " pass` |
+| `-t`   | Timeout (in seconds)  | `read -t 10 var`             |
+
+---
+
+## ✅ Quick Recap
+
+* Use `read` to get **interactive input** in your Bash scripts.
+* Combine options (`-sp`, `-tp`, etc.) for powerful input control.
+* Avoid exposing sensitive data—use secure handling practices.
+

From 6d0e75ad856ea8b43e1b207895e14553167383cc Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 9 Jul 2025 12:32:27 +0330
Subject: [PATCH 039/116] kuber doc: pv and pvc

---
 .../Kubernetes/workloads/11-Pv.md             | 141 +++++++++++++-----
 1 file changed, 103 insertions(+), 38 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md b/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md
index c749197..35a594b 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md	
@@ -1,12 +1,13 @@
-Here's a clean, organized, and visually appealing document version of your input on **Persistent Volumes (PV) in Kubernetes**:
-
----
-
-# 🌐 Kubernetes: Persistent Volumes (PV) Cheat Sheet
+# 🌐 Kubernetes Persistent Volumes (PV) Cheat Sheet
 
 ## 📦 What is a Persistent Volume (PV)?
 
-A **Persistent Volume** is a piece of storage in a Kubernetes cluster that has been provisioned by an administrator or dynamically provisioned using **StorageClasses**.
+A **Persistent Volume (PV)** is a piece of storage in a Kubernetes cluster that is either:
+
+* Pre-provisioned by an administrator, or
+* Dynamically provisioned using **StorageClasses**.
+
+It allows data to **persist beyond the lifecycle of individual Pods**.
 
 ---
 
@@ -15,56 +16,64 @@ A **Persistent Volume** is a piece of storage in a Kubernetes cluster that has b
 1. **HostPath**
 
    * Mounts a file or directory from the host node’s filesystem into your Pod.
+   * Useful only for single-node testing or development.
 
 2. **Using PV and PVC**
 
-   * **PV (Persistent Volume):** The actual storage resource.
-   * **PVC (Persistent Volume Claim):** A request for storage by a user.
+   * **PV (Persistent Volume):** Represents the actual storage resource.
+   * **PVC (Persistent Volume Claim):** A user's request for storage resources and access.
 
 ---
 
 ## 🧱 Kubernetes Storage Layers
 
-1. **Persistent Volume (PV)**
-2. **Persistent Volume Claim (PVC)**
+1. **Persistent Volume (PV)** – The actual storage unit.
+2. **Persistent Volume Claim (PVC)** – A request for that storage.
 
 ---
 
 ## 🔄 PV Lifecycle States
 
-| State        | Description                                          |
-| ------------ | ---------------------------------------------------- |
-| Provisioning | Kubernetes is preparing the PV.                      |
-| Binding      | The PV is bound to a PVC.                            |
-| Using        | The bound PV is being used by a Pod.                 |
-| Releasing    | PVC is deleted; PV is no longer bound.               |
-| Reclaiming   | PV is reclaimed using one of the following policies: |
-|              |     • `Delete` – Remove the storage                  |
-|              |     • `Recycle` – Basic scrub (deprecated)           |
-|              |     • `Retain` – Manual reclaim                      |
+| State        | Description                                |
+| ------------ | ------------------------------------------ |
+| Provisioning | PV is being prepared.                      |
+| Binding      | PV is bound to a PVC.                      |
+| Using        | PV is in use by a Pod.                     |
+| Releasing    | PVC is deleted; PV becomes unbound.        |
+| Reclaiming   | Reclaim policy is applied:                 |
+|              | • `Delete` – Remove the storage.           |
+|              | • `Recycle` – Basic scrub (deprecated).    |
+|              | • `Retain` – Manual intervention required. |
 
 ---
 
 ## 🔒 PV Access Modes
 
-| Mode   | Description                                 |
-| ------ | ------------------------------------------- |
-| `RWO`  | **ReadWriteOnce** – One node can read/write |
-| `ROX`  | **ReadOnlyMany** – Many nodes read-only     |
-| `RWX`  | **ReadWriteMany** – Many nodes read/write   |
-| `RWOP` | **ReadWriteOncePod** – One Pod only         |
+| Mode   | Description                                    |
+| ------ | ---------------------------------------------- |
+| `RWO`  | **ReadWriteOnce** – One node can read/write    |
+| `ROX`  | **ReadOnlyMany** – Multiple nodes read-only    |
+| `RWX`  | **ReadWriteMany** – Multiple nodes read/write  |
+| `RWOP` | **ReadWriteOncePod** – Only one Pod can use it |
 
 ---
 
-## 🛠️ Check PVs via CLI
+## 🛠️ CLI Commands to Manage PVs
 
 ```bash
+# List all Persistent Volumes
 kubectl get pv
+
+# List all Persistent Volume Claims
+kubectl get pvc
+
+# Edit a PVC
+kubectl edit pvc -n <namespace> <pvc-name>
 ```
 
 ---
 
-## 🚀 Example: Deployment using HostPath Volume
+## 🚀 Example 1: Deployment with `hostPath` Volume
 
 ```yaml
 apiVersion: apps/v1
@@ -73,18 +82,16 @@ metadata:
   name: app-1
   namespace: dev
   labels:
-    label1: test1
-    app.kubernetes.io/label2: test2
+    app.kubernetes.io/name: nginx
 spec:
   replicas: 3
   selector:
     matchLabels:
-      app.kubernetes.io/label2: test2
+      app.kubernetes.io/name: nginx
   template:
     metadata:
       labels:
-        app.kubernetes.io/label2: test2
-        os: linux
+        app.kubernetes.io/name: nginx
     spec:
       containers:
         - name: nginx
@@ -93,16 +100,19 @@ spec:
             - containerPort: 80
           volumeMounts:
             - name: nginx-log
-              mountPath: /var/log/nginx  
+              mountPath: /var/log/nginx
       volumes:
         - name: nginx-log
           hostPath:
             path: /root/nginx/logs
+            type: DirectoryOrCreate
 ```
 
 ---
 
-## 📂 Example: PersistentVolume with NFS
+## 📂 Example 2: NFS-backed Persistent Volume
+
+### 🧩 PersistentVolume Definition
 
 ```yaml
 apiVersion: v1
@@ -110,12 +120,12 @@ kind: PersistentVolume
 metadata:
   name: pv1
 spec:
-  capacity: 
+  capacity:
     storage: 5Gi
   volumeMode: Filesystem
-  accessModes: 
+  accessModes:
     - ReadWriteMany
-  persistentVolumeReclaimPolicy: Recycle
+  persistentVolumeReclaimPolicy: Retain
   storageClassName: custom-name
   mountOptions:
     - hard
@@ -125,3 +135,58 @@ spec:
     server: 192.168.1.10
 ```
 
+### 📄 PersistentVolumeClaim
+
+```yaml
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: pvc1
+  namespace: ns-test
+spec:
+  accessModes:
+    - ReadWriteMany
+  resources:
+    requests:
+      storage: 1Gi
+  storageClassName: custom-name
+```
+
+### 🚀 Deployment Using PVC
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-1
+  namespace: dev
+  labels:
+    app.kubernetes.io/name: nginx
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app.kubernetes.io/name: nginx
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/name: nginx
+    spec:
+      containers:
+        - name: nginx
+          image: nginx
+          ports:
+            - containerPort: 80
+          volumeMounts:
+            - name: nginx-log
+              mountPath: /var/log/nginx
+      volumes:
+        - name: nginx-log
+          persistentVolumeClaim:
+            claimName: pvc1
+```
+
+---
+
+## 📝 Common Mistakes Fixed
+

From fe2232fdcb763eaad7546d6a6aeb5851a9670d87 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 9 Jul 2025 12:37:15 +0330
Subject: [PATCH 040/116] kuber doc: configmap

---
 .../Kubernetes/Commands/3-Commands.md         |   4 +
 .../Kubernetes/Commands/config-map.md         | 104 ++++++++++++++++++
 2 files changed, 108 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/Commands/config-map.md

diff --git a/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md b/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md
index 02f0118..efab6b8 100755
--- a/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md	
+++ b/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md	
@@ -115,3 +115,7 @@ This guide provides a concise reference for common `kubectl` commands used to ma
   Any YAML files placed in `/etc/kubernetes/manifests/` are automatically loaded when the kubelet starts (for example, after a server reboot).
 
 
+
+```bash
+kubectl cp -n <ns> <pod-name>:dir/ ./
+```
diff --git a/Containerization & Orchestration/Kubernetes/Commands/config-map.md b/Containerization & Orchestration/Kubernetes/Commands/config-map.md
new file mode 100644
index 0000000..778a5c7
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/Commands/config-map.md	
@@ -0,0 +1,104 @@
+# 🧾 Kubernetes ConfigMap
+
+## 📘 What is a ConfigMap?
+
+A **ConfigMap** allows you to **store configuration data** in key-value pairs that can be:
+
+* Mounted as files in a Pod
+* Exposed as environment variables
+* Consumed by Kubernetes workloads without hardcoding settings in container images
+
+---
+
+## ⚙️ Creating a ConfigMap from Files
+
+Create a ConfigMap from one or more files:
+
+```bash
+kubectl -n <namespace> create configmap <configmap-name> --from-file=<file-or-directory>
+```
+
+### ✅ Examples
+
+```bash
+# Create from a single file
+kubectl -n <ns> create configmap nginx-conf --from-file=./nginx.conf
+
+# Create from multiple files
+kubectl -n <ns> create configmap nginx-conf --from-file=./nginx.conf --from-file=./site.conf
+```
+
+---
+
+## 📂 Viewing and Editing ConfigMaps
+
+```bash
+# List ConfigMaps in a namespace
+kubectl get cm -n <namespace>
+
+# Edit a ConfigMap
+kubectl -n <namespace> edit configmap <configmap-name>
+```
+
+---
+
+## 📄 ConfigMap YAML Example
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: game-demo
+data:
+  # Key-value style
+  player_initial_lives: "3"
+  ui_properties_file_name: "user-interface.properties"
+
+  # Multi-line file-style entries
+  game.properties: |
+    enemy.types=aliens,monsters
+    player.maximum-lives=5    
+  user-interface.properties: |
+    color.good=purple
+    color.bad=yellow
+    allow.textmode=true    
+```
+
+---
+
+## 🚀 Deployment Example: Using ConfigMap as Volume
+
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: app-1
+  namespace: dev
+  labels:
+    app.kubernetes.io/name: nginx
+spec:
+  replicas: 3
+  selector:
+    matchLabels:
+      app.kubernetes.io/name: nginx
+  template:
+    metadata:
+      labels:
+        app.kubernetes.io/name: nginx
+        os: linux
+    spec:
+      containers:
+        - name: nginx
+          image: nginx
+          ports:
+            - containerPort: 80
+          volumeMounts:
+            - name: configfile
+              mountPath: /etc/nginx/nginx.conf
+              subPath: nginx.conf  # Mount specific file from ConfigMap
+      volumes:
+        - name: configfile
+          configMap:
+            name: nginx-conf
+```
+

From 8a41d6f124e5feaf334c6ceb1a5c62380c65aadd Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Thu, 10 Jul 2025 12:12:16 +0330
Subject: [PATCH 041/116] Update 2-Operators.md

---
 Linux/Bash Script/2-Operators.md | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/Linux/Bash Script/2-Operators.md b/Linux/Bash Script/2-Operators.md
index d97fa74..0391dea 100644
--- a/Linux/Bash Script/2-Operators.md	
+++ b/Linux/Bash Script/2-Operators.md	
@@ -1,5 +1,4 @@
-
-# 🖥️ Bash Opreators
+# 🖥️ Bash Operators
 
 A quick reference guide to essential bash command operators and their usage.
 
@@ -53,6 +52,18 @@ echo "Hi" > file1 ; cat file1
 
 ---
 
+## `|` — **Pipe Operator**
+
+Takes the **output of the command on the left** and **uses it as input for the command on the right**.
+
+```bash
+ls -l | grep "txt"
+```
+
+🔗 Passes the output of `ls -l` to `grep "txt"` to filter and display only files containing "txt".
+
+---
+
 ## `*` — **Wildcard (All Matching Files)**
 
 Matches **all files** that meet the pattern.
@@ -78,4 +89,3 @@ cat file[1,2,3]
 ```bash
 cat file1 file2 file3
 ```
-

From 5ff17bdb403c77533666233fbd5a3be619874bf4 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 10 Jul 2025 17:14:41 +0330
Subject: [PATCH 042/116] update kuber: longhorn,resource quota

---
 .../Kubernetes/Longhorn/with-kubectl.md       | 58 +++++++++++++++++++
 .../12-Config-map.md}                         |  0
 .../Kubernetes/workloads/13-Resource-quota.md | 21 +++++++
 3 files changed, 79 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/Longhorn/with-kubectl.md
 rename Containerization & Orchestration/Kubernetes/{Commands/config-map.md => workloads/12-Config-map.md} (100%)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/13-Resource-quota.md

diff --git a/Containerization & Orchestration/Kubernetes/Longhorn/with-kubectl.md b/Containerization & Orchestration/Kubernetes/Longhorn/with-kubectl.md
new file mode 100644
index 0000000..16b176d
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/Longhorn/with-kubectl.md	
@@ -0,0 +1,58 @@
+# 📦 Deploying Longhorn with `kubectl`
+
+This guide walks you through installing **Longhorn**, a cloud-native distributed block storage solution for Kubernetes, using `kubectl`.
+
+---
+
+## 🚀 Prerequisites
+
+* A Kubernetes cluster (v1.21 or newer recommended)
+* `kubectl` configured and connected to your cluster
+* Internet access for downloading manifests
+
+---
+
+## 🧩 Step 1: Apply Longhorn YAML
+
+Apply the official Longhorn deployment manifest in the `longhorn-system` namespace:
+
+```bash
+kubectl apply -f https://raw.githubusercontent.com/longhorn/longhorn/v1.9.0/deploy/longhorn.yaml
+```
+
+This will create all required resources under the `longhorn-system` namespace.
+
+---
+
+## 🔍 Step 2: Monitor Longhorn Pods
+
+Watch the pods being created to ensure Longhorn is deploying properly:
+
+```bash
+kubectl get pods \
+--namespace longhorn-system \
+--watch
+```
+
+Wait until all pods show a `Running` or `Completed` status.
+
+---
+
+## 📦 Step 3: Verify Storage Classes
+
+Once Longhorn is running, verify that the storage classes have been registered:
+
+```bash
+kubectl get storageclasses
+```
+
+You should see a storage class named `longhorn`, which can now be used in your PersistentVolumeClaims (PVCs).
+
+---
+
+## ✅ Success!
+
+Longhorn is now successfully deployed and ready to provide persistent block storage for your workloads.
+
+For more information, visit the [official Longhorn documentation](https://longhorn.io/docs/).
+
diff --git a/Containerization & Orchestration/Kubernetes/Commands/config-map.md b/Containerization & Orchestration/Kubernetes/workloads/12-Config-map.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Commands/config-map.md
rename to Containerization & Orchestration/Kubernetes/workloads/12-Config-map.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/13-Resource-quota.md b/Containerization & Orchestration/Kubernetes/workloads/13-Resource-quota.md
new file mode 100644
index 0000000..3e78518
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/13-Resource-quota.md	
@@ -0,0 +1,21 @@
+resource Quota:
+
+```bash
+kubectl get resourcequota -n <ns>
+```
+
+
+```yaml
+apiVersion: v1
+kind: ResourceQuota
+metadata:
+    name: my-ns-quota
+    namcespace: dev
+spec:
+    hard:
+        pod: 10
+        requests.cpu: "1"
+        requests.memory: "1024Mb"
+        service: "5"
+        configmap: "2"
+```
\ No newline at end of file

From 9ac143f3f697cd4ed0d3a36b5fbf4a82798269fa Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 10 Jul 2025 17:23:45 +0330
Subject: [PATCH 043/116] update kuber: longhorn statfullset

---
 .../workloads/manifests/state-full-set.yaml   | 49 +++++++++++++++++++
 1 file changed, 49 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml

diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml
new file mode 100644
index 0000000..07ad5b0
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml	
@@ -0,0 +1,49 @@
+---
+apiVersion: v1
+kind: Service
+metadata:
+  labels:
+    app: nginx
+  name: nginx
+spec:
+  clusterIP: None
+  ports:
+    - name: web
+      port: 80
+  selector:
+    app: nginx
+---
+apiVersion: apps/v1
+kind: StatefulSet
+metadata:
+  name: simple-stateful-set
+spec:
+  replicas: 3  # the default is 1
+  selector:
+    matchLabels:
+      app: nginx  # has to match .spec.template.metadata.labels
+  serviceName: "nginx"
+  template:
+    metadata:
+      labels:
+        app: nginx  # has to match .spec.selector.matchLabels
+    spec:
+      terminationGracePeriodSeconds: 10
+      containers:
+        - image: nginx
+          name: nginx
+          ports:
+            - containerPort: 80
+              name: web
+          volumeMounts:
+            - mountPath: /usr/share/nginx/html
+              name: www
+  volumeClaimTemplates:
+    - metadata:
+        name: www
+      spec:
+        accessModes: ["ReadWriteOnce"]
+        resources:
+          requests:
+            storage: 1Gi
+        storageClassName: "longhorn"
\ No newline at end of file

From 254634d81798c5fe052658f64132f6fcffb4ce8b Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 15 Jul 2025 23:04:32 +0330
Subject: [PATCH 044/116] linux doc: usermanage

---
 Linux/LPIC1/18-usermanage.md | 111 +++++++++++++++++++++++++++++++++++
 1 file changed, 111 insertions(+)
 create mode 100644 Linux/LPIC1/18-usermanage.md

diff --git a/Linux/LPIC1/18-usermanage.md b/Linux/LPIC1/18-usermanage.md
new file mode 100644
index 0000000..5987969
--- /dev/null
+++ b/Linux/LPIC1/18-usermanage.md
@@ -0,0 +1,111 @@
+# 🧑‍💻 Linux User & Group Management Cheat Sheet
+
+---
+
+## 🔍 Viewing User Info from `/etc/shadow`
+
+```bash
+cat /etc/shadow
+```
+
+Example entry:
+
+```bash
+radin:$y$j9T$gxn.Bgl/nVnzPEeWn0Hrz.$CEeQGtg1TlZ/jwu9Zsz2kkIq3dBtbhJ/bzhVT7cJ1.9:20270:0:99999:7:::
+```
+
+| Field             | Description                                  | Example                                         |
+| ----------------- | -------------------------------------------- | ----------------------------------------------- |
+| 👤 Username       | User’s login name                            | `radin`                                         |
+| 🔒 Password Hash  | Encrypted password                           | `$y$j9T$gxn.Bgl/nVnzPEeWn0Hrz.$CEeQGtg1TlZ/...` |
+| 🗓️ Last Changed  | Days since Jan 1, 1970 when password changed | `20270` (which is 20270 + 1970 = year)          |
+| ⏳ Min Age         | Minimum days between password changes        | `0`                                             |
+| ⏰ Max Age         | Maximum days before password must be changed | `99999`                                         |
+| ⚠️ Warning Period | Days before expiration user is warned        | `7`                                             |
+
+---
+
+## 🛡️ Viewing Groups from `/etc/group`
+
+```bash
+cat /etc/group
+```
+
+Example:
+
+```bash
+radin:x:1000:
+sudo:x:27:radin
+```
+
+| Field         | Description                          | Example         |
+| ------------- | ------------------------------------ | --------------- |
+| 👥 Group Name | Name of the group                    | `radin`, `sudo` |
+| 🔑 Password   | Password (usually `x` means none)    | `x`             |
+| 🆔 GID        | Group ID                             | `1000`, `27`    |
+| 👤 Users      | Users in the group (comma-separated) | `radin`         |
+
+---
+
+## 👥 Check Groups for a User
+
+```bash
+groups <username>
+```
+
+---
+
+## 🆔 View User and Group IDs
+
+```bash
+id <username>
+```
+
+Example output:
+
+```bash
+uid=1000(radin) gid=1000(radin) groups=1000(radin),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),114(lpadmin)
+```
+
+---
+
+## ➕ Adding Users
+
+| Command                                | Description                               |
+| -------------------------------------- | ----------------------------------------- |
+| `useradd <username>`                   | Add user without home directory           |
+| `useradd -m <username>`                | Add user **with** home directory          |
+| `useradd -s /bin/bash -m <username>`   | Add user with bash shell & home directory |
+| `useradd -G group1,root -m <username>` | Add user with home and extra groups       |
+
+---
+
+## 🔑 Changing Password
+
+```bash
+passwd <username>
+```
+
+---
+
+## ❌ Deleting Users
+
+| Command                 | Description                          |
+| ----------------------- | ------------------------------------ |
+| `userdel <username>`    | Delete user                          |
+| `userdel -r <username>` | Delete user and their home directory |
+| `userdel -f <username>` | Force delete user                    |
+
+---
+
+## 🔧 Modifying Users (`usermod`)
+
+| Command                                  | Description                               |
+| ---------------------------------------- | ----------------------------------------- |
+| `usermod [options] username`             | Modify user with various options          |
+| `usermod -l <newusername> <oldusername>` | Rename user                               |
+| `usermod -d <dir> -m <username>`         | Change user home directory and move files |
+| `usermod -G <groups> <username>`         | Set new groups (replaces old groups)      |
+| `usermod -aG <group> <username>`         | Add user to a supplementary group         |
+| `usermod -s <shell> <username>`          | Change user login shell                   |
+

From 3b6241d5f678823a70487ac61ee7a93cdba69b0b Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 15 Jul 2025 23:08:36 +0330
Subject: [PATCH 045/116] linux doc: perm doc

---
 Linux/LPIC1/19-chmod-chown.md | 150 ++++++++++++++++++++++++++++++++++
 1 file changed, 150 insertions(+)
 create mode 100644 Linux/LPIC1/19-chmod-chown.md

diff --git a/Linux/LPIC1/19-chmod-chown.md b/Linux/LPIC1/19-chmod-chown.md
new file mode 100644
index 0000000..c5c794f
--- /dev/null
+++ b/Linux/LPIC1/19-chmod-chown.md
@@ -0,0 +1,150 @@
+# 📁 Linux File Permissions: A Quick & Clear Guide
+
+---
+
+## 🔍 Example: Output of `ls -lh`
+
+Run this command in your terminal:
+
+```bash
+ls -lh
+```
+
+Example output:
+
+```bash
+drwxr-xr-x 3 root root 4.0K Jul  1 22:22 dir1
+-rw-r--r-- 1 root root 2.0G Jul  1 21:59 test2.tar
+```
+
+---
+
+## 🧠 Understanding the Output Columns
+
+| Column               | Description                             |
+| -------------------- | --------------------------------------- |
+| `d` / `-`            | File type (`d` = directory, `-` = file) |
+| `rwxr-xr-x`          | Permissions (user, group, others)       |
+| `3`                  | Number of hard links                    |
+| `root`               | Owner (user)                            |
+| `root`               | Group                                   |
+| `4.0K` / `2.0G`      | File size                               |
+| `Jul 1 22:22`        | Last modification date                  |
+| `dir1` / `test2.tar` | File or directory name                  |
+
+---
+
+## 🔤 First Character: File Type Indicator
+
+* `d` → Directory 📂
+* `-` → Regular file 📄
+
+---
+
+## 🔠 File Permissions Breakdown
+
+```
+drwxr-xr-x
+│││ │ │ │
+│││ │ │ └─ Permissions for Others (o)
+│││ │ └── Permissions for Group (g)
+│││ └──── Permissions for User (u)
+│└──────── File type (d = directory, - = file)
+└───────── Read (r), Write (w), Execute (x)
+```
+
+---
+
+## 🔐 Permission Symbols Explained
+
+| Symbol | Meaning |
+| ------ | ------- |
+| `r`    | Read    |
+| `w`    | Write   |
+| `x`    | Execute |
+
+---
+
+## 👥 Permission Entities
+
+| Symbol | Meaning      |
+| ------ | ------------ |
+| `u`    | User (owner) |
+| `g`    | Group        |
+| `o`    | Others       |
+| `a`    | All          |
+
+---
+
+## 🔢 Numeric Permission Values (Octal)
+
+| Value | Binary | Permissions | Meaning                |
+| ----- | ------ | ----------- | ---------------------- |
+| 0     | 000    | ---         | No permissions         |
+| 1     | 001    | --x         | Execute only           |
+| 2     | 010    | -w-         | Write only             |
+| 3     | 011    | -wx         | Write + Execute        |
+| 4     | 100    | r--         | Read only              |
+| 5     | 101    | r-x         | Read + Execute         |
+| 6     | 110    | rw-         | Read + Write           |
+| 7     | 111    | rwx         | Read + Write + Execute |
+
+---
+
+## 🛠️ Changing Permissions with `chmod`
+
+### Syntax:
+
+```bash
+chmod [permissions] [filename]
+```
+
+### Example (numeric):
+
+```bash
+chmod 755 myscript.sh
+```
+
+### What does `755` mean?
+
+| Entity | Value | Permission                 |
+| ------ | ----- | -------------------------- |
+| User   | 7     | rwx (read, write, execute) |
+| Group  | 5     | r-x (read, execute)        |
+| Others | 5     | r-x (read, execute)        |
+
+### Recursive permission change:
+
+```bash
+chmod -R <permission> <directory>
+```
+
+---
+
+## 👑 Changing Ownership with `chown`
+
+### Syntax:
+
+```bash
+chown [options] owner[:group] file
+```
+
+### Examples:
+
+Change owner only:
+
+```bash
+sudo chown radin file.txt
+```
+
+Change owner and group:
+
+```bash
+sudo chown radin:dev file.txt
+```
+
+Change owner and group recursively (for directories):
+
+```bash
+sudo chown -R radin:dev files/
+```

From 279c08aab69a939a6800aff08c5a6728d23b3f7f Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Thu, 17 Jul 2025 17:51:23 +0330
Subject: [PATCH 046/116] Create etcd-external.md

---
 .../Kubernetes/etcd-external.md               | 172 ++++++++++++++++++
 1 file changed, 172 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/etcd-external.md

diff --git a/Containerization & Orchestration/Kubernetes/etcd-external.md b/Containerization & Orchestration/Kubernetes/etcd-external.md
new file mode 100644
index 0000000..d9bad71
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/etcd-external.md	
@@ -0,0 +1,172 @@
+# 🛠️ Setting Up a High Availability etcd Cluster for Kubernetes
+
+This guide walks you through installing a 3-node etcd cluster and using it as an **external HA datastore for Kubernetes**.
+
+---
+
+## 📦 Step 1: Install etcd
+
+Download the etcd binary:
+
+```bash
+wget https://github.com/etcd-io/etcd/releases/download/v3.6.2/etcd-v3.6.2-linux-amd64.tar.gz
+```
+
+Extract it:
+
+```bash
+tar -xzvf etcd-v3.6.2-linux-amd64.tar.gz
+```
+
+Move binaries to the system path:
+
+```bash
+cp etcd-v3.6.2-linux-amd64/etcd* /usr/local/bin
+```
+
+Create the data directory:
+
+```bash
+mkdir -p /var/lib/etcd
+```
+
+---
+
+## ⚙️ Step 2: Configure etcd Systemd Services
+
+Create a systemd service config at:
+
+```bash
+/etc/systemd/system/etcd.conf
+```
+
+### 🔹 Server 1 (`192.168.6.170`)
+
+```ini
+[Service]
+ExecStart=/usr/local/bin/etcd \
+  --name etcd-1 \
+  --listen-client-urls http://192.168.6.170:2379,http://127.0.0.1:2379 \
+  --advertise-client-urls http://192.168.6.170:2379 \
+  --initial-advertise-peer-urls http://192.168.6.170:2380 \
+  --listen-peer-urls http://192.168.6.170:2380 \
+  --initial-cluster-token etcd-cluster-1 \
+  --initial-cluster etcd-1=http://192.168.6.170:2380,etcd-2=http://192.168.6.171:2380,etcd-3=http://192.168.6.172:2380 \
+  --initial-cluster-state new \
+  --data-dir /var/lib/etcd
+Restart=always
+User=root
+StandardOutput=journal
+StandardError=journal
+
+[Install]
+WantedBy=multi-user.target
+```
+
+### 🔹 Server 2 (`192.168.6.171`)
+
+```ini
+[Service]
+ExecStart=/usr/local/bin/etcd \
+  --name etcd-2 \
+  --listen-client-urls http://192.168.6.171:2379,http://127.0.0.1:2379 \
+  --advertise-client-urls http://192.168.6.171:2379 \
+  --initial-advertise-peer-urls http://192.168.6.171:2380 \
+  --listen-peer-urls http://192.168.6.171:2380 \
+  --initial-cluster-token etcd-cluster-1 \
+  --initial-cluster etcd-1=http://192.168.6.170:2380,etcd-2=http://192.168.6.171:2380,etcd-3=http://192.168.6.172:2380 \
+  --initial-cluster-state new \
+  --data-dir /var/lib/etcd
+Restart=always
+User=root
+StandardOutput=journal
+StandardError=journal
+
+[Install]
+WantedBy=multi-user.target
+```
+
+### 🔹 Server 3 (`192.168.6.172`)
+
+```ini
+[Service]
+ExecStart=/usr/local/bin/etcd \
+  --name etcd-3 \
+  --listen-client-urls http://192.168.6.172:2379,http://127.0.0.1:2379 \
+  --advertise-client-urls http://192.168.6.172:2379 \
+  --initial-advertise-peer-urls http://192.168.6.172:2380 \
+  --listen-peer-urls http://192.168.6.172:2380 \
+  --initial-cluster-token etcd-cluster-1 \
+  --initial-cluster etcd-1=http://192.168.6.170:2380,etcd-2=http://192.168.6.171:2380,etcd-3=http://192.168.6.172:2380 \
+  --initial-cluster-state new \
+  --data-dir /var/lib/etcd
+Restart=always
+User=root
+StandardOutput=journal
+StandardError=journal
+
+[Install]
+WantedBy=multi-user.target
+```
+
+---
+
+## ▶️ Step 3: Start etcd Service
+
+Enable and start the etcd service on **each server**:
+
+```bash
+systemctl start etcd
+systemctl enable etcd
+```
+
+---
+
+## ✅ Step 4: Verify etcd Cluster Health
+
+Check endpoint health:
+
+```bash
+etcdctl --endpoints http://<IP>:2379 endpoint health
+```
+
+Check cluster membership:
+
+```bash
+etcdctl --endpoints http://<IP-SERVER-1>:2379 member list
+```
+
+If all members are healthy and visible, you're ready to move on.
+
+---
+
+## ☸️ Step 5: Install Kubernetes (Using External etcd)
+
+Create a configuration file `config.yaml` on the **master node**:
+
+```yaml
+apiVersion: kubeadm.k8s.io/v1beta3
+kind: ClusterConfiguration
+etcd:
+  external:
+    endpoints:
+    - http://192.168.6.170:2379
+    - http://192.168.6.171:2379
+    - http://192.168.6.172:2379
+
+networking:
+  podSubnet: 10.244.0.0/16
+```
+
+Initialize Kubernetes:
+
+```bash
+kubeadm init --config config.yaml
+```
+
+---
+
+## 🎉 Done!
+
+You now have a **Kubernetes cluster with external, high availability etcd**. :)
+

From cbbda9db6f6b830ef654e77004eceab54e7bf598 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Fri, 18 Jul 2025 15:32:23 +0330
Subject: [PATCH 047/116] state full set

---
 .../Kubernetes/workloads/manifests/state-full-set.yaml          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml b/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml
index 07ad5b0..a60575a 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml	
+++ b/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml	
@@ -46,4 +46,4 @@ spec:
         resources:
           requests:
             storage: 1Gi
-        storageClassName: "longhorn"
\ No newline at end of file
+        storageClassName: "longhorn "
\ No newline at end of file

From e41aa509c6a3f9c965c1dfecd2170da4749b24f9 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 21 Jul 2025 17:52:10 +0330
Subject: [PATCH 048/116] update scripts

---
 .../Kubernetes/workloads/09-Services.md       | 25 +++++++++++++++++++
 .../Kubernetes/workloads/11-Pv.md             | 13 ++++++++++
 2 files changed, 38 insertions(+)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md
index aa5f782..a4a3812 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md	
@@ -48,6 +48,13 @@ kubectl get ep -n <namespace>
 kubectl get svc -n <namespace>
 ```
 
+
+```bash
+kubectl expose deployment web-server-dep -n dev --port 80 
+```
+
+
+
 ---
 
 ## 🔁 **Port Forwarding**
@@ -99,3 +106,21 @@ spec:
 > 🔍 **Note:** The `selector` must match the labels of the target Pods.
 > 🧠 **Tip:** Use `kubectl describe svc <service-name>` to inspect the service and verify connectivity.
 
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: nginx
+  namespace: ns
+  labels:
+    app: web-server
+spec:
+  type: LoadBalancer
+  selector:
+    app: nginx
+  ports:
+    - name: http
+      port: 80
+      targetPort: 8080
+```
diff --git a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md b/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md
index 35a594b..aa7fa5b 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md	
@@ -108,6 +108,19 @@ spec:
             type: DirectoryOrCreate
 ```
 
+```yaml
+spec:
+  containers:
+    volumeMounts:
+      - name: nginx-log
+        mountPath: /var/log/nginx
+
+volumes:
+  - name: nginx-log
+    emptyDir:
+      sizeLimit: 500Mi
+```
+
 ---
 
 ## 📂 Example 2: NFS-backed Persistent Volume

From 26d00e355d5e2370af4eb21993d42da99b961717 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 23 Jul 2025 14:52:27 +0330
Subject: [PATCH 049/116] update kuber doc: stroage

---
 .../{ => Storage}/Longhorn/with-kubectl.md    |  0
 .../{workloads/11-Pv.md => Storage/Pv.md}     | 12 ----
 .../Kubernetes/Storage/emptydir_vol.md        | 64 +++++++++++++++++++
 .../{12-Config-map.md => 11-Config-map.md}    |  0
 ...Resource-quota.md => 12-Resource-quota.md} |  0
 5 files changed, 64 insertions(+), 12 deletions(-)
 rename Containerization & Orchestration/Kubernetes/{ => Storage}/Longhorn/with-kubectl.md (100%)
 rename Containerization & Orchestration/Kubernetes/{workloads/11-Pv.md => Storage/Pv.md} (96%)
 create mode 100644 Containerization & Orchestration/Kubernetes/Storage/emptydir_vol.md
 rename Containerization & Orchestration/Kubernetes/workloads/{12-Config-map.md => 11-Config-map.md} (100%)
 rename Containerization & Orchestration/Kubernetes/workloads/{13-Resource-quota.md => 12-Resource-quota.md} (100%)

diff --git a/Containerization & Orchestration/Kubernetes/Longhorn/with-kubectl.md b/Containerization & Orchestration/Kubernetes/Storage/Longhorn/with-kubectl.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Longhorn/with-kubectl.md
rename to Containerization & Orchestration/Kubernetes/Storage/Longhorn/with-kubectl.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md b/Containerization & Orchestration/Kubernetes/Storage/Pv.md
similarity index 96%
rename from Containerization & Orchestration/Kubernetes/workloads/11-Pv.md
rename to Containerization & Orchestration/Kubernetes/Storage/Pv.md
index aa7fa5b..17100ae 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/11-Pv.md	
+++ b/Containerization & Orchestration/Kubernetes/Storage/Pv.md	
@@ -108,18 +108,6 @@ spec:
             type: DirectoryOrCreate
 ```
 
-```yaml
-spec:
-  containers:
-    volumeMounts:
-      - name: nginx-log
-        mountPath: /var/log/nginx
-
-volumes:
-  - name: nginx-log
-    emptyDir:
-      sizeLimit: 500Mi
-```
 
 ---
 
diff --git a/Containerization & Orchestration/Kubernetes/Storage/emptydir_vol.md b/Containerization & Orchestration/Kubernetes/Storage/emptydir_vol.md
new file mode 100644
index 0000000..3be7dd5
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/Storage/emptydir_vol.md	
@@ -0,0 +1,64 @@
+
+## 📦 Pod Volume Lifecycle & `emptyDir` Usage in Kubernetes
+
+This document describes how volumes work in the context of Kubernetes Pods, focusing on `emptyDir` and its lifecycle behavior.
+
+---
+
+### 🔁 Pod Lifecycle & Volumes
+
+* **Volumes are defined at the Pod level.**
+  They are not tied to a specific container, but can be shared among containers within the same Pod.
+
+* **Volumes are attached to containers through `volumeMounts`.**
+  This enables containers to access the volume’s filesystem at the specified `mountPath`.
+
+* **Data in `emptyDir` volumes is ephemeral.**
+  The volume is created when the Pod starts and **deleted when the Pod is removed**, erasing all stored data.
+
+---
+
+### ⚠️ Visibility Across Pods & Containers
+
+* A **Pod cannot access another Pod’s volume**, even if it's of type `emptyDir`.
+  For example:
+
+  * Pod A cannot see Pod B’s `emptyDir`.
+* However, **containers within the same Pod can share and access the same `emptyDir`** volume.
+
+---
+
+### 🧪 Example: Pod with `emptyDir` Volume in Memory
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  namespace: ns-test
+  name: pod-tests
+spec:
+  containers:
+    - name: nginx
+      image: nginx
+      resources:
+        limits:
+          memory: "150Mi"
+          cpu: "500m"
+      volumeMounts:
+        - name: nginx-log
+          mountPath: /var/log/nginx
+  volumes:
+    - name: nginx-log
+      emptyDir:
+        medium: Memory  # Uses memory for faster read/write operations
+        sizeLimit: 64Mi # Volume size limited to 64Mi
+```
+
+---
+
+### 🧠 Key Points
+
+* `emptyDir` is ideal for temporary storage like logs, scratch space, or caches.
+* Using `medium: Memory` stores data in memory (RAM) instead of disk, offering higher performance.
+* `sizeLimit` restricts the amount of memory that the `emptyDir` can consume.
+
diff --git a/Containerization & Orchestration/Kubernetes/workloads/12-Config-map.md b/Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/12-Config-map.md
rename to Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/13-Resource-quota.md b/Containerization & Orchestration/Kubernetes/workloads/12-Resource-quota.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/13-Resource-quota.md
rename to Containerization & Orchestration/Kubernetes/workloads/12-Resource-quota.md

From a44069bda75bea02847cabad0e15af9baf026891 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 24 Jul 2025 01:24:13 +0330
Subject: [PATCH 050/116] update lpic: if statment doc

---
 Linux/Bash Script/7-If.md | 175 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 175 insertions(+)
 create mode 100644 Linux/Bash Script/7-If.md

diff --git a/Linux/Bash Script/7-If.md b/Linux/Bash Script/7-If.md
new file mode 100644
index 0000000..ab5e4e8
--- /dev/null
+++ b/Linux/Bash Script/7-If.md	
@@ -0,0 +1,175 @@
+
+# 🐚 Bash `if` Statement Guide
+
+Conditional statements in Bash allow you to execute code based on specific conditions. Below is a comprehensive guide to `if` statements, their syntax, comparison operators, and examples.
+
+---
+
+## 🔹 Basic Syntax
+
+```bash
+if [[ condition ]]; then
+    # commands if condition is true
+fi
+```
+
+### With `else`
+
+```bash
+if [[ condition ]]; then
+    # true
+else
+    # false
+fi
+```
+
+### With `elif`
+
+```bash
+if [[ condition1 ]]; then
+    # condition1 is true
+elif [[ condition2 ]]; then
+    # condition2 is true
+else
+    # none matched
+fi
+```
+
+---
+
+## ⚙️ Operators
+
+### 🔢 Numeric Comparison
+
+| Operator | Meaning          |
+| -------- | ---------------- |
+| `-eq`    | Equal to         |
+| `-ne`    | Not equal        |
+| `-lt`    | Less than        |
+| `-le`    | Less or equal    |
+| `-gt`    | Greater than     |
+| `-ge`    | Greater or equal |
+
+### 🔤 String Comparison
+
+| Operator | Meaning          |
+| -------- | ---------------- |
+| `==`     | Equal to         |
+| `!=`     | Not equal        |
+| `-z`     | Empty string     |
+| `-n`     | Not empty string |
+
+### 📁 File Tests
+
+| Operator | Meaning            |
+| -------- | ------------------ |
+| `-e`     | File exists        |
+| `-d`     | Directory exists   |
+| `-r`     | File is readable   |
+| `-w`     | File is writable   |
+| `-x`     | File is executable |
+
+---
+
+## 🧪 Practical Examples
+
+### Example 1: Number Check
+
+```bash
+read -p "Enter Your Number: " number
+
+if [[ $number -eq 0 ]]; then
+    echo "Zero"
+elif [[ $number -ge 1 ]]; then
+    echo "Positive"
+else
+    echo "Negative"
+fi
+```
+
+---
+
+### Example 2: Number Range with Error Handling
+
+```bash
+read -p "Enter Your Number: " number
+
+if [[ $number -eq 0 ]]; then
+    echo "Zero"
+elif [[ $number -ge 1 ]]; then
+    echo "Positive"
+elif [[ $number -le -1 ]]; then
+    echo "Negative"
+else 
+    echo "Error: Invalid input"
+    exit 1
+fi
+```
+
+---
+
+### Example 3: String Check
+
+```bash
+read -p "Enter Your String: " str
+
+if [[ -n $str ]]; then
+    if [[ $str == "hello" ]]; then
+        echo "Hi"
+    elif [[ $str != "hello" ]]; then
+        echo "Ok"
+    fi
+else
+    echo "Nothing to read"
+    exit 1
+fi
+```
+
+---
+
+### Example 4: File Existence
+
+```bash
+file="script.sh"
+
+if [[ -e $file ]]; then
+    echo "File exists"
+else
+    touch "$file"
+    echo "File created"
+fi
+```
+
+---
+
+### Example 5: File Permission Check
+
+```bash
+file="script50.sh"
+
+if [[ -e $file ]]; then
+    echo "File exists"
+
+    if [[ ! -x $file ]]; then
+        chmod +x "$file"
+        echo "Executable permission added"
+    fi
+
+    if [[ ! -r $file ]]; then
+        chmod +r "$file"
+        echo "Read permission added"
+    fi
+else
+    touch "$file"
+    echo "File created"
+fi
+```
+
+---
+
+## ✅ Tips
+
+* Always quote variables: `"$var"` to prevent word splitting.
+* Use `[[ ... ]]` for conditional tests (preferred over `[ ... ]`).
+* Prefer `read -r` to avoid backslash escapes.
+

From d8c1e958721454d8a4534495af97f8d9a1c6974e Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 24 Jul 2025 12:07:47 +0330
Subject: [PATCH 051/116] functions

---
 Linux/Bash Script/8-Function.md | 90 +++++++++++++++++++++++++++++++++
 Linux/Bash Script/9-For.md      |  0
 2 files changed, 90 insertions(+)
 create mode 100644 Linux/Bash Script/8-Function.md
 create mode 100644 Linux/Bash Script/9-For.md

diff --git a/Linux/Bash Script/8-Function.md b/Linux/Bash Script/8-Function.md
new file mode 100644
index 0000000..50aec97
--- /dev/null
+++ b/Linux/Bash Script/8-Function.md	
@@ -0,0 +1,90 @@
+# 🐚 Bash Function Syntax & Examples
+
+Bash functions allow you to group reusable logic in shell scripts. Below are clear examples and explanations to help you understand how to define and use them effectively.
+
+---
+
+## 🔧 Defining a Function
+
+You can define a Bash function in two main ways:
+
+### Option 1: Classic Syntax
+
+```bash
+function_name () {
+    # commands
+}
+```
+
+### Option 2: With the `function` Keyword
+
+```bash
+function function_name () {
+    # commands
+}
+```
+
+> 💡 Both syntaxes are valid. The use of the `function` keyword is optional and mostly stylistic.
+
+---
+
+## 📥 Passing Arguments
+
+Bash functions accept arguments just like scripts. These are accessed via `$1`, `$2`, etc.
+
+### Example: Single Argument
+
+```bash
+func1() {
+    echo "Arg: $1"
+}
+
+func1 "Test"
+```
+
+**Output:**
+
+```
+Arg: Test
+```
+
+---
+
+## ➕ Multiple Arguments & Calculation
+
+You can perform operations using passed arguments, like arithmetic:
+
+```bash
+summery() {
+    local sum=$(( $1 + $2 ))
+    echo $sum
+}
+
+summery 5 7
+```
+
+**Output:**
+
+```
+12
+```
+
+> 📌 `local` ensures `sum` is scoped within the function.
+
+---
+
+## ✅ Best Practices
+
+* Use `local` to avoid polluting the global scope.
+* Quote variables when dealing with strings.
+* Use descriptive names for clarity.
+
+---
+
+## 🧪 Try It Yourself
+
+Add these examples to a `.sh` file and run it with:
+
+```bash
+bash script.sh
+```
diff --git a/Linux/Bash Script/9-For.md b/Linux/Bash Script/9-For.md
new file mode 100644
index 0000000..e69de29

From 1bfb49d0f3e75a1b4797f144e69bdeea54ee59fa Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Fri, 25 Jul 2025 20:59:41 +0330
Subject: [PATCH 052/116] update kuber doc: update pv

---
 .../Kubernetes/Storage/Pv.md                  | 195 ++++++++++--------
 1 file changed, 106 insertions(+), 89 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/Storage/Pv.md b/Containerization & Orchestration/Kubernetes/Storage/Pv.md
index 17100ae..9a8138a 100644
--- a/Containerization & Orchestration/Kubernetes/Storage/Pv.md	
+++ b/Containerization & Orchestration/Kubernetes/Storage/Pv.md	
@@ -2,63 +2,61 @@
 
 ## 📦 What is a Persistent Volume (PV)?
 
-A **Persistent Volume (PV)** is a piece of storage in a Kubernetes cluster that is either:
+A **Persistent Volume (PV)** is a piece of storage in a Kubernetes cluster that can be:
 
-* Pre-provisioned by an administrator, or
-* Dynamically provisioned using **StorageClasses**.
+- **Pre-provisioned** by an administrator, or  
+- **Dynamically provisioned** using a **StorageClass**.
 
-It allows data to **persist beyond the lifecycle of individual Pods**.
+> PVs allow data to **persist beyond the lifecycle of individual Pods**.
 
 ---
 
 ## 📁 PV Storage Options
 
-1. **HostPath**
+### 1. **HostPath**
+- Mounts a file or directory from the host node’s filesystem into a Pod.
+- Only suitable for **single-node testing or development** environments.
 
-   * Mounts a file or directory from the host node’s filesystem into your Pod.
-   * Useful only for single-node testing or development.
-
-2. **Using PV and PVC**
-
-   * **PV (Persistent Volume):** Represents the actual storage resource.
-   * **PVC (Persistent Volume Claim):** A user's request for storage resources and access.
+### 2. **Persistent Volume (PV) & Persistent Volume Claim (PVC)**
+- **PV**: Represents the actual physical or virtual storage resource.
+- **PVC**: A user's request for specific storage resources and access modes.
 
 ---
 
-## 🧱 Kubernetes Storage Layers
+## 🧱 Kubernetes Storage Architecture
 
-1. **Persistent Volume (PV)** – The actual storage unit.
-2. **Persistent Volume Claim (PVC)** – A request for that storage.
+1. **Persistent Volume (PV)** – The actual storage unit, managed by the admin or provisioned dynamically.  
+2. **Persistent Volume Claim (PVC)** – A user’s request for a certain amount and type of storage.
 
 ---
 
-## 🔄 PV Lifecycle States
+## 🔄 PV Lifecycle Phases
 
-| State        | Description                                |
-| ------------ | ------------------------------------------ |
-| Provisioning | PV is being prepared.                      |
-| Binding      | PV is bound to a PVC.                      |
-| Using        | PV is in use by a Pod.                     |
-| Releasing    | PVC is deleted; PV becomes unbound.        |
-| Reclaiming   | Reclaim policy is applied:                 |
-|              | • `Delete` – Remove the storage.           |
-|              | • `Recycle` – Basic scrub (deprecated).    |
-|              | • `Retain` – Manual intervention required. |
+| **State**     | **Description**                             |
+|---------------|---------------------------------------------|
+| Provisioning  | PV is being created or initialized.         |
+| Binding       | PV is bound to a PVC.                       |
+| Using         | PV is in use by a Pod.                      |
+| Releasing     | PVC is deleted; PV becomes unbound.         |
+| Reclaiming    | Based on reclaim policy:                    |
+|               | - `Delete`: Remove the storage.             |
+|               | - `Recycle`: Basic scrub (deprecated).      |
+|               | - `Retain`: Manual cleanup required.        |
 
 ---
 
 ## 🔒 PV Access Modes
 
-| Mode   | Description                                    |
-| ------ | ---------------------------------------------- |
-| `RWO`  | **ReadWriteOnce** – One node can read/write    |
-| `ROX`  | **ReadOnlyMany** – Multiple nodes read-only    |
-| `RWX`  | **ReadWriteMany** – Multiple nodes read/write  |
-| `RWOP` | **ReadWriteOncePod** – Only one Pod can use it |
+| **Mode**   | **Description**                                 |
+|------------|-------------------------------------------------|
+| `RWO`      | **ReadWriteOnce** – One node can read/write.    |
+| `ROX`      | **ReadOnlyMany** – Multiple nodes can read.     |
+| `RWX`      | **ReadWriteMany** – Multiple nodes can read/write. |
+| `RWOP`     | **ReadWriteOncePod** – Only one Pod can mount it with read/write access. |
 
 ---
 
-## 🛠️ CLI Commands to Manage PVs
+## 🛠️ CLI Commands to Manage PVs & PVCs
 
 ```bash
 # List all Persistent Volumes
@@ -73,7 +71,7 @@ kubectl edit pvc -n <namespace> <pvc-name>
 
 ---
 
-## 🚀 Example 1: Deployment with `hostPath` Volume
+## 🚀 Example: Deployment with `hostPath` Volume
 
 ```yaml
 apiVersion: apps/v1
@@ -81,17 +79,15 @@ kind: Deployment
 metadata:
   name: app-1
   namespace: dev
-  labels:
-    app.kubernetes.io/name: nginx
 spec:
   replicas: 3
   selector:
     matchLabels:
-      app.kubernetes.io/name: nginx
+      name: nginx
   template:
     metadata:
       labels:
-        app.kubernetes.io/name: nginx
+        name: nginx
     spec:
       containers:
         - name: nginx
@@ -108,86 +104,107 @@ spec:
             type: DirectoryOrCreate
 ```
 
+### Valid `hostPath` Types:
+- `DirectoryOrCreate`
+- `Directory`
+- `FileOrCreate`
+- `File`
+- `Socket`
+- `CharDevice`
+- `BlockDevice`
 
 ---
 
-## 📂 Example 2: NFS-backed Persistent Volume
-
-### 🧩 PersistentVolume Definition
+## 📄 Example: Static Persistent Volume (PV)
 
 ```yaml
 apiVersion: v1
 kind: PersistentVolume
 metadata:
-  name: pv1
+  name: pv001
 spec:
   capacity:
-    storage: 5Gi
-  volumeMode: Filesystem
+    storage: 128Mi
   accessModes:
     - ReadWriteMany
   persistentVolumeReclaimPolicy: Retain
-  storageClassName: custom-name
-  mountOptions:
-    - hard
-    - nfsvers=4.1
-  nfs:
-    path: /nfs/data
-    server: 192.168.1.10
 ```
 
-### 📄 PersistentVolumeClaim
+---
+
+## 📄 Example: Persistent Volume Claim (PVC)
 
 ```yaml
 apiVersion: v1
 kind: PersistentVolumeClaim
 metadata:
-  name: pvc1
-  namespace: ns-test
+  name: pvc-2
+  namespace: db
 spec:
   accessModes:
-    - ReadWriteMany
+    - ReadWriteOnce
   resources:
     requests:
-      storage: 1Gi
-  storageClassName: custom-name
+      storage: 64Mi
 ```
 
-### 🚀 Deployment Using PVC
-
+> ✅ To bind a PVC to a specific PV, add `volumeName: <pv-name>` in the PVC spec:
 ```yaml
-apiVersion: apps/v1
-kind: Deployment
-metadata:
-  name: app-1
-  namespace: dev
-  labels:
-    app.kubernetes.io/name: nginx
-spec:
-  replicas: 3
-  selector:
-    matchLabels:
-      app.kubernetes.io/name: nginx
-  template:
-    metadata:
-      labels:
-        app.kubernetes.io/name: nginx
-    spec:
-      containers:
-        - name: nginx
-          image: nginx
-          ports:
-            - containerPort: 80
-          volumeMounts:
-            - name: nginx-log
-              mountPath: /var/log/nginx
-      volumes:
-        - name: nginx-log
-          persistentVolumeClaim:
-            claimName: pvc1
+volumeName: pv001
 ```
 
 ---
 
-## 📝 Common Mistakes Fixed
+## 🌐 NFS-Based Persistent Volume
 
+### Persistent Volume (PV)
+
+```yaml
+apiVersion: v1
+kind: PersistentVolume
+metadata:
+  name: pv-nfs-2
+spec:
+  capacity:
+    storage: 128Mi
+  accessModes:
+    - ReadWriteMany
+  persistentVolumeReclaimPolicy: Retain
+  storageClassName: nginx-files
+  mountOptions:
+    - hard
+    - nfsvers=4.2
+  nfs:
+    path: /root/Nginx_Files
+    server: 192.168.6.160
+```
+
+### Persistent Volume Claim (PVC)
+
+```yaml
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+  name: pvc-1
+  namespace: db
+spec:
+  volumeName: pv-nfs-2
+  accessModes:
+    - ReadWriteMany
+  resources:
+    requests:
+      storage: 64Mi
+  storageClassName: nginx-files
+```
+
+---
+
+## 🏗️ Static StorageClass for Pre-Provisioned Volumes
+
+```yaml
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  name: nginx-files
+provisioner: kubernetes.io/no-provisioner
+```

From e5a924156d3b70c7b2372a1cff583e3e75a5b295 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 27 Jul 2025 22:28:16 +0330
Subject: [PATCH 053/116] Nginxx doc: file server

---
 .../Nginx/6-File-Server.md                    | 54 +++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 Web Servers & Reverse Proxies/Nginx/6-File-Server.md

diff --git a/Web Servers & Reverse Proxies/Nginx/6-File-Server.md b/Web Servers & Reverse Proxies/Nginx/6-File-Server.md
new file mode 100644
index 0000000..687fb08
--- /dev/null
+++ b/Web Servers & Reverse Proxies/Nginx/6-File-Server.md	
@@ -0,0 +1,54 @@
+### 📄 **NGINX File Server Configuration**
+
+This configuration sets up an NGINX server to serve files from two different directories:
+
+* `/srv/files` for general file browsing at the root path (`/`)
+* `/srv/images` for image browsing at `/image`
+
+```nginx
+server {
+    # Define the domain name for this server block
+    server_name domain;
+
+    # Default root directory for the server
+    root /srv/files;
+
+    # Serve files and list directory contents at the root URL (e.g., http://domain/)
+    location / {
+        autoindex on;  # Enables directory listing
+    }
+
+    # Serve images and list contents at /image (e.g., http://domain/image/)
+    location /image {
+        autoindex on;            # Enables directory listing
+        root /srv/images;        # Note: this overrides the global root
+                                 # Final path served will be /srv/images/image/ due to how root works
+    }
+}
+```
+
+---
+
+### ⚠️ **Important Notes**
+
+1. **Path Behavior**:
+
+   * In the `/image` block, using `root` adds the location path (`/image`) to the end. So `http://domain/image/` will map to `/srv/images/image/`.
+   * If you want `/image/` to map directly to `/srv/images/`, use `alias` instead:
+
+     ```nginx
+     location /image/ {
+         autoindex on;
+         alias /srv/images/;
+     }
+     ```
+
+2. **Security**:
+
+   * Be cautious when enabling `autoindex`; it exposes directory contents to the public.
+   * Consider restricting access or adding authentication for sensitive directories.
+
+3. **Permissions**:
+
+   * Ensure the NGINX user (usually `www-data`) has read access to the directories.
+

From dd029a4dca04eae95757bbc3f861dc29259b5408 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 27 Jul 2025 22:43:14 +0330
Subject: [PATCH 054/116] linux doc: ip command

---
 Linux/LPIC1/20-ip.md | 148 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 148 insertions(+)
 create mode 100644 Linux/LPIC1/20-ip.md

diff --git a/Linux/LPIC1/20-ip.md b/Linux/LPIC1/20-ip.md
new file mode 100644
index 0000000..954de61
--- /dev/null
+++ b/Linux/LPIC1/20-ip.md
@@ -0,0 +1,148 @@
+
+# 🌐 IP Command Cheat Sheet
+
+The `ip` command is a powerful tool for network configuration and management in Linux. It replaces many of the older `ifconfig` functionalities.
+
+---
+
+## 📌 General Syntax
+
+```bash
+ip [ OPTIONS ] OBJECT { COMMAND | help }
+```
+
+**Common OBJECTS:**
+
+* `addr` – IP addresses
+* `link` – Network interfaces
+* `route` – Routing tables
+* `neigh` – ARP table
+* `rule`, `netns`, etc.
+
+---
+
+## 🔍 View Network Information
+
+### Show All IP Addresses
+
+```bash
+ip addr show
+# or shorthand:
+ip a
+```
+
+### Show IP for Specific Interface
+
+```bash
+ip addr show dev eth0
+```
+
+### Show Link Layer Information
+
+```bash
+ip link show
+```
+
+---
+
+## 🔧 Interface Management
+
+### Bring Interface Down
+
+```bash
+ip link set eth0 down
+```
+
+### Bring Interface Up
+
+```bash
+ip link set eth0 up
+```
+
+---
+
+## 🌐 IP Address Configuration
+
+### Add an IP Address
+
+```bash
+ip addr add 192.168.1.10/24 dev eth0
+```
+
+### Delete an IP Address
+
+```bash
+ip addr del 192.168.1.10/24 dev eth0
+```
+
+---
+
+## 🛣️ Routing
+
+### Show Routing Table
+
+```bash
+ip route show
+```
+
+### Add a Default Gateway
+
+```bash
+ip route add default via 192.168.1.1
+```
+
+### Add a Specific Route
+
+```bash
+ip route add 192.168.10.0/24 via 192.168.5.2
+```
+
+### Delete a Specific Route
+
+```bash
+ip route del 192.168.10.0/24 via 192.168.5.2
+```
+
+---
+
+## 🧱 Bridge Interface Management
+
+### Create a Bridge
+
+```bash
+ip link add name br0 type bridge
+```
+
+### Delete a Bridge
+
+```bash
+ip link delete br0
+```
+
+### Bring Bridge Up
+
+```bash
+ip link set br0 up
+```
+
+---
+
+## 🛠️ Example: Set a Static IP Address
+
+```bash
+ip link set ens33 up
+ip addr add 10.10.40.12/24 dev ens33
+ip route add default via 10.10.40.1
+```
+
+---
+
+### ✅ Tip:
+
+Always verify with:
+
+```bash
+ip a
+ip r
+```
+

From e2f00da11f352bc8e7201e6d45b5d3567692ae5e Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 28 Jul 2025 20:26:44 +0330
Subject: [PATCH 055/116] mariadb replicat doc

---
 Databases/Mariadb/Replication.md | 153 +++++++++++++++++++++++++++++++
 1 file changed, 153 insertions(+)
 create mode 100644 Databases/Mariadb/Replication.md

diff --git a/Databases/Mariadb/Replication.md b/Databases/Mariadb/Replication.md
new file mode 100644
index 0000000..aeeac74
--- /dev/null
+++ b/Databases/Mariadb/Replication.md
@@ -0,0 +1,153 @@
+
+# 📘 MariaDB Replication Setup Guide
+
+This guide walks you through setting up **Master-Slave Replication** using MariaDB.
+
+---
+
+## 🛠️ Step 1: Install MariaDB
+
+Install MariaDB on both the **master** and **slave** servers.
+
+```bash
+sudo apt update
+sudo apt install mariadb-server
+```
+
+---
+
+## ⚙️ Step 2: Configure the Master Server
+
+Edit the MariaDB configuration file:
+
+```bash
+sudo vim /etc/mysql/mariadb.conf.d/50-server.cnf
+```
+
+Add or modify the following under the `[mariadb]` section:
+
+```cnf
+[mariadb]
+log-bin
+server_id=1
+log-basename=master1
+binlog-format=mixed
+```
+
+🔁 **Also**, change the `bind-address` to allow external connections:
+
+```cnf
+bind-address = 0.0.0.0
+```
+
+---
+
+## 🔐 Step 3: Create Replication User
+
+Access the MariaDB shell:
+
+```bash
+sudo mysql
+```
+
+Then run:
+
+```sql
+CREATE USER 'radin'@'%' IDENTIFIED BY '123';
+GRANT REPLICATION SLAVE ON *.* TO 'radin'@'%';
+FLUSH PRIVILEGES;
+```
+
+---
+
+## 📈 Step 4: Check Master Status
+
+Still inside the MariaDB shell, run:
+
+```sql
+FLUSH TABLES WITH READ LOCK;
+SHOW MASTER STATUS;
+```
+
+Take note of:
+
+* `File`: The binary log file name (e.g., `db-master1-bin.000003`)
+* `Position`: The log position (e.g., `347`)
+
+Then, in a separate terminal, unlock tables:
+
+```sql
+UNLOCK TABLES;
+```
+
+---
+
+## 🛠️ Step 5: Configure the Slave Server
+
+Edit the config file on the slave:
+
+```bash
+sudo vim /etc/mysql/mariadb.conf.d/50-server.cnf
+```
+
+Set the following:
+
+```cnf
+[mariadb]
+log-bin
+server_id=2
+log-basename=slave1
+binlog-format=mixed
+```
+
+---
+
+## 🔄 Step 6: Set Up Slave Replication
+
+Access the MariaDB shell on the slave server:
+
+```bash
+sudo mysql
+```
+
+Run the following (replace values as needed):
+
+```sql
+CHANGE MASTER TO
+  MASTER_HOST='192.168.6.160',
+  MASTER_USER='radin',
+  MASTER_PASSWORD='123',
+  MASTER_PORT=3306,
+  MASTER_LOG_FILE='db-master1-bin.000003',
+  MASTER_LOG_POS=347,
+  MASTER_CONNECT_RETRY=10;
+```
+
+Start the slave:
+
+```sql
+START SLAVE;
+```
+
+Check slave status:
+
+```sql
+SHOW SLAVE STATUS\G
+```
+
+Look for:
+
+* `Slave_IO_Running: Yes`
+* `Slave_SQL_Running: Yes`
+
+---
+
+## 🔁 Resetting the Slave
+
+To reset the slave configuration:
+
+```sql
+STOP SLAVE;
+RESET SLAVE ALL;
+```
+

From c92308fd54ed3ba59b63dd794f31cddd911e656a Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 28 Jul 2025 21:24:14 +0330
Subject: [PATCH 056/116] update config map doc

---
 .../Kubernetes/workloads/11-Config-map.md     | 184 +++++++++++++-----
 1 file changed, 134 insertions(+), 50 deletions(-)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md b/Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md
index 778a5c7..6dce7d1 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md	
@@ -1,18 +1,22 @@
-# 🧾 Kubernetes ConfigMap
+# 🧾 Kubernetes ConfigMap Guide
 
-## 📘 What is a ConfigMap?
-
-A **ConfigMap** allows you to **store configuration data** in key-value pairs that can be:
-
-* Mounted as files in a Pod
-* Exposed as environment variables
-* Consumed by Kubernetes workloads without hardcoding settings in container images
+Manage configuration without hardcoding! `ConfigMaps` let you store external configurations as key-value pairs and inject them into Kubernetes workloads.
 
 ---
 
-## ⚙️ Creating a ConfigMap from Files
+## 📘 What is a ConfigMap?
 
-Create a ConfigMap from one or more files:
+A **ConfigMap** is a Kubernetes object used to store **non-confidential configuration data** in **key-value** format. You can:
+
+* 📄 Mount it as files inside a Pod
+* 🌿 Use it as environment variables
+* 🧩 Keep your container images decoupled from configuration
+
+---
+
+## ⚙️ Creating a ConfigMap
+
+You can create a ConfigMap from files or directories:
 
 ```bash
 kubectl -n <namespace> create configmap <configmap-name> --from-file=<file-or-directory>
@@ -21,28 +25,33 @@ kubectl -n <namespace> create configmap <configmap-name> --from-file=<file-or-di
 ### ✅ Examples
 
 ```bash
-# Create from a single file
+# From a single file
 kubectl -n <ns> create configmap nginx-conf --from-file=./nginx.conf
 
-# Create from multiple files
-kubectl -n <ns> create configmap nginx-conf --from-file=./nginx.conf --from-file=./site.conf
+# From multiple files
+kubectl -n <ns> create configmap nginx-conf \
+  --from-file=./nginx.conf \
+  --from-file=./site.conf
 ```
 
 ---
 
-## 📂 Viewing and Editing ConfigMaps
+## 📂 Viewing & Editing ConfigMaps
 
 ```bash
-# List ConfigMaps in a namespace
+# List all ConfigMaps in a namespace
 kubectl get cm -n <namespace>
 
-# Edit a ConfigMap
+# View detailed ConfigMap info
+kubectl describe configmap <name> -n <namespace>
+
+# Edit in-place
 kubectl -n <namespace> edit configmap <configmap-name>
 ```
 
 ---
 
-## 📄 ConfigMap YAML Example
+## 📄 YAML: ConfigMap Example
 
 ```yaml
 apiVersion: v1
@@ -50,14 +59,13 @@ kind: ConfigMap
 metadata:
   name: game-demo
 data:
-  # Key-value style
   player_initial_lives: "3"
   ui_properties_file_name: "user-interface.properties"
 
-  # Multi-line file-style entries
   game.properties: |
     enemy.types=aliens,monsters
     player.maximum-lives=5    
+
   user-interface.properties: |
     color.good=purple
     color.bad=yellow
@@ -66,39 +74,115 @@ data:
 
 ---
 
-## 🚀 Deployment Example: Using ConfigMap as Volume
+## 💡 Usage Examples
+
+### 📌 ConfigMap as Environment Variables
+
+**ConfigMap:**
 
 ```yaml
-apiVersion: apps/v1
-kind: Deployment
+apiVersion: v1
+kind: ConfigMap
 metadata:
-  name: app-1
-  namespace: dev
-  labels:
-    app.kubernetes.io/name: nginx
-spec:
-  replicas: 3
-  selector:
-    matchLabels:
-      app.kubernetes.io/name: nginx
-  template:
-    metadata:
-      labels:
-        app.kubernetes.io/name: nginx
-        os: linux
-    spec:
-      containers:
-        - name: nginx
-          image: nginx
-          ports:
-            - containerPort: 80
-          volumeMounts:
-            - name: configfile
-              mountPath: /etc/nginx/nginx.conf
-              subPath: nginx.conf  # Mount specific file from ConfigMap
-      volumes:
-        - name: configfile
-          configMap:
-            name: nginx-conf
+  name: app-config
+  namespace: default
+data:
+  APP_MODE: "production"
+  LOG_LEVEL: "info"
+  FEATURE_FLAG_X: "enabled"
 ```
 
+**Pod:**
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: my-app
+spec:
+  containers:
+    - name: my-container
+      image: busybox
+      command: ["/bin/sh", "-c", "env && sleep 3600"]
+      envFrom:
+        - configMapRef:
+            name: app-config
+```
+
+---
+
+### 🧾 Mounting ConfigMap as a File (nginx.conf example)
+
+**ConfigMap:**
+
+```yaml
+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: nginx-config
+  namespace: default
+data:
+  nginx.conf: |
+    worker_processes  1;
+
+    events {
+        worker_connections  1024;
+    }
+
+    http {
+        include       mime.types;
+        default_type  application/octet-stream;
+
+        sendfile        on;
+        keepalive_timeout  65;
+
+        server {
+            listen       80;
+            server_name  localhost;
+
+            location / {
+                root   /usr/share/nginx/html;
+                index  index.html index.htm;
+            }
+
+            error_page   500 502 503 504  /50x.html;
+            location = /50x.html {
+                root   /usr/share/nginx/html;
+            }
+        }
+    }
+```
+
+**Pod:**
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: nginx-pod
+spec:
+  containers:
+    - name: nginx
+      image: nginx:latest
+      volumeMounts:
+        - name: nginx-config-volume
+          mountPath: /etc/nginx/nginx.conf
+          subPath: nginx.conf
+  volumes:
+    - name: nginx-config-volume
+      configMap:
+        name: nginx-config
+```
+
+---
+
+## 🛠 Pro Tips
+
+* 🔐 For **sensitive data**, use **Secrets** instead of ConfigMaps.
+* 🧪 Combine ConfigMaps with **Deployment** objects for flexible, versioned config management.
+* 📦 Use `--from-env-file` to load multiple key-value pairs from a `.env` style file:
+
+  ```bash
+  kubectl create configmap my-config --from-env-file=env.list
+  ```
+

From 9e81dfc1ac368b126202ffcf48c82867f4cbd680 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 29 Jul 2025 19:40:45 +0330
Subject: [PATCH 057/116] route command

---
 Linux/LPIC1/21-route.md   | 74 +++++++++++++++++++++++++++++++++++++++
 Linux/LPIC1/22-netstat.md |  0
 2 files changed, 74 insertions(+)
 create mode 100644 Linux/LPIC1/21-route.md
 create mode 100644 Linux/LPIC1/22-netstat.md

diff --git a/Linux/LPIC1/21-route.md b/Linux/LPIC1/21-route.md
new file mode 100644
index 0000000..d205867
--- /dev/null
+++ b/Linux/LPIC1/21-route.md
@@ -0,0 +1,74 @@
+# 🛣️ `route` Command Documentation
+
+The `route` command is used to view and manipulate the IP routing table in Linux systems. Below is a concise guide to listing, adding, and deleting routes using `route`.
+
+---
+
+## 📋 View Routing Table
+
+```bash
+route -n
+```
+
+* **Description**: Displays the kernel routing table.
+* **`-n`**: Shows numerical addresses instead of resolving hostnames (faster and cleaner).
+
+---
+
+## ➕ Add Routes
+
+### Add a Network Route
+
+```bash
+route add -net 10.10.10.0 netmask 255.255.255.0 gw 192.168.1.1
+```
+
+* **`-net 10.10.10.0`**: Specifies the network address.
+* **`netmask 255.255.255.0`**: Defines the subnet mask for the network.
+* **`gw 192.168.1.1`**: Sets the gateway through which packets will be routed.
+
+### Add a Default Gateway
+
+```bash
+route add default gw 192.168.1.1
+```
+
+* **default**: Indicates this is the default route.
+* **`gw 192.168.1.1`**: The default gateway IP address for all traffic not destined for a known network.
+
+---
+
+## ❌ Delete Routes
+
+### Delete a Network Route
+
+```bash
+route del -net 10.10.10.0 netmask 255.255.255.0
+```
+
+* Removes the specified network route.
+
+### Delete the Default Route
+
+```bash
+route del default
+```
+
+* Removes the current default gateway.
+
+---
+
+## 📎 Notes
+
+* These commands typically require **superuser (root)** privileges. Use `sudo` if needed:
+
+  ```bash
+  sudo route add ...
+  ```
+
+* Consider using `ip route` instead of `route`, as `route` is deprecated on some modern distributions:
+
+  ```bash
+  ip route show
+  ```
+
diff --git a/Linux/LPIC1/22-netstat.md b/Linux/LPIC1/22-netstat.md
new file mode 100644
index 0000000..e69de29

From 1fb19e6e456579f3c768ee208e5c0da077a20da7 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 29 Jul 2025 19:47:19 +0330
Subject: [PATCH 058/116] netstat & ss command

---
 Linux/LPIC1/22-netstat.md | 102 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 102 insertions(+)

diff --git a/Linux/LPIC1/22-netstat.md b/Linux/LPIC1/22-netstat.md
index e69de29..42e325d 100644
--- a/Linux/LPIC1/22-netstat.md
+++ b/Linux/LPIC1/22-netstat.md
@@ -0,0 +1,102 @@
+# 🌐 `netstat` and `ss` Command Documentation
+
+This guide provides essential usage examples for the `netstat` and `ss` commands to monitor network connections, listening ports, and socket statistics in Linux.
+
+---
+
+## 📡 `netstat` – Network Statistics
+
+`netstat` is a legacy tool used for displaying network connections, routing tables, interface statistics, masquerade connections, and multicast memberships.
+
+> ⚠️ `netstat` may be deprecated on some systems. Consider using `ss` as a modern replacement.
+
+### 🔍 Show All Active Network Connections
+
+```bash
+netstat
+```
+
+* Displays all active sockets (both listening and non-listening).
+* Includes TCP, UDP, UNIX domain sockets, etc.
+
+---
+
+### 🎧 Show Listening Ports
+
+```bash
+netstat -l
+```
+
+* Lists all **listening** ports (TCP and UDP).
+* Useful for checking which services are waiting for incoming connections.
+
+---
+
+### 🔒 Show Listening TCP Ports
+
+```bash
+netstat -lt
+```
+
+* Lists only **TCP** ports in the **listening** state.
+
+---
+
+### 📡 Show Listening UDP Ports
+
+```bash
+netstat -lu
+```
+
+* Lists only **UDP** ports in the **listening** state.
+
+---
+
+### 🧠 Show Listening TCP/UDP Ports with Process Info
+
+```bash
+netstat -tulpn
+```
+
+* Shows all listening **TCP/UDP** ports.
+* Includes **process ID (PID)** and **program name**.
+* Useful for identifying which service is using a specific port.
+
+---
+
+## ⚡ `ss` – Socket Statistics (Modern Alternative)
+
+`ss` is a faster and more powerful alternative to `netstat` for displaying socket statistics.
+
+### Common `ss` Options
+
+| Option | Description                                  |
+| ------ | -------------------------------------------- |
+| `-t`   | Show TCP sockets                             |
+| `-u`   | Show UDP sockets                             |
+| `-l`   | Show only listening sockets                  |
+| `-n`   | Show numerical addresses (no DNS resolution) |
+| `-p`   | Show process using the socket                |
+| `-a`   | Show all sockets                             |
+
+### Example – Show Listening TCP/UDP with Process Info
+
+```bash
+ss -tulpn
+```
+
+* Equivalent to `netstat -tulpn`
+* Recommended for modern Linux distributions.
+
+---
+
+## ✅ Summary
+
+| Task                                | `netstat` Command | `ss` Equivalent |
+| ----------------------------------- | ----------------- | --------------- |
+| Show all connections                | `netstat`         | `ss -a`         |
+| Show listening ports                | `netstat -l`      | `ss -l`         |
+| Show listening TCP ports            | `netstat -lt`     | `ss -lt`        |
+| Show listening UDP ports            | `netstat -lu`     | `ss -lu`        |
+| Show listening TCP/UDP with process | `netstat -tulpn`  | `ss -tulpn`     |
+

From 47b8e7d2009b8452b8f670540e6a5766903328b5 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Fri, 1 Aug 2025 21:04:22 +0330
Subject: [PATCH 059/116] kuber doc: added secret

---
 .../Kubernetes/workloads/13-Secret.md         | 78 +++++++++++++++++++
 1 file changed, 78 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/13-Secret.md

diff --git a/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md b/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md
new file mode 100644
index 0000000..7046c01
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md	
@@ -0,0 +1,78 @@
+# 🔐 Kubernetes Secrets Guide
+
+Kubernetes **Secrets** are used to store and manage sensitive information such as passwords, OAuth tokens, and SSH keys. Unlike ConfigMaps, they are specifically designed for confidential data.
+
+---
+
+## 📌 Types of Kubernetes Secrets
+
+| **Built-in Type**                     | **Usage**                               |
+| ------------------------------------- | --------------------------------------- |
+| `Opaque`                              | Arbitrary user-defined data             |
+| `kubernetes.io/service-account-token` | ServiceAccount token                    |
+| `kubernetes.io/dockercfg`             | Serialized `~/.dockercfg` file          |
+| `kubernetes.io/dockerconfigjson`      | Serialized `~/.docker/config.json` file |
+| `kubernetes.io/basic-auth`            | Credentials for basic authentication    |
+| `kubernetes.io/ssh-auth`              | Credentials for SSH authentication      |
+| `kubernetes.io/tls`                   | Data for a TLS client or server         |
+| `bootstrap.kubernetes.io/token`       | Bootstrap token data                    |
+
+---
+
+## 📂 Creating a Secret
+
+You can create a Secret directly with `kubectl`:
+
+```bash
+kubectl create secret generic db-pass --from-literal=password='123'
+```
+
+Verify it exists:
+
+```bash
+kubectl get secret db-pass
+```
+
+---
+
+## 📜 Secret YAML Example
+
+```yaml
+apiVersion: v1
+kind: Secret
+metadata:
+  name: db-pass
+type: Opaque
+data:
+  password: '123'
+```
+
+---
+
+## 🚀 Using a Secret in a Pod
+
+Secrets can be injected into a Pod as **environment variables**:
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: mariadb-db
+spec:
+  containers:
+    - name: mariadb
+      image: mariadb
+      env:
+        - name: MARIADB_ROOT_PASSWORD
+          valueFrom:
+            secretKeyRef:
+              name: db-pass
+              key: password
+```
+
+This example sets the MariaDB root password from the `db-pass` Secret.
+
+---
+
+✅ **Pro Tip**: Always base64-encode values when writing Secrets directly in YAML. Kubernetes expects the `data` field in base64, not plaintext.
+

From 61ddfa712f497155155130cc16b05f5bf1bb1ad2 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sat, 2 Aug 2025 13:58:24 +0330
Subject: [PATCH 060/116] change secret doc k8s

---
 .../Kubernetes/workloads/13-Secret.md                           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md b/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md
index 7046c01..3faaa5a 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md	
@@ -43,7 +43,7 @@ kind: Secret
 metadata:
   name: db-pass
 type: Opaque
-data:
+stringData:
   password: '123'
 ```
 

From 31639a80494f87185c51e697fc6ae7e350e4a117 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sat, 2 Aug 2025 14:02:46 +0330
Subject: [PATCH 061/116] added nodeport k8s in svc

---
 .../Kubernetes/workloads/09-Services.md        | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md
index a4a3812..402d620 100644
--- a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md	
+++ b/Containerization & Orchestration/Kubernetes/workloads/09-Services.md	
@@ -107,6 +107,7 @@ spec:
 > 🧠 **Tip:** Use `kubectl describe svc <service-name>` to inspect the service and verify connectivity.
 
 
+
 ```yaml
 apiVersion: v1
 kind: Service
@@ -124,3 +125,20 @@ spec:
       port: 80
       targetPort: 8080
 ```
+
+```yaml
+apiVersion: v1
+kind: Service
+metadata:
+  name: db-svc
+  namespace: db
+spec:
+  type: NodePort
+  ports:
+    - name: sql
+      port: 3306
+      targetPort: 3306
+      nodePort: 30000
+  selector:
+    app: db
+```
\ No newline at end of file

From 3a24aaf5f98066ff963c93d405b4cd89afaa83a7 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sat, 2 Aug 2025 22:10:30 +0330
Subject: [PATCH 062/116] update ps,kill doc

---
 Linux/LPIC1/16-ps.md   | 14 ++++++++++++++
 Linux/LPIC1/17-kill.md |  6 ++++++
 2 files changed, 20 insertions(+)

diff --git a/Linux/LPIC1/16-ps.md b/Linux/LPIC1/16-ps.md
index 36b1d94..986e2f6 100644
--- a/Linux/LPIC1/16-ps.md
+++ b/Linux/LPIC1/16-ps.md
@@ -63,3 +63,17 @@ ps aux
 | `TIME`    | Total CPU time used                                |
 | `COMMAND` | Command that started the process                   |
 
+
+### 📑 Show List Jobs
+
+```bash
+jobs
+```
+
+### 🔄Move Process From Background To Forground
+
+```bash
+fg
+```
+
+
diff --git a/Linux/LPIC1/17-kill.md b/Linux/LPIC1/17-kill.md
index 38f8bac..980d96f 100644
--- a/Linux/LPIC1/17-kill.md
+++ b/Linux/LPIC1/17-kill.md
@@ -33,6 +33,12 @@ kill -9 123
 *Doesn’t allow cleanup — use only when necessary.*
 🗡️ *Think of it as the "katana" of kill commands.*
 
+### 📑 Multi Process Kill
+
+```bash
+pidof <ps-name> | xargs kill -9 
+```
+
 ---
 
 ### ⌨️ Interrupt — `SIGINT` (Signal 2)

From 2e8f53ca271f5b17d5df4feaa4b73290c59e2eb6 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 3 Aug 2025 00:33:05 +0330
Subject: [PATCH 063/116] for doc bash script

---
 .../Kubernetes/workloads/14-Ingress.md        |   2 +
 Linux/Bash Script/9-For.md                    | 126 ++++++++++++++++++
 2 files changed, 128 insertions(+)
 create mode 100644 Containerization & Orchestration/Kubernetes/workloads/14-Ingress.md

diff --git a/Containerization & Orchestration/Kubernetes/workloads/14-Ingress.md b/Containerization & Orchestration/Kubernetes/workloads/14-Ingress.md
new file mode 100644
index 0000000..5b67d86
--- /dev/null
+++ b/Containerization & Orchestration/Kubernetes/workloads/14-Ingress.md	
@@ -0,0 +1,2 @@
+traffic input --> ingress
+traffic output --> egress
diff --git a/Linux/Bash Script/9-For.md b/Linux/Bash Script/9-For.md
index e69de29..f626d61 100644
--- a/Linux/Bash Script/9-For.md	
+++ b/Linux/Bash Script/9-For.md	
@@ -0,0 +1,126 @@
+# Bash `for` Loop Cheat Sheet
+
+A clear and concise reference for using `for` loops in Bash, with syntax variations, examples, and best practices.
+
+---
+
+## 1. Basic `for` Loop (List Iteration)
+
+Iterates over a fixed list of items.
+
+**Syntax:**
+
+```bash
+for VARIABLE in ITEM1 ITEM2 ITEM3 ...
+do
+  commands
+DONE
+done
+```
+
+**Example:**
+
+```bash
+for color in red green blue
+do
+  echo "Color: $color"
+done
+```
+
+*Output:*
+
+```
+Color: red
+Color: green
+Color: blue
+```
+
+---
+
+## 2. Numeric Iteration Using a List
+
+When you explicitly list out numbers.
+
+**Example:**
+
+```bash
+for i in 1 2 3 4 5
+do
+  echo "Number: $i"
+done
+```
+
+*Output:*
+
+```
+Number: 1
+Number: 2
+Number: 3
+Number: 4
+Number: 5
+```
+
+---
+
+## 3. C-style `for` Loop (Arithmetic)
+
+Similar to loops in C-style languages: initialize, condition, increment.
+
+**Syntax:**
+
+```bash
+for (( init; condition; increment ))
+do
+  commands
+ndone
+```
+
+**Example:**
+
+```bash
+for (( i=0; i<5; i++ ))
+do
+  echo "Index: $i"
+done
+```
+
+*Output:*
+
+```
+Index: 0
+Index: 1
+Index: 2
+Index: 3
+Index: 4
+```
+
+---
+
+## 4. Looping Over Files (Globbing)
+
+Use shell glob patterns to iterate over matching filenames.
+
+**Example:**
+
+```bash
+for file in *.txt
+do
+  echo "Found text file: $file"
+done
+```
+
+```
+# If the directory contains a.txt and notes.txt, output might be:
+Found text file: a.txt
+Found text file: notes.txt
+```
+
+---
+
+## Summary
+
+| Style             | Purpose                                    | Notes                                 |
+| ----------------- | ------------------------------------------ | ------------------------------------- |
+| `for var in list` | Iterate over a static list or glob results | Most common in shell scripting        |
+| `for (( ... ))`   | Numeric / arithmetic loops                 | C-style syntax, powerful for counters |
+

From 79ac218bcd6447a201e3295d7279468d1b7a1d71 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 3 Aug 2025 00:45:41 +0330
Subject: [PATCH 064/116] while doc bash script

---
 Linux/Bash Script/10-While.md | 138 ++++++++++++++++++++++++++++++++++
 1 file changed, 138 insertions(+)
 create mode 100644 Linux/Bash Script/10-While.md

diff --git a/Linux/Bash Script/10-While.md b/Linux/Bash Script/10-While.md
new file mode 100644
index 0000000..7ad88a7
--- /dev/null
+++ b/Linux/Bash Script/10-While.md	
@@ -0,0 +1,138 @@
+# Bash `while` Loop Guide
+
+A clear, concise, and visually pleasant reference for using `while` loops in Bash.
+
+---
+
+## 1. Overview
+
+The `while` loop in Bash repeatedly executes a block of commands **as long as a condition evaluates to true**. It is a fundamental control structure for iteration when the number of repetitions is not known in advance.
+
+### General form
+
+```bash
+while [ condition ]
+do
+  command1
+  command2
+  ...
+done
+```
+
+* The condition is evaluated before each iteration. If it returns a zero (truthy) exit status, the loop body runs. Otherwise, the loop exits.
+* Square brackets (`[ ... ]`) are a synonym for the `test` command; spacing matters.
+
+---
+
+## 2. Examples
+
+### 2.1 Simple counter
+
+Counts from 1 to 5 and prints the current value.
+
+```bash
+counter=1
+
+while [ $counter -le 5 ]
+do
+  echo "Counter: $counter"
+  ((counter++))
+done
+```
+
+**What it does:**
+
+* Initializes `counter` to 1.
+* The loop continues while `counter` is less than or equal to 5.
+* Prints and increments the counter each iteration.
+
+### 2.2 Waiting for a file to appear
+
+Polls for the existence of `/tmp/myfile.txt` once per second.
+
+```bash
+while [ ! -f /tmp/myfile.txt ]
+do
+  echo "Waiting for file..."
+  sleep 1
+done
+
+echo "File exists!"
+```
+
+**What it does:**
+
+* Checks if the file does **not** exist (`! -f`).
+* Sleeps for one second between checks to avoid busy-waiting.
+* When the file appears, exits the loop and prints confirmation.
+
+### 2.3 Interactive prompt with exit condition
+
+Keeps prompting the user until they type `q`.
+
+```bash
+while true
+do
+  read -p "Type 'q' to quit: " input
+  if [ "$input" = "q" ]; then
+    break
+  fi
+done
+```
+
+**What it does:**
+
+* Uses an infinite loop (`while true`).
+* Prompts the user each time.
+* Exits the loop when the input equals `q` using `break`.
+
+---
+
+## 3. Tips & Best Practices
+
+* **Quote variables** to avoid word splitting and issues when they are empty: `[ "$foo" = "bar" ]`.
+* **Use arithmetic expressions** with `(( ... ))` when dealing with numbers (`((counter++))` is more concise than `counter=$((counter + 1))`).
+* **Avoid busy loops:** if waiting on external state, insert a `sleep` to reduce CPU usage.
+* **Use `set -u` and `set -e`** in scripts to catch undefined variables and stop on errors, but be careful when using them with conditional tests.
+* **Test conditions explicitly:** e.g., use `-f`, `-d`, `-r`, `-s`, etc., for file-related checks.
+
+---
+
+## 4. Common Pitfalls
+
+* Missing spaces inside `[ ]` — `while [$counter -le 5]` is invalid; it must be `[ $counter -le 5 ]`.
+* Forgetting to initialize loop variables, leading to unexpected behavior when using them in tests.
+* Using `read` without handling empty input; consider providing a default or validating.
+* Infinite loops without an exit strategy (e.g., missing `break` or condition never false).
+
+---
+
+## 5. Variations
+
+* **Until loop:** opposite of `while` — runs until a condition becomes true.
+
+  ```bash
+  until [ -f /tmp/myfile.txt ]
+  do
+    echo "Waiting..."
+    sleep 1
+  ```
+
+done
+
+- **Command-based condition:** you can use any command whose exit status matters.
+
+```bash
+while ping -c1 example.com >/dev/null 2>&1
+do
+  echo "Host is reachable"
+  sleep 5
+done
+````
+
+---
+
+## 6. Summary
+
+Use `while` loops when the number of iterations depends on dynamic conditions (user input, file existence, external services). Combine with proper quoting, sleeping, and exit strategies to write robust and readable scripts.
+

From c86d20d4100c530bd62dbd0e69e613e6ac3c1046 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 3 Aug 2025 00:47:45 +0330
Subject: [PATCH 065/116] fixed bash script file numbers

---
 Linux/Bash Script/{1-Echo.md => 01-Echo.md}             | 0
 Linux/Bash Script/{2-Operators.md => 02-Operators.md}   | 0
 Linux/Bash Script/{3-Exit-Codes.md => 03-Exit-Codes.md} | 0
 Linux/Bash Script/{4-Shebang.md => 04-Shebang.md}       | 0
 Linux/Bash Script/{5-Variables.md => 05-Variables.md}   | 0
 Linux/Bash Script/{6-Read.md => 06-Read.md}             | 0
 Linux/Bash Script/{7-If.md => 07-If.md}                 | 0
 Linux/Bash Script/{8-Function.md => 08-Function.md}     | 0
 Linux/Bash Script/{9-For.md => 09-For.md}               | 0
 9 files changed, 0 insertions(+), 0 deletions(-)
 rename Linux/Bash Script/{1-Echo.md => 01-Echo.md} (100%)
 rename Linux/Bash Script/{2-Operators.md => 02-Operators.md} (100%)
 rename Linux/Bash Script/{3-Exit-Codes.md => 03-Exit-Codes.md} (100%)
 rename Linux/Bash Script/{4-Shebang.md => 04-Shebang.md} (100%)
 rename Linux/Bash Script/{5-Variables.md => 05-Variables.md} (100%)
 rename Linux/Bash Script/{6-Read.md => 06-Read.md} (100%)
 rename Linux/Bash Script/{7-If.md => 07-If.md} (100%)
 rename Linux/Bash Script/{8-Function.md => 08-Function.md} (100%)
 rename Linux/Bash Script/{9-For.md => 09-For.md} (100%)

diff --git a/Linux/Bash Script/1-Echo.md b/Linux/Bash Script/01-Echo.md
similarity index 100%
rename from Linux/Bash Script/1-Echo.md
rename to Linux/Bash Script/01-Echo.md
diff --git a/Linux/Bash Script/2-Operators.md b/Linux/Bash Script/02-Operators.md
similarity index 100%
rename from Linux/Bash Script/2-Operators.md
rename to Linux/Bash Script/02-Operators.md
diff --git a/Linux/Bash Script/3-Exit-Codes.md b/Linux/Bash Script/03-Exit-Codes.md
similarity index 100%
rename from Linux/Bash Script/3-Exit-Codes.md
rename to Linux/Bash Script/03-Exit-Codes.md
diff --git a/Linux/Bash Script/4-Shebang.md b/Linux/Bash Script/04-Shebang.md
similarity index 100%
rename from Linux/Bash Script/4-Shebang.md
rename to Linux/Bash Script/04-Shebang.md
diff --git a/Linux/Bash Script/5-Variables.md b/Linux/Bash Script/05-Variables.md
similarity index 100%
rename from Linux/Bash Script/5-Variables.md
rename to Linux/Bash Script/05-Variables.md
diff --git a/Linux/Bash Script/6-Read.md b/Linux/Bash Script/06-Read.md
similarity index 100%
rename from Linux/Bash Script/6-Read.md
rename to Linux/Bash Script/06-Read.md
diff --git a/Linux/Bash Script/7-If.md b/Linux/Bash Script/07-If.md
similarity index 100%
rename from Linux/Bash Script/7-If.md
rename to Linux/Bash Script/07-If.md
diff --git a/Linux/Bash Script/8-Function.md b/Linux/Bash Script/08-Function.md
similarity index 100%
rename from Linux/Bash Script/8-Function.md
rename to Linux/Bash Script/08-Function.md
diff --git a/Linux/Bash Script/9-For.md b/Linux/Bash Script/09-For.md
similarity index 100%
rename from Linux/Bash Script/9-For.md
rename to Linux/Bash Script/09-For.md

From 00122ac85c6bbb17939966edb1612e4a45c797fa Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 3 Aug 2025 20:24:53 +0330
Subject: [PATCH 066/116] link doc

---
 Linux/LPIC1/23-link.md | 66 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 66 insertions(+)
 create mode 100644 Linux/LPIC1/23-link.md

diff --git a/Linux/LPIC1/23-link.md b/Linux/LPIC1/23-link.md
new file mode 100644
index 0000000..04656b9
--- /dev/null
+++ b/Linux/LPIC1/23-link.md
@@ -0,0 +1,66 @@
+# 🔗 **Linux Links: Soft Link vs Hard Link**
+
+## 📝 **Types of Links**
+
+In Linux, there are **two types** of links:
+
+1. 🪶 **Soft Link** (Symbolic Link)
+2. 🪨 **Hard Link**
+
+---
+
+## ⚙️ **Commands**
+
+### 🪶 **Soft Link (Symbolic Link)**
+
+Acts like a **shortcut** pointing to the original file.
+
+```bash
+ln -s <base-file> <link-file>
+```
+
+💡 **Example:**
+
+```bash
+ln -s file.txt file_link.txt
+```
+
+---
+
+### 🪨 **Hard Link**
+
+Points directly to the file's **inode** (physical data on disk).
+
+```bash
+ln <base-file> <link-file>
+```
+
+💡 **Example:**
+
+```bash
+ln file.txt file_hard.txt
+```
+
+---
+
+## 📊 **Soft Link vs Hard Link**
+
+| 🏷️ Feature               | 🪶 Soft Link (Symbolic)           | 🪨 Hard Link                  |
+| ------------------------- | --------------------------------- | ----------------------------- |
+| 🔢 **Inode Number**       | Different from the original file  | Same as original file         |
+| 🗂 **Cross Filesystem**   | ✅ Yes                             | ❌ No                          |
+| ❌ **If Original Deleted** | Link breaks (becomes invalid)     | File still exists             |
+| 📦 **Storage**            | Stores path to original file      | Stores actual data reference  |
+| 🔄 **Update**             | Reflects changes in original file | Reflects changes (same inode) |
+
+---
+
+## 🧠 **Quick Notes**
+
+* **Soft Link** → Think *shortcut* 📎
+* **Hard Link** → Think *clone reference* 📀
+* If you delete the **base file**:
+
+  * 🪶 Soft Link → ❌ Broken link
+  * 🪨 Hard Link → ✅ Still works (data intact)
+

From 838d7bdbbb5d5975960ee20131f4a8b76becc15c Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 4 Aug 2025 16:11:34 +0330
Subject: [PATCH 067/116] disk info doc

---
 .../01-runlevels.md                           |  0
 .../02-directorys.md                          |  0
 .../03-package-managers.md                    |  0
 .../04-dpkg.md                                |  0
 .../{LPIC1 => Basic Administration}/05-apt.md |  0
 .../{LPIC1 => Basic Administration}/06-yum.md |  0
 .../{LPIC1 => Basic Administration}/07-rpm.md |  0
 .../08-setup-ssh.md                           |  0
 .../{LPIC1 => Basic Administration}/09-vim.md |  0
 .../{LPIC1 => Basic Administration}/10-zip.md |  0
 .../{LPIC1 => Basic Administration}/11-tar.md |  0
 .../12-grep.md                                |  0
 .../13-less.md                                |  0
 .../14-head-tail.md                           |  0
 .../{LPIC1 => Basic Administration}/15-wc.md  |  0
 .../{LPIC1 => Basic Administration}/16-ps.md  |  0
 .../17-kill.md                                |  0
 .../18-usermanage.md                          |  0
 .../19-chmod-chown.md                         |  0
 .../{LPIC1 => Basic Administration}/20-ip.md  |  0
 .../21-route.md                               |  0
 .../22-netstat.md                             |  0
 .../23-link.md                                |  0
 Linux/Basic Administration/24-disk-info.md    | 67 +++++++++++++++++++
 24 files changed, 67 insertions(+)
 rename Linux/{LPIC1 => Basic Administration}/01-runlevels.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/02-directorys.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/03-package-managers.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/04-dpkg.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/05-apt.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/06-yum.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/07-rpm.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/08-setup-ssh.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/09-vim.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/10-zip.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/11-tar.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/12-grep.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/13-less.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/14-head-tail.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/15-wc.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/16-ps.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/17-kill.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/18-usermanage.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/19-chmod-chown.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/20-ip.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/21-route.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/22-netstat.md (100%)
 rename Linux/{LPIC1 => Basic Administration}/23-link.md (100%)
 create mode 100644 Linux/Basic Administration/24-disk-info.md

diff --git a/Linux/LPIC1/01-runlevels.md b/Linux/Basic Administration/01-runlevels.md
similarity index 100%
rename from Linux/LPIC1/01-runlevels.md
rename to Linux/Basic Administration/01-runlevels.md
diff --git a/Linux/LPIC1/02-directorys.md b/Linux/Basic Administration/02-directorys.md
similarity index 100%
rename from Linux/LPIC1/02-directorys.md
rename to Linux/Basic Administration/02-directorys.md
diff --git a/Linux/LPIC1/03-package-managers.md b/Linux/Basic Administration/03-package-managers.md
similarity index 100%
rename from Linux/LPIC1/03-package-managers.md
rename to Linux/Basic Administration/03-package-managers.md
diff --git a/Linux/LPIC1/04-dpkg.md b/Linux/Basic Administration/04-dpkg.md
similarity index 100%
rename from Linux/LPIC1/04-dpkg.md
rename to Linux/Basic Administration/04-dpkg.md
diff --git a/Linux/LPIC1/05-apt.md b/Linux/Basic Administration/05-apt.md
similarity index 100%
rename from Linux/LPIC1/05-apt.md
rename to Linux/Basic Administration/05-apt.md
diff --git a/Linux/LPIC1/06-yum.md b/Linux/Basic Administration/06-yum.md
similarity index 100%
rename from Linux/LPIC1/06-yum.md
rename to Linux/Basic Administration/06-yum.md
diff --git a/Linux/LPIC1/07-rpm.md b/Linux/Basic Administration/07-rpm.md
similarity index 100%
rename from Linux/LPIC1/07-rpm.md
rename to Linux/Basic Administration/07-rpm.md
diff --git a/Linux/LPIC1/08-setup-ssh.md b/Linux/Basic Administration/08-setup-ssh.md
similarity index 100%
rename from Linux/LPIC1/08-setup-ssh.md
rename to Linux/Basic Administration/08-setup-ssh.md
diff --git a/Linux/LPIC1/09-vim.md b/Linux/Basic Administration/09-vim.md
similarity index 100%
rename from Linux/LPIC1/09-vim.md
rename to Linux/Basic Administration/09-vim.md
diff --git a/Linux/LPIC1/10-zip.md b/Linux/Basic Administration/10-zip.md
similarity index 100%
rename from Linux/LPIC1/10-zip.md
rename to Linux/Basic Administration/10-zip.md
diff --git a/Linux/LPIC1/11-tar.md b/Linux/Basic Administration/11-tar.md
similarity index 100%
rename from Linux/LPIC1/11-tar.md
rename to Linux/Basic Administration/11-tar.md
diff --git a/Linux/LPIC1/12-grep.md b/Linux/Basic Administration/12-grep.md
similarity index 100%
rename from Linux/LPIC1/12-grep.md
rename to Linux/Basic Administration/12-grep.md
diff --git a/Linux/LPIC1/13-less.md b/Linux/Basic Administration/13-less.md
similarity index 100%
rename from Linux/LPIC1/13-less.md
rename to Linux/Basic Administration/13-less.md
diff --git a/Linux/LPIC1/14-head-tail.md b/Linux/Basic Administration/14-head-tail.md
similarity index 100%
rename from Linux/LPIC1/14-head-tail.md
rename to Linux/Basic Administration/14-head-tail.md
diff --git a/Linux/LPIC1/15-wc.md b/Linux/Basic Administration/15-wc.md
similarity index 100%
rename from Linux/LPIC1/15-wc.md
rename to Linux/Basic Administration/15-wc.md
diff --git a/Linux/LPIC1/16-ps.md b/Linux/Basic Administration/16-ps.md
similarity index 100%
rename from Linux/LPIC1/16-ps.md
rename to Linux/Basic Administration/16-ps.md
diff --git a/Linux/LPIC1/17-kill.md b/Linux/Basic Administration/17-kill.md
similarity index 100%
rename from Linux/LPIC1/17-kill.md
rename to Linux/Basic Administration/17-kill.md
diff --git a/Linux/LPIC1/18-usermanage.md b/Linux/Basic Administration/18-usermanage.md
similarity index 100%
rename from Linux/LPIC1/18-usermanage.md
rename to Linux/Basic Administration/18-usermanage.md
diff --git a/Linux/LPIC1/19-chmod-chown.md b/Linux/Basic Administration/19-chmod-chown.md
similarity index 100%
rename from Linux/LPIC1/19-chmod-chown.md
rename to Linux/Basic Administration/19-chmod-chown.md
diff --git a/Linux/LPIC1/20-ip.md b/Linux/Basic Administration/20-ip.md
similarity index 100%
rename from Linux/LPIC1/20-ip.md
rename to Linux/Basic Administration/20-ip.md
diff --git a/Linux/LPIC1/21-route.md b/Linux/Basic Administration/21-route.md
similarity index 100%
rename from Linux/LPIC1/21-route.md
rename to Linux/Basic Administration/21-route.md
diff --git a/Linux/LPIC1/22-netstat.md b/Linux/Basic Administration/22-netstat.md
similarity index 100%
rename from Linux/LPIC1/22-netstat.md
rename to Linux/Basic Administration/22-netstat.md
diff --git a/Linux/LPIC1/23-link.md b/Linux/Basic Administration/23-link.md
similarity index 100%
rename from Linux/LPIC1/23-link.md
rename to Linux/Basic Administration/23-link.md
diff --git a/Linux/Basic Administration/24-disk-info.md b/Linux/Basic Administration/24-disk-info.md
new file mode 100644
index 0000000..b69a8b6
--- /dev/null
+++ b/Linux/Basic Administration/24-disk-info.md	
@@ -0,0 +1,67 @@
+# 💽 **Disk Partition Types & Commands Guide**
+
+## 🗂 **Partition Types**
+
+### 1️⃣ **MBR (Master Boot Record)**
+
+* 📏 **Max Disk Size:** 2 TB
+* 📦 **Partition Entries:** 4
+
+---
+
+### 2️⃣ **GPT (GUID Partition Table)**
+
+* 📏 **Max Disk Size:** 9 ZB (zettabytes)
+* 📦 **Partition Entries:** 128
+
+---
+
+## 📊 **Disk Space & Usage Commands**
+
+### 🖥 **`df` – Show Disk Space Usage**
+
+The `df` command displays information about available and used disk space.
+
+| Command               | Description                              |
+| --------------------- | ---------------------------------------- |
+| `df`          | 📄 Show disk space in default format     |
+| `df -h`       | 🧍 Human-readable sizes (e.g., GB, MB)   |
+| `df -T`       | 📂 Show file system type                 |
+| `df -i`       | 🔢 Show inode usage                      |
+| `df -h /home` | 🏠 Show usage for `/home` directory only |
+
+---
+
+### 📦 **`du` – Show Disk Usage**
+
+The `du` command shows how much space files and directories take up.
+
+| Command                       | Description                              |
+| ----------------------------- | ---------------------------------------- |
+| `du`                  | 📄 Show disk usage in blocks             |
+| `du -h`               | 🧍 Human-readable sizes                  |
+| `du -sh`              | 📊 Summary of current directory          |
+| `du -h --max-depth=1` | 📂 Usage per subdirectory (1 level deep) |
+
+---
+
+## 🔍 **Disk & Partition Information Commands**
+
+### 💿 **`lsblk`**
+
+Shows partitions, disks, sizes, and mount points.
+
+```bash
+lsblk
+```
+
+---
+
+### 🆔 **`blkid`**
+
+Displays partition UUIDs and types.
+
+```bash
+blkid
+```
+

From 64032b8e8eaf1196e8737561a5f0e66058db12cb Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 7 Aug 2025 22:25:20 +0330
Subject: [PATCH 068/116] linux doc : disk manage

---
 Linux/Basic Administration/25-disk-manage.md | 110 +++++++++++++++++++
 1 file changed, 110 insertions(+)
 create mode 100644 Linux/Basic Administration/25-disk-manage.md

diff --git a/Linux/Basic Administration/25-disk-manage.md b/Linux/Basic Administration/25-disk-manage.md
new file mode 100644
index 0000000..41b1175
--- /dev/null
+++ b/Linux/Basic Administration/25-disk-manage.md	
@@ -0,0 +1,110 @@
+# 📘 Disk Partitioning Guide: MBR & GPT using `fdisk` and `gdisk`
+
+## 🔹 Overview
+
+* Use `**fdisk**` for **MBR (Master Boot Record)** partitioning.
+* For **GPT (GUID Partition Table)**, the recommended tool is `**gdisk**`, but `fdisk` also supports GPT.
+
+---
+
+## 🧰 Disk Partitioning with `fdisk`
+
+### 🔍 List Partitions
+
+| Command    | Description                         |
+| ---------- | ----------------------------------- |
+| `fdisk -l` | Show list of available partitions   |
+| `fdisk -x` | Show list with extended information |
+
+### ⚙️ Launch `fdisk`
+
+```bash
+fdisk /dev/sdX
+```
+
+Replace `/dev/sdX` with your actual disk name (e.g., `/dev/sdb`).
+
+---
+
+### 📖 Inside `fdisk`
+
+Once inside the `fdisk` prompt:
+
+| Key | Function                          |
+| --- | --------------------------------- |
+| `m` | Show help                         |
+| `p` | Print partition table (disk info) |
+| `n` | Create new partition              |
+| `t` | Change partition type             |
+| `w` | Write changes and exit            |
+
+#### ➕ Creating a Partition (`n`)
+
+* Choose **`p`** for **primary** or **`e`** for **extended** partition.
+* MBR allows **4 primary** partitions. One of them can be **extended**, which can hold **logical** partitions.
+
+#### 📏 Define Partition Size
+
+Example:
+
+```bash
++512M
+```
+
+---
+
+## 🧱 Create Filesystem
+
+To format the partition with `ext4`:
+
+```bash
+mkfs.ext4 /dev/sdb1
+```
+
+---
+
+## 🔗 Get Partition UUID
+
+Option 1: After formatting, the UUID is shown in output.
+Option 2: Use `blkid` to retrieve it:
+
+```bash
+blkid
+```
+
+---
+
+## 📝 Mount Using `/etc/fstab`
+
+1. Open the `fstab` configuration file:
+
+```bash
+vim /etc/fstab
+```
+
+2. Add the following line:
+
+```
+/dev/disk/by-uuid/<UUID> <mount_path> <filesystem> defaults 0 1
+```
+
+### Example:
+
+```
+/dev/disk/by-uuid/1eb043d2-f2ee-4a69-a7c4-13c283c3ccc6 /test ext4 defaults 0 1
+```
+
+This ensures the partition is mounted automatically at boot.
+
+---
+
+## ✅ Summary
+
+| Task               | Command/Action        |
+| ------------------ | --------------------- |
+| List partitions    | `fdisk -l`            |
+| Start partitioning | `fdisk /dev/sdX`      |
+| Format partition   | `mkfs.ext4 /dev/sdX1` |
+| Get UUID           | `blkid`               |
+| Edit fstab         | `vim /etc/fstab`      |
+

From 495e4f4bc854f9887e3e14e7826b108ed0351745 Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Fri, 8 Aug 2025 01:09:37 +0330
Subject: [PATCH 069/116] Update README.md

---
 README.md | 63 ++++++++++++++++++++++++++++++-------------------------
 1 file changed, 35 insertions(+), 28 deletions(-)

diff --git a/README.md b/README.md
index 55bced6..85a9cea 100755
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# 🐧 Linux Documents
+# 🐧 DevOps Documents
 
 A curated collection of scripts, configuration files, and guides for managing and configuring Linux-based systems. This personal repository serves as a comprehensive knowledge base to simplify deployment, automation, monitoring, security, and much more.
 
@@ -12,10 +12,10 @@ A curated collection of scripts, configuration files, and guides for managing an
 
 ### 🐳 Containerization & Orchestration
 - [Docker](./Containerization%20&%20Orchestration/Docker)
-- [Kubernetes(On Working)](./Containerization%20&%20Orchestration/Kubernetes)
+- [Kubernetes (In Progress)](./Containerization%20&%20Orchestration/Kubernetes)
 
 ### 🗄️ Databases
-- [Postgresql](./Databases/Postgresql)
+- [PostgreSQL](./Databases/Postgresql)
 
 ### ⚡ Caching
 - [Redis](./Caching/redis)
@@ -24,11 +24,11 @@ A curated collection of scripts, configuration files, and guides for managing an
 - [Git](./Code%20Management/Git)
 
 ### 🔀 High Availability
-- [Ha-Proxy](./High%20Availability/Ha-Proxy)
+- [HAProxy](./High%20Availability/Ha-Proxy)
 
 ### 📊 Monitoring & Logging
 - [Grafana](./Monitoring%20&%20Logging/Grafana)
-- [Librenms](./Monitoring%20&%20Logging/Librenms)
+- [LibreNMS](./Monitoring%20&%20Logging/Librenms)
 - [Netdata](./Monitoring%20&%20Logging/Netdata)
 - [Zabbix](./Monitoring%20&%20Logging/Zabbix)
 
@@ -36,7 +36,7 @@ A curated collection of scripts, configuration files, and guides for managing an
 - [iptables](./Security%20&%20Networking/Iptables)
 - [Nmap](./Security%20&%20Networking/Nmap)
 - [Nginx](./Security%20&%20Networking/Nginx)
-- [FileSharing](./Security%20&%20Networking/FileSharing)
+- [File Sharing](./Security%20&%20Networking/FileSharing)
 
 ### 📦 Storage
 - [NFS](./Storage/NFS)
@@ -44,16 +44,11 @@ A curated collection of scripts, configuration files, and guides for managing an
 ### 🧠 System & Kernel Management
 - [Kernel](./System%20&%20Kernel%20Management/Kernel)
 
-### 🌐 Web Development & Frameworks
-- [Django](./Web%20Development%20&%20Frameworks/Django)
-- [Laravel API Setup](./Web%20Development%20&%20Frameworks/LaravelAPI)
-- [Laravel on Nginx](./Web%20Development%20&%20Frameworks/LaravelOnNginx)
-
 ### 🔁 Web Servers & Reverse Proxies
-- [Nginx](./Web%20Servers%20&%20Reverse%20Proxies/Nginx)
+- [Nginx (Web)](./Web%20Servers%20&%20Reverse%20Proxies/Nginx)
 
 ### 🤖 Bots & Automation Tools
-- [TelegramBot](./Bots%20&%20Automation%20Tools/TelegramBot)
+- [Telegram Bot](./Bots%20&%20Automation%20Tools/TelegramBot)
 
 ### 📝 Miscellaneous
 - [Info](./Info)
@@ -65,35 +60,47 @@ A curated collection of scripts, configuration files, and guides for managing an
 ```bash
 git clone https://github.com/RadinPirouz/linux-documents.git
 cd linux-documents
-```
+````
 
-- Explore each folder for setup guides, scripts, and configuration examples.
-- Follow individual READMEs or documentation inside each directory before running any scripts.
+* Explore each folder for setup guides, scripts, and configuration examples.
+* Follow individual README or documentation files inside each directory before running any scripts.
 
 ---
 
 ## 📌 Notes
-- Tested on **Debian/Ubuntu** and **CentOS/RHEL**-based distributions.
-- Always review and test configurations in a staging environment before applying to production.
+
+* Tested on **Debian/Ubuntu** and **CentOS/RHEL**-based distributions.
+* ⚠️ Always review and test configurations in a staging environment before applying to production.
 
 ---
 
 ## 🤝 Contributing
 
 Contributions are welcome! 🛠️
-1. Fork the repository.
-2. Create a new branch (`git checkout -b feature/YourFeature`).
-3. Commit your changes (`git commit -m "Add new config for X"`).
-4. Push to the branch (`git push origin feature/YourFeature`).
-5. Open a Pull Request. 🙌
 
-Please ensure your code is tested and documented.
+1. Fork the repository.
+2. Create a new branch:
+   `git checkout -b feature/YourFeature`
+3. Commit your changes:
+   `git commit -m "Add new config for X"`
+4. Push to the branch:
+   `git push origin feature/YourFeature`
+5. Open a Pull Request 🙌
+
+Please ensure your code is tested and well-documented.
+
 ---
 
 ## 📬 Contact
 
-Questions or feedback? 📫
-- Telegram: [@RadinPirouz](https://t.me/RadinPirouz)
-- GitHub Issues: Open an issue in this repo
+Questions or feedback? Reach out:
+
+* 💬 Telegram: [@RadinPirouz](https://t.me/RadinPirouz)
+* 🐛 GitHub Issues: [Open an Issue](https://github.com/RadinPirouz/linux-documents/issues)
+
+---
+
+## ⭐️ Support
+
+If you find this repository useful, please give it a ⭐ and share it with others!
 
-⭐ If you find this repository useful, don’t forget to give it a star!

From 8364efca597ee8210016f97fd5d82b9d8579ab32 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 10 Aug 2025 00:43:44 +0330
Subject: [PATCH 070/116] update docker file doc

---
 .../Docker/3-Docker-File.md                   | 148 ++++++++++--------
 1 file changed, 80 insertions(+), 68 deletions(-)

diff --git a/Containerization & Orchestration/Docker/3-Docker-File.md b/Containerization & Orchestration/Docker/3-Docker-File.md
index cc69eca..6920bd3 100755
--- a/Containerization & Orchestration/Docker/3-Docker-File.md	
+++ b/Containerization & Orchestration/Docker/3-Docker-File.md	
@@ -1,148 +1,160 @@
-## What is a Dockerfile?
-
-A **Dockerfile** is a simple text file containing instructions to create a Docker image. Docker images provide a consistent and reproducible environment for running applications in containers. By defining dependencies, configurations, and the operating system, Dockerfiles automate the image creation process, ensuring version-controlled and portable environments.
-
-### Key Concepts:
-
-- **Base Image**: The foundational layer of your image, typically an official operating system like Ubuntu, CentOS, or Alpine Linux.
-- **Instructions**: Commands such as `RUN`, `COPY`, and `CMD` define what’s installed, how the image behaves, and which files to include.
-  
-  Common instructions include:
-  - **`RUN`**: Executes commands (e.g., installing software) inside the container.
-  - **`COPY`**: Copies files from your local machine to the image.
-  - **`CMD`**: Specifies the default command to run when the container starts.
+# 🚢 Understanding Dockerfile: A Complete Guide
 
 ---
 
-## Step-by-Step Guide to Creating a Dockerfile
+## 📄 What is a Dockerfile?
 
-### 1. Create a File Named `Dockerfile`
+A **Dockerfile** is a simple text file containing instructions to create a **Docker image**. Docker images provide a consistent, reproducible environment to run applications inside containers. By defining dependencies, configurations, and the operating system, Dockerfiles automate image creation, ensuring version-controlled and portable environments.
 
-Start by creating a file called `Dockerfile` in your project directory. If you name it something else, you'll need to specify the file name during the build process.
+---
+
+### 🔑 Key Concepts:
+
+* 🏗️ **Base Image**: The foundational layer of your image, usually an official OS like Ubuntu, CentOS, or Alpine Linux.
+* 📝 **Instructions**: Commands that tell Docker what to install, how the image behaves, and which files to include.
+
+Common instructions include:
+
+| Instruction | Description                                                      |
+| ----------- | ---------------------------------------------------------------- |
+| 🏃‍♂️ `RUN` | Executes commands inside the container (e.g., install software). |
+| 📁 `COPY`   | Copies files from your local machine to the image.               |
+| ▶️ `CMD`    | Specifies the default command when the container starts.         |
+
+---
+
+## 🛠️ Step-by-Step Guide to Creating a Dockerfile
+
+---
+
+### 1️⃣ Create a File Named `Dockerfile`
+
+Create a file called `Dockerfile` in your project directory. If named differently, specify the filename during build.
 
 #### Example Dockerfile:
 
 ```dockerfile
-# Use Ubuntu 22.04 as the base image
+# 🐧 Use Ubuntu 22.04 as the base image
 FROM ubuntu:22.04
 
-# Add metadata such as version information
+# 🏷️ Add metadata such as version information
 LABEL version="0.0.1"
 
-# Update package lists and install essential tools
+# 🔄 Update package lists and install essential tools
 RUN apt update && apt install -y bash vim curl
 
-# Install Nginx web server
+# 🌐 Install Nginx web server
 RUN apt install -y nginx
 ```
 
-#### Breakdown of Instructions:
+**Explanation:**
 
-- **`FROM ubuntu:22.04`**: Defines Ubuntu 22.04 as the base image.
-- **`LABEL version="0.0.1"`**: Adds metadata, such as the version label.
-- **`RUN`**: Runs commands inside the container. In this case, it updates package lists and installs `bash`, `vim`, `curl`, and `nginx`.
+* `FROM ubuntu:22.04` — Use Ubuntu 22.04 as the base image.
+* `LABEL version="0.0.1"` — Adds version metadata.
+* `RUN` — Executes commands inside the container to install tools and software.
 
 ---
 
-### 2. Example Using Alpine Linux
+### 2️⃣ Example Using Alpine Linux
 
-Alpine Linux is a lightweight option that results in smaller images. Here's an example of a Dockerfile using Alpine:
+Alpine Linux is lightweight and creates smaller images.
 
 ```dockerfile
-# Use Alpine as the base image
+# 🐧 Use Alpine as the base image
 FROM alpine
 
-# Add version metadata
+# 🏷️ Add version metadata
 LABEL version="0.0.1"
 
-# Update package lists and install essential tools
+# 🔄 Update package lists and install essential tools
 RUN apk update && apk add bash vim curl
 ```
 
-This example is perfect for when you need a compact, minimalistic image.
+Perfect for a compact, minimalistic image.
 
 ---
 
-### 3. Complex Dockerfile with a Script
-
-In this example, you'll learn how to copy a script into the container, set a working directory, and make the script executable.
+### 3️⃣ Complex Dockerfile with a Script
 
 ```dockerfile
-# Start with Alpine as the base image
+# 🐧 Start with Alpine as the base image
 FROM alpine
 
-# Add metadata
+# 🏷️ Add metadata
 LABEL version="0.0.1"
 
-# Update package lists and install essential tools
+# 🔄 Update packages and install essential tools
 RUN apk update && apk add bash vim curl iputils-ping
 
-# Copy the script into the image
+# 📂 Copy the script into the image
 COPY <local-file-path> <container-destination-path>
 
-# Set the working directory for subsequent commands
+# 🏠 Set working directory
 WORKDIR <container-destination-path>
 
-# Add environment variables
+# 🌿 Add environment variables
 ENV API_KEY="123445"
 
-# Set user and expose ports
+# 👤 Set user and expose ports
 USER deploy
 EXPOSE 3210
 
-# Give execution permissions to the script
+# ⚙️ Make the script executable
 RUN chmod +x app.sh
 
-# Define the default command to run
+# ▶️ Default command to run
 CMD ["./app.sh"]
-# Alternatively, you can use ENTRYPOINT
+# Alternatively, ENTRYPOINT ensures always running the executable
 ENTRYPOINT ["bash", "./app.sh"]
 ```
 
-#### Key Concepts in This Example:
-- **`COPY`**: Copies a file from your local machine to the container.
-- **`WORKDIR`**: Sets the working directory inside the container for subsequent commands.
-- **`RUN chmod +x app.sh`**: Grants execution permissions to the `app.sh` script.
-- **`CMD` vs. `ENTRYPOINT`**: `CMD` provides default behavior, while `ENTRYPOINT` is used when you want to ensure the container always runs a specific executable.
+---
+
+### ❤️ Health Check Setup
+
+```dockerfile
+HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
+  CMD curl -f http://localhost/ || exit 1
+```
+
+* ⏲️ **interval**: time between checks
+* ⏳ **timeout**: fail if check takes longer than 5 seconds
+* 🔄 **retries**: mark container unhealthy after failed attempts
+* 🛡️ **start-period**: grace period before counting failures
 
 ---
 
-### 4. Build Your Docker Image
-
-Once your `Dockerfile` is ready, build the Docker image using the `docker build` command.
+### 4️⃣ Build Your Docker Image
 
 ```bash
 docker build -t <app-name> <path-to-dockerfile>
 ```
 
-#### Usage Examples:
+**Examples:**
+
+* Build with Dockerfile in current directory:
 
-- To build with a `Dockerfile` in the current directory:
   ```bash
   docker build -t app-test .
   ```
-  Here, the `.` indicates the current directory as the build context.
+* Use custom Dockerfile name:
 
-- If your file is named something other than `Dockerfile` (e.g., `CustomDockerfile`):
   ```bash
   docker build -t app-test -f <CustomDockerfile> .
   ```
-- If you want build file without use cache 
-  ```bash
-    docker build -t app-test:v1 -f <Custom-Dir> . --no-cache
-  ```
+* Build without cache:
 
-#### Explanation:
-- **`docker build`**: Builds a Docker image.
-- **`-t <app-name>`**: Tags the image with a name (e.g., `app-test`).
-- **`<path-to-dockerfile>`**: Specifies the location of the `Dockerfile`. Use `.` for the current directory or provide an absolute path.
+  ```bash
+  docker build -t app-test:v1 -f <Custom-Dir> . --no-cache
+  ```
 
 ---
 
-## Summary
+## 📋 Summary
 
-A **Dockerfile** is a powerful tool for automating the creation of Docker images. Here’s a quick recap:
+A **Dockerfile** is a powerful tool for automating Docker image creation:
+
+1. 📝 **Create a Dockerfile**: Define the image with `FROM`, `RUN`, `COPY`, and `CMD`.
+2. 🏗️ **Build the Image**: Use `docker build` to generate your image.
+3. 🚀 **Run the Container**: Use `docker run` to start your container.
 
-1. **Create a Dockerfile**: Use instructions like `FROM`, `RUN`, `COPY`, and `CMD` to define the image.
-2. **Build the Image**: Run the `docker build` command to turn your Dockerfile into a Docker image.
-3. **Run the Container**: Once the image is built, use `docker run` to create and run a container based on it.

From 28a5b42df34aca5332fb9be50177c2ae13e39aba Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 10 Aug 2025 20:47:14 +0330
Subject: [PATCH 071/116] free commnad

---
 Linux/Basic Administration/26-free.md | 29 +++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 Linux/Basic Administration/26-free.md

diff --git a/Linux/Basic Administration/26-free.md b/Linux/Basic Administration/26-free.md
new file mode 100644
index 0000000..633c993
--- /dev/null
+++ b/Linux/Basic Administration/26-free.md	
@@ -0,0 +1,29 @@
+## 🖥️ Viewing Memory Usage with `free`
+
+The `free` command shows your system’s memory usage.
+
+```bash
+free
+```
+
+For **human-readable** output (MB, GB, etc.):
+
+```bash
+free -h
+```
+
+**📊 Explanation of columns:**
+
+| Column           | Description                                                        |
+| ---------------- | ------------------------------------------------------------------ |
+| **💾 total**     | Total physical memory (RAM) available in the system.               |
+| **📂 used**      | Memory currently used by processes and the system.                 |
+| **🆓 free**      | Completely unused RAM (not allocated to anything).                 |
+| **🔄 shared**    | Memory shared between multiple processes.                          |
+| **⚡ buff/cache** | Memory used for file buffers and cache to improve performance.     |
+| **✅ available**  | Estimated memory available for starting new apps without swapping. |
+
+💡 **Pro Tip:**
+
+* `✅ available` is more useful than `🆓 free` for knowing how much memory you can actually use, since Linux keeps unused memory in cache for speed.
+

From a3d2d9a9e19376230ff94602ca1218c7ef232024 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 10 Aug 2025 21:32:52 +0330
Subject: [PATCH 072/116] top command

---
 Linux/Basic Administration/27-top-htop.md | 34 +++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 Linux/Basic Administration/27-top-htop.md

diff --git a/Linux/Basic Administration/27-top-htop.md b/Linux/Basic Administration/27-top-htop.md
new file mode 100644
index 0000000..4d9aa96
--- /dev/null
+++ b/Linux/Basic Administration/27-top-htop.md	
@@ -0,0 +1,34 @@
+## 🕵️‍♂️ Monitoring Processes with `top`
+
+The `top` command provides a simple, real-time overview of all running processes and system stats.
+
+```bash
+top
+```
+
+### Sample output header:
+
+```bash
+top - 21:28:31 up 10:05,  5 users,  load average: 0.19, 0.26, 0.23
+
+Tasks: 382 total,   1 running, 381 sleeping,   0 stopped,   0 zombie
+
+%Cpu(s):  8.0 us,  1.8 sy,  0.0 ni, 90.2 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
+
+MiB Mem :  19754.0 total,  14439.8 free,   3207.1 used,   2871.8 buff/cache
+
+MiB Swap:   8192.0 total,   8192.0 free,      0.0 used.  16547.0 avail Mem
+```
+
+### What each part means:
+
+| Item              | Description                                                                     |
+| ----------------- | ------------------------------------------------------------------------------- |
+| 🕒 `21:28:31`     | Current system time                                                             |
+| ⏳ `up 10:05`      | System uptime — 10 hours and 5 minutes since last boot                          |
+| 👥 `5 users`      | Number of users currently logged in                                             |
+| 📈 `load average` | CPU load averages over 1, 5, and 15 minutes (fractions of total CPU cores used) |
+|                   | — 0.19 = load in last 1 min                                                     |
+|                   | — 0.26 = load in last 5 min                                                     |
+|                   | — 0.23 = load in last 15 min                                                    |
+

From dbfef14ac458863c19c9b8e2e260f394eaea15b6 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sun, 10 Aug 2025 21:40:27 +0330
Subject: [PATCH 073/116] nload doc

---
 Linux/Basic Administration/28-nload.md | 47 ++++++++++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 Linux/Basic Administration/28-nload.md

diff --git a/Linux/Basic Administration/28-nload.md b/Linux/Basic Administration/28-nload.md
new file mode 100644
index 0000000..ee15aa1
--- /dev/null
+++ b/Linux/Basic Administration/28-nload.md	
@@ -0,0 +1,47 @@
+## 📊 Network Monitoring with `nload`
+
+```bash
+nload [options] [interface]
+```
+
+* If no interface is specified, `nload` lists available interfaces and lets you choose one.
+* Displays **two graphs**:
+  🔽 Incoming traffic
+  🔼 Outgoing traffic
+
+---
+
+### ⚙️ Options
+
+| Option              | Description                                                                                           |
+| ------------------- | ----------------------------------------------------------------------------------------------------- |
+| `-u <unit>`         | Set unit for data rates (bits, bytes, kilobits, etc.) Options: `b`, `B`, `k`, `m`, `g` (default: `b`) |
+| `-t <milliseconds>` | Refresh interval in milliseconds (default: 500 ms)                                                    |
+| `-m`                | Show minimum and maximum network usage statistics                                                     |
+| `-a`                | Show average network usage statistics                                                                 |
+| `-q`                | Quiet mode — no graphical output, only numeric data                                                   |
+| `-V`                | Show version info and exit                                                                            |
+| `-h`                | Show help message and exit                                                                            |
+
+---
+
+### 💡 Examples
+
+**Monitor a specific interface (e.g., eth0):**
+
+```bash
+nload eth0
+```
+
+**Use bytes per second as unit:**
+
+```bash
+nload -u B eth0
+```
+
+**Set refresh interval to 1 second:**
+
+```bash
+nload -t 1000 eth0
+```
+

From ae273d1149742d617351b9ddbf131226650cc636 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 12 Aug 2025 20:10:34 +0330
Subject: [PATCH 074/116] iptable doc

---
 Security & Networking/Iptables/iptables.md | 284 ++++++++++++++++++---
 Security & Networking/Iptables/temp.md     | 114 +++++++++
 2 files changed, 359 insertions(+), 39 deletions(-)
 create mode 100644 Security & Networking/Iptables/temp.md

diff --git a/Security & Networking/Iptables/iptables.md b/Security & Networking/Iptables/iptables.md
index ef38fae..6f5185a 100755
--- a/Security & Networking/Iptables/iptables.md	
+++ b/Security & Networking/Iptables/iptables.md	
@@ -1,52 +1,258 @@
-## First Whitelist Port and Block Ports at the End
+# 🛡️ Iptables & Netfilter Guide
 
 
+## 🌐 Overview
 
-```bash
-iptables -A/-I/-D INPUT/OUTPUT/FORWARD -i/-o interface -s/-d address -p tcp/udp/icmp --sport/--dport 80 -j ACCEPT/REJECT/DROP/LOG/MASQUARATE 
+**iptables** works with **Netfilter** to manage and control network traffic on Linux systems.
+
+---
+
+## 🔗 Connection Types
+
+1. **NEW** – A new connection being initiated
+2. **ESTABLISHED** – An existing, ongoing connection
+3. **RELATED** – A new connection related to an existing one
+
+---
+
+## 🧰 iptables-persistent
+
+Install iptables and save the rules to a file for persistence across reboots.
+
+---
+
+## 📂 Default Path
+
+```plaintext
+/etc/iptables
 ```
 
-- `-A`: Append
-- `-I`: Insert
-- `-D`: Delete
-- `-i`: Input interface
-- `-o`: Output interface
-- `-s`: Source
-- `-d`: Destination
-- `-p`: Protocol
-- `--sport`: Source port
-- `--dport`: Destination port
-- `-j`: Action
-  - `ACCEPT`: Accept the packet
-  - `REJECT`: Reject the packet with an appropriate ICMP message
-  - `DROP`: Silently discard the packet
-  - `LOG`: Log the packet
-  - `MASQUERADE`: Source NAT
+---
 
-### Examples:
-
-- `iptables -nvL`: Print Iptables Rules
-- `iptables -P INPUT DROP`: Drop All Incoming Packets
-- `iptables -P OUTPUT DROP`: Drop All Outgoing Packets
-- `iptables -A INPUT -p tcp --dport 22 -j ACCEPT`: Accept Incoming Traffic to Port 22 with TCP Protocol
-- `iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT`: Accept Outgoing Traffic from Port 22 with TCP Protocol
-- `iptables -A INPUT -p tcp -s 192.168.1.100 -j DROP`: Drop All Packets Incoming With TCP Protocol From 192.168.1.100
-- `iptables -A INPUT -p tcp --dport 443 -j ACCEPT`: Accept Incoming Traffic to Port 443 (HTTPS) with TCP Protocol
-- `iptables -A INPUT -p tcp -m multiport --dport 22,443,80,3306 -j ACCEPT`: Accept Incoming Traffic to Multiple Ports: 22 (SSH), 80 (HTTP), 3306 (Database), 443 (HTTPS) with TCP Protocol
-- `iptables -A INPUT -p tcp -m multiport --dport 22,443,80,3306 -d 192.168.10.0/24 -j ACCEPT`: Accept Incoming Traffic to Multiple Ports: 22 (SSH), 80 (HTTP), 3306 (Database), 443 (HTTPS) with TCP Protocol to Destination 192.168.10.0
-- `iptables -A INPUT -p tcp --dport 80 -m limit --limit 100/minute --limit-burst 200 -j ACCEPT`: Allow incoming TCP traffic on port 80 with rate limiting
-- `iptables -t NAT -A PREROUTING -i ens33 -p tcp --dport 80 -j REDIRECT --to-port 443`: Redirect traffic from port 80 to port 443 using NAT
-
-### Saving rules for permanent:
-
-To save the rules for permanent usage, you can install the `iptables-persistent` package:
+## ⚙️ Command Format
 
 ```bash
-apt install iptables-persistent
+iptables -t <table-name> <option> <chain-name> <match> -j <action>
 ```
 
-Then, save the rules to the appropriate file:
+---
+
+## 🏷️ Table Names
+
+| Table Name | Purpose                          |
+| ---------- | -------------------------------- |
+| filter     | Default – Filtering Packets      |
+| nat        | Network Address Translation      |
+| mangle     | Packet alteration/editing        |
+| raw        | Pre-processing packets before OS |
+
+---
+
+## 🔄 Chains
+
+| Table  | Chains                                          |
+| ------ | ----------------------------------------------- |
+| filter | INPUT, OUTPUT, FORWARD                          |
+| nat    | PREROUTING, OUTPUT, POSTROUTING                 |
+| mangle | PREROUTING, INPUT, FORWARD, OUTPUT, POSTROUTING |
+| raw    | PREROUTING, OUTPUT                              |
+
+---
+
+## 🚦 Chain Functions
+
+| Chain       | Description                                              |
+| ----------- | -------------------------------------------------------- |
+| INPUT       | Incoming connections to the server                       |
+| OUTPUT      | Outgoing packets from the server                         |
+| FORWARD     | Packets routed through the server to other destinations  |
+| PREROUTING  | Edit packets before routing                              |
+| POSTROUTING | Edit packets after routing and before exiting the server |
+
+---
+
+## 🔧 Options
+
+| Option | Meaning     |
+| ------ | ----------- |
+| `-A`   | Append rule |
+| `-I`   | Insert rule |
+| `-D`   | Delete rule |
+
+---
+
+## 🎯 Actions
+
+| Action     | Description                                  |
+| ---------- | -------------------------------------------- |
+| ACCEPT     | Accept the packet                            |
+| DROP       | Drop the packet silently (no response)       |
+| REJECT     | Drop the packet and send a rejection message |
+| LOG        | Log the packet details                       |
+| MASQUERADE | Perform NAT masquerading                     |
+
+---
+
+## 🧩 iptables Command Examples & Explanations
+
+---
+
+### 1️⃣ Save Current Rules to a File
 
 ```bash
-iptables-save > /etc/iptables/rule.v4
+iptables-save >> <file_path>
 ```
+
+💾 **Explanation:**
+This command saves the current iptables rules to a file (`<file_path>`). Useful for backing up or persisting your firewall rules.
+
+---
+
+### 2️⃣ List Rules in Default Filter Table
+
+```bash
+iptables -nL
+```
+
+📜 **Explanation:**
+Lists all rules in the default `filter` table, showing rules without resolving IPs to names (`-n` speeds it up).
+
+---
+
+### 3️⃣ List Rules in NAT Table
+
+```bash
+iptables -t nat -nL
+```
+
+🔄 **Explanation:**
+Lists all NAT table rules. NAT is used for modifying packets, like translating IP addresses.
+
+---
+
+### 4️⃣ Allow Traffic from a Specific IP (Insert Rule)
+
+```bash
+iptables -t filter -I INPUT -s 192.168.1.100 -j ACCEPT
+```
+
+✅ **Explanation:**
+Inserts (`-I`) a rule at the top of the `INPUT` chain to ACCEPT all packets coming from IP `192.168.1.100`.
+
+---
+
+### 5️⃣ Drop All Incoming Packets (Insert Rule)
+
+```bash
+iptables -t filter -I INPUT -j DROP
+```
+
+⛔ **Explanation:**
+Inserts a rule to DROP all incoming packets on the `INPUT` chain, effectively blocking all new inbound traffic.
+
+---
+
+### 6️⃣ Append Drop Rule at End of INPUT Chain
+
+```bash
+iptables -t filter -A INPUT -j DROP
+```
+
+⏳ **Explanation:**
+Appends (`-A`) a rule at the end of the `INPUT` chain to drop packets that don’t match previous ACCEPT rules.
+
+---
+
+### 7️⃣ Allow Incoming TCP Traffic on Port 22 (SSH)
+
+```bash
+iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+```
+
+🔓 **Explanation:**
+Allows incoming TCP traffic on port 22, which is commonly used for SSH connections.
+
+---
+
+### 8️⃣ Drop Incoming TCP Traffic on Port 22 (SSH)
+
+```bash
+iptables -I INPUT -p tcp --dport 22 -j DROP
+```
+
+🚫 **Explanation:**
+Inserts a rule to DROP all incoming TCP traffic destined for port 22, blocking SSH access.
+
+---
+
+### 9️⃣ Drop TCP Traffic From a Specific IP
+
+```bash
+iptables -A INPUT -p tcp -s 192.168.1.100 -j DROP
+```
+
+📵 **Explanation:**
+Drops all incoming TCP packets coming from IP `192.168.1.100`.
+
+---
+
+### 🔟 Allow Incoming TCP Traffic on Port 443 (HTTPS)
+
+```bash
+iptables -A INPUT -p tcp --dport 443 -j ACCEPT
+```
+
+🔐 **Explanation:**
+Allows incoming TCP traffic on port 443, used for secure HTTPS connections.
+
+---
+
+### 1️⃣1️⃣ Allow Multiple Ports Using Multiport Module
+
+```bash
+iptables -A INPUT -p tcp -m multiport --dports 22,443,80,3306 -j ACCEPT
+```
+
+🎯 **Explanation:**
+Accepts incoming TCP traffic on multiple ports at once: SSH (22), HTTPS (443), HTTP (80), and MySQL (3306).
+
+---
+
+### 1️⃣2️⃣ Allow Multiple Ports From a Specific Subnet
+
+```bash
+iptables -A INPUT -p tcp -m multiport --dports 22,443,80,3306 -s 192.168.10.0/24 -j ACCEPT
+```
+
+🏠 **Explanation:**
+Allows TCP traffic on ports 22, 443, 80, and 3306 but only if it originates from the subnet `192.168.10.0/24`.
+
+---
+
+### 1️⃣3️⃣ Limit Incoming Connections on Port 80
+
+```bash
+iptables -A INPUT -p tcp --dport 80 -m limit --limit 100/minute --limit-burst 200 -j ACCEPT
+```
+
+🚦 **Explanation:**
+Limits HTTP (port 80) incoming connections to 100 per minute with a burst of 200, helping prevent DoS attacks.
+
+---
+
+### 1️⃣4️⃣ Redirect HTTP Traffic to HTTPS on Interface `ens33`
+
+```bash
+iptables -t nat -A PREROUTING -i ens33 -p tcp --dport 80 -j REDIRECT --to-port 443
+```
+
+🔄 **Explanation:**
+In the `nat` table's PREROUTING chain, this redirects all HTTP traffic (port 80) arriving on interface `ens33` to HTTPS port 443.
+
+## 🎉 Summary
+
+* **iptables** is a powerful Linux firewall tool
+* Works by managing **tables**, **chains**, and **rules**
+* Supports filtering, NAT, packet mangling, and raw processing
+* Persistence through `iptables-persistent` package
+* Flexible commands for network security and traffic control
diff --git a/Security & Networking/Iptables/temp.md b/Security & Networking/Iptables/temp.md
new file mode 100644
index 0000000..f8ab30c
--- /dev/null
+++ b/Security & Networking/Iptables/temp.md	
@@ -0,0 +1,114 @@
+iptable work with net filter
+
+connection type:
+1. new
+2. stablished
+3. Related 
+
+iptable-persitant --> install iptables and save in iptables file 
+
+
+defualt path --> /etc/iptables
+
+command format
+
+```bash
+iptables -t <table-names> <option> <chain-name> <match> -j <action>
+```
+table name: 
+1. filter (default) --> Filtering Packets
+2. nat --> Nating Service
+3. mangel --> Edit Packets
+4. raw --> edit packets before prossecc by os
+
+chains: 
+
+1. filter:
+    1. INPUT
+    2. OUTPUT
+    3. Forward
+2. nat
+    1. OUTPUT
+    2. PREROUTING
+    3. PASTROUTING
+3. mangle
+    1. INPUT
+    2. OUTPUT
+    3. Forward
+    4. PREROUTING
+    5. PASTROUTING
+4. raw
+    1. OUTPUT
+    2. PREROUTIUNG
+
+INPUT : Connection Incomming into Server
+OUTPUT : Packets Outgoiing From server
+FORWARD : Packer incomming to server but the target is not server (routing)
+PREROUTING : EDIT Packets Before Routing 
+PASTROUTING : Edit Packet After Routing And Before Exit From Server
+
+option:
+1. `-A`: Append
+2. `-I`: Insert
+3. `-D`: Delete
+
+actions:
+ACCEPT: accept the packet
+DROP: drop the packer without any msg
+REJECT: drop the packet with send message to packet sender
+LOG: Log The Packet 
+MASQUERADE: Nating
+
+```bash
+iptables-save >> <file_dir>
+```
+
+```bash
+iptables -nL
+```
+```bash
+iptables -t nat -nL
+```
+
+```bash
+iptables -t filter -I INPUT -s 192.168.1.100 -j ACCEPT 
+```
+
+```bash
+iptables -t filter -I INPUT -j DROP 
+```
+
+```bash
+iptables -t filter -A INPUT -j DROP 
+```
+
+```bash
+iptables -A INPUT -p tcp --dport 22 -j ACCEPT
+```
+
+```bash
+iptables -I INPUT -p tcp --dport 22 -j DROP 
+```
+
+```bash
+iptables -A INPUT -p tcp -s 192.168.1.100 -j DROP
+```
+```bash
+iptables -A INPUT -p tcp --dport 443 -j ACCEPT
+```
+
+```bash
+les -A INPUT -p tcp -m multiport --dport 22,443,80,3306 -j ACCEPT
+```
+
+```bash
+iptables -A INPUT -p tcp -m multiport --dport 22,443,80,3306 -d 192.168.10.0/24 -j ACCEPT
+```
+
+```bash
+iptables -A INPUT -p tcp --dport 80 -m limit --limit 100/minute --limit-burst 200 -j ACCEPT
+```
+
+```bash
+iptables -t NAT -A PREROUTING -i ens33 -p tcp --dport 80 -j REDIRECT --to-port 443
+```

From d822d7eb85c63c79ec5537d2cc258b47aff51a61 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Tue, 12 Aug 2025 20:11:35 +0330
Subject: [PATCH 075/116] remove old file

---
 Security & Networking/Iptables/temp.md | 114 -------------------------
 1 file changed, 114 deletions(-)
 delete mode 100644 Security & Networking/Iptables/temp.md

diff --git a/Security & Networking/Iptables/temp.md b/Security & Networking/Iptables/temp.md
deleted file mode 100644
index f8ab30c..0000000
--- a/Security & Networking/Iptables/temp.md	
+++ /dev/null
@@ -1,114 +0,0 @@
-iptable work with net filter
-
-connection type:
-1. new
-2. stablished
-3. Related 
-
-iptable-persitant --> install iptables and save in iptables file 
-
-
-defualt path --> /etc/iptables
-
-command format
-
-```bash
-iptables -t <table-names> <option> <chain-name> <match> -j <action>
-```
-table name: 
-1. filter (default) --> Filtering Packets
-2. nat --> Nating Service
-3. mangel --> Edit Packets
-4. raw --> edit packets before prossecc by os
-
-chains: 
-
-1. filter:
-    1. INPUT
-    2. OUTPUT
-    3. Forward
-2. nat
-    1. OUTPUT
-    2. PREROUTING
-    3. PASTROUTING
-3. mangle
-    1. INPUT
-    2. OUTPUT
-    3. Forward
-    4. PREROUTING
-    5. PASTROUTING
-4. raw
-    1. OUTPUT
-    2. PREROUTIUNG
-
-INPUT : Connection Incomming into Server
-OUTPUT : Packets Outgoiing From server
-FORWARD : Packer incomming to server but the target is not server (routing)
-PREROUTING : EDIT Packets Before Routing 
-PASTROUTING : Edit Packet After Routing And Before Exit From Server
-
-option:
-1. `-A`: Append
-2. `-I`: Insert
-3. `-D`: Delete
-
-actions:
-ACCEPT: accept the packet
-DROP: drop the packer without any msg
-REJECT: drop the packet with send message to packet sender
-LOG: Log The Packet 
-MASQUERADE: Nating
-
-```bash
-iptables-save >> <file_dir>
-```
-
-```bash
-iptables -nL
-```
-```bash
-iptables -t nat -nL
-```
-
-```bash
-iptables -t filter -I INPUT -s 192.168.1.100 -j ACCEPT 
-```
-
-```bash
-iptables -t filter -I INPUT -j DROP 
-```
-
-```bash
-iptables -t filter -A INPUT -j DROP 
-```
-
-```bash
-iptables -A INPUT -p tcp --dport 22 -j ACCEPT
-```
-
-```bash
-iptables -I INPUT -p tcp --dport 22 -j DROP 
-```
-
-```bash
-iptables -A INPUT -p tcp -s 192.168.1.100 -j DROP
-```
-```bash
-iptables -A INPUT -p tcp --dport 443 -j ACCEPT
-```
-
-```bash
-les -A INPUT -p tcp -m multiport --dport 22,443,80,3306 -j ACCEPT
-```
-
-```bash
-iptables -A INPUT -p tcp -m multiport --dport 22,443,80,3306 -d 192.168.10.0/24 -j ACCEPT
-```
-
-```bash
-iptables -A INPUT -p tcp --dport 80 -m limit --limit 100/minute --limit-burst 200 -j ACCEPT
-```
-
-```bash
-iptables -t NAT -A PREROUTING -i ens33 -p tcp --dport 80 -j REDIRECT --to-port 443
-```

From 646ee01febd1eaa059bc6475dd6566a0545d9dfa Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 13 Aug 2025 22:39:51 +0330
Subject: [PATCH 076/116] Certbot doc

---
 Web Servers & Reverse Proxies/CertBot/temp.md | 94 +++++++++++++++++++
 1 file changed, 94 insertions(+)
 create mode 100644 Web Servers & Reverse Proxies/CertBot/temp.md

diff --git a/Web Servers & Reverse Proxies/CertBot/temp.md b/Web Servers & Reverse Proxies/CertBot/temp.md
new file mode 100644
index 0000000..9000c1c
--- /dev/null
+++ b/Web Servers & Reverse Proxies/CertBot/temp.md	
@@ -0,0 +1,94 @@
+# 🔐 Certbot – SSL Certificate Management Guide
+
+## 📦 Install Certbot
+
+```bash
+apt install certbot
+```
+
+Installs **Certbot**, the free tool to automatically obtain and manage SSL/TLS certificates from **Let's Encrypt**.
+
+---
+
+## 🖥️ Method 1 – Standalone Mode
+
+```bash
+certbot certonly --standalone -d www.example.com
+```
+
+💡 **Standalone mode** runs its own temporary web server to complete the verification.
+
+* Use when no web server (Apache/Nginx) is running on the same port.
+* Certificates will be saved in:
+
+  * All versions: `/etc/letsencrypt/archive/`
+  * Latest version (symlink): `/etc/letsencrypt/live/`
+
+---
+
+## 🌐 Method 2 – Webroot Mode
+
+```bash
+certbot certonly --webroot --webroot-path <path> -d <domain>
+```
+
+📌 **Webroot mode** places a verification file in your website's public directory.
+
+* `<path>` = your website's document root (e.g., `/var/www/html`)
+* Use when your site is already running and accessible.
+
+---
+
+## 🛠️ Method 3 – Manual DNS Challenge
+
+```bash
+certbot certonly --manual --preferred-challenges dns -d <domain>
+```
+
+🔹 **DNS mode** requires you to manually add a TXT record to your domain’s DNS.
+
+* Best for **wildcard** certificates (`*.example.com`)
+* Works even without a running web server.
+
+---
+
+## ♻️ Renew Certificates
+
+### Automatic Renewal
+
+```bash
+certbot renew
+```
+
+* Renews all certificates close to expiration.
+
+### Force Renewal
+
+```bash
+certbot renew --force-renewal
+```
+
+* Renews certificates **immediately**, even if not expiring soon.
+
+---
+
+## 📅 Tips
+
+* Certificates expire every **90 days** — always set up **auto-renew**.
+* Test renewal without changes:
+
+```bash
+certbot renew --dry-run
+```
+
+* Restart your web server after renewal to apply new certificates:
+
+```bash
+systemctl restart nginx
+# or
+systemctl restart apache2
+```
+
+---
+
+✨ **With Certbot, your HTTPS setup can be fast, free, and automatic!** 🔒🚀

From 6280c427ed9add619e42491c31b906ce20b679e4 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 13 Aug 2025 22:42:51 +0330
Subject: [PATCH 077/116] update nginx

---
 .../CertBot/{temp.md => certbot.md}           |  0
 Web Servers & Reverse Proxies/Nginx/7-ssl.md  | 56 ++++++++++++++
 Web Servers & Reverse Proxies/Nginx/8-auth.md | 75 +++++++++++++++++++
 3 files changed, 131 insertions(+)
 rename Web Servers & Reverse Proxies/CertBot/{temp.md => certbot.md} (100%)
 create mode 100644 Web Servers & Reverse Proxies/Nginx/7-ssl.md
 create mode 100644 Web Servers & Reverse Proxies/Nginx/8-auth.md

diff --git a/Web Servers & Reverse Proxies/CertBot/temp.md b/Web Servers & Reverse Proxies/CertBot/certbot.md
similarity index 100%
rename from Web Servers & Reverse Proxies/CertBot/temp.md
rename to Web Servers & Reverse Proxies/CertBot/certbot.md
diff --git a/Web Servers & Reverse Proxies/Nginx/7-ssl.md b/Web Servers & Reverse Proxies/Nginx/7-ssl.md
new file mode 100644
index 0000000..2ef56c7
--- /dev/null
+++ b/Web Servers & Reverse Proxies/Nginx/7-ssl.md	
@@ -0,0 +1,56 @@
+# 🔐 Nginx SSL Configuration Guide
+
+## 📄 Example Server Block (HTTPS)
+
+```nginx
+listen 443 ssl;
+server_name example.com www.example.com;
+
+# 🔒 SSL Certificate (Generated by Certbot)
+ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; 
+ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; 
+
+# 📂 Website Root
+root /var/www/example.com/html;
+index index.html;
+
+# 🚦 Request Handling
+location / {
+    try_files $uri $uri/ =404;
+}
+```
+
+---
+
+## 🗂️ What Each Part Does
+
+| Directive                    | Meaning                                                |
+| ---------------------------- | ------------------------------------------------------ |
+| `listen 443 ssl;`            | Listens on port **443** for secure HTTPS traffic.      |
+| `server_name`                | Specifies the domain(s) for this site.                 |
+| `ssl_certificate`            | The **full certificate chain** file from Certbot.      |
+| `ssl_certificate_key`        | The **private key** file from Certbot.                 |
+| `root`                       | Directory containing your website’s files.             |
+| `index`                      | Default file served for a directory request.           |
+| `try_files $uri $uri/ =404;` | Checks if a file/directory exists, else returns a 404. |
+
+---
+
+## ⚠️ SSL Notes
+
+* Certbot certificates are stored here:
+
+  ```
+  /etc/letsencrypt/live/<your-domain>/
+  ```
+* Certificates **expire every 90 days** — set up auto-renew:
+
+  ```bash
+  certbot renew --quiet
+  ```
+* After renewal, always reload Nginx to apply changes:
+
+  ```bash
+  systemctl reload nginx
+  ```
+
diff --git a/Web Servers & Reverse Proxies/Nginx/8-auth.md b/Web Servers & Reverse Proxies/Nginx/8-auth.md
new file mode 100644
index 0000000..2f70f27
--- /dev/null
+++ b/Web Servers & Reverse Proxies/Nginx/8-auth.md	
@@ -0,0 +1,75 @@
+# 🔐🔑 Nginx SSL with HTTP Basic Authentication
+
+## 📄 Example Secure Server Block (HTTPS + Password Protection)
+
+```nginx
+listen 443 ssl;
+server_name example.com www.example.com;
+
+# 🔒 SSL Certificates (Generated by Certbot)
+ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; 
+ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; 
+
+# 📂 Website Root
+root /var/www/example.com/html;
+index index.html;
+
+# 🔑 Password-Protected Location
+location / {
+    auth_basic "Admin";
+    auth_basic_user_file /etc/nginx/.htpasswd;
+    try_files $uri $uri/ =404;
+}
+```
+
+---
+
+## 🗂️ Explanation of Key Parts
+
+| Directive              | Purpose                                                             |
+| ---------------------- | ------------------------------------------------------------------- |
+| `auth_basic "Admin";`  | Enables **HTTP Basic Authentication** with prompt title “Admin”.    |
+| `auth_basic_user_file` | Points to the `.htpasswd` file containing username/password hashes. |
+| `.htpasswd` file       | Stores encrypted credentials — created using `htpasswd` command.    |
+| SSL lines              | Load the certificate and private key from **Certbot**.              |
+
+---
+
+## 🛠️ How to Set Up Password Protection
+
+### 1️⃣ Install `apache2-utils` (for `htpasswd` tool)
+
+```bash
+apt install apache2-utils
+```
+
+### 2️⃣ Create the `.htpasswd` File
+
+```bash
+htpasswd -c /etc/nginx/.htpasswd <username>
+```
+
+* `-c` creates a **new file** (omit `-c` if adding more users).
+* You’ll be prompted to set a password.
+
+### 3️⃣ Adjust File Permissions
+
+```bash
+chmod 640 /etc/nginx/.htpasswd
+chown root:www-data /etc/nginx/.htpasswd
+```
+
+### 4️⃣ Test and Reload Nginx
+
+```bash
+nginx -t
+systemctl reload nginx
+```
+
+---
+
+## ⚠️ Security Notes
+
+* Always store `.htpasswd` **outside** your web root.
+* Passwords in `.htpasswd` are hashed, but still protect the file with correct permissions.
+* Works best for **admin panels**, **staging sites**, or private areas.

From 1bc79e6f58c841b6f128aeb3f7369c1c0d0d7662 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Wed, 13 Aug 2025 22:58:36 +0330
Subject: [PATCH 078/116] Treafik Information Doc

---
 .../Traefik/1-Information.md                  | 83 +++++++++++++++++++
 1 file changed, 83 insertions(+)
 create mode 100644 Web Servers & Reverse Proxies/Traefik/1-Information.md

diff --git a/Web Servers & Reverse Proxies/Traefik/1-Information.md b/Web Servers & Reverse Proxies/Traefik/1-Information.md
new file mode 100644
index 0000000..4f2c538
--- /dev/null
+++ b/Web Servers & Reverse Proxies/Traefik/1-Information.md	
@@ -0,0 +1,83 @@
+# 🚦 **Traefik Overview**
+
+**Traefik** is a **modern reverse proxy** and load balancer that makes deploying, securing, and managing microservices easier.
+
+---
+
+## 🔄 **Core Concepts**
+
+### 1️⃣ **Entrypoint** 🛬
+
+* The starting point for **incoming requests**.
+* Example: `:80` for HTTP or `:443` for HTTPS.
+
+### 2️⃣ **Router** 🚏
+
+* Decides **where a request should go** based on rules.
+* Connects **entrypoints** to **services**.
+
+### 3️⃣ **Service** 🛠️
+
+* The actual application or backend that processes the request.
+
+---
+
+## 🧩 **Routers Details**
+
+**Routers** can have:
+
+1. **Middleware** 🧱
+
+   * Modify requests/responses before reaching the service.
+   * Examples:
+
+     * `StripPrefix` ➡️ Remove part of the URL path.
+     * `RateLimit` ➡️ Limit request rate.
+     * `Auth` ➡️ Add authentication.
+
+2. **Rules** 📜
+
+   * Define **how to match a request**.
+   * Examples:
+
+     * `Host("example.com")`
+     * `PathPrefix("/api")`
+
+---
+
+## ⚙️ **Traefik Configuration Types**
+
+1. **Static Configuration** 🗂️
+
+   * Defines **Traefik’s own behavior**.
+   * Example: entrypoints, providers, log level.
+   * Set in `traefik.yml` or CLI args.
+
+2. **Dynamic Configuration** 📡
+
+   * Defines **how Traefik routes requests**.
+   * Example: routers, services, middlewares.
+   * Comes from files, Kubernetes CRDs, or Docker labels.
+
+---
+
+## 🔗 **Request Flow**
+
+```
+Request  
+   ⬇️  
+ Entrypoint 🛬  
+   ⬇️  
+ Router 🚏  
+   ⬇️  
+ Middleware 1 🧱 → Middleware 2 🧱  
+   ⬇️  
+ Service 🛠️  
+```
+
+---
+
+## 🌟 **Summary**
+
+Traefik acts like a **smart traffic cop** 🚓 for your microservices, ensuring that requests go exactly where they should, with the right rules and transformations applied along the way.
+

From 5437d96e3441a099a25dbc190ea1bf8641351c87 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Thu, 28 Aug 2025 14:16:32 +0330
Subject: [PATCH 079/116] Vaultwarden Doc

---
 Password Manager/Vaultwarden/Setup.md         | 114 ++++++++++++++++++
 .../Traefik/1-Information.md                  |  83 -------------
 2 files changed, 114 insertions(+), 83 deletions(-)
 create mode 100644 Password Manager/Vaultwarden/Setup.md
 delete mode 100644 Web Servers & Reverse Proxies/Traefik/1-Information.md

diff --git a/Password Manager/Vaultwarden/Setup.md b/Password Manager/Vaultwarden/Setup.md
new file mode 100644
index 0000000..76428ad
--- /dev/null
+++ b/Password Manager/Vaultwarden/Setup.md	
@@ -0,0 +1,114 @@
+# 🚀 Vaultwarden Setup Guide (with Docker & Nginx SSL)
+
+This guide walks you through deploying Vaultwarden (a lightweight Bitwarden server alternative) using Docker Compose, Nginx as a reverse proxy, and a self-signed SSL certificate for secure HTTPS access.
+
+---
+
+## 📦 Step 1: Docker Compose Configuration
+
+Create a file named docker-compose.yml with the following content:
+
+services:
+  vaultwarden:
+    image: vaultwarden/server:latest
+    container_name: vaultwarden
+    restart: unless-stopped
+    environment:
+      DOMAIN: "https://<your-domain>"
+      ADMIN_TOKEN: "<ADMIN_TOKEN>"
+    volumes:
+      - ./vw-data/:/data/
+    ports:
+      - 8000:80
+
+  nginx:
+    image: nginx:alpine
+    container_name: nginx
+    restart: unless-stopped
+    volumes:
+      - ./nginx-config:/etc/nginx/conf.d
+      - ./nginx-certs/vault.local.key:/etc/ssl/private/vault.local.key
+      - ./nginx-certs/vault.local.crt:/etc/ssl/certs/vault.local.crt
+    ports:
+      - 80:80
+      - 443:443
+
+
+🔹 Notes:
+- Vaultwarden runs on port 8000 internally (proxied by Nginx).  
+- Persistent data is stored in ./vw-data/.  
+- Replace DOMAIN and ADMIN_TOKEN with your values.  
+
+---
+
+## 🌐 Step 2: Nginx Reverse Proxy Configuration
+
+Inside your nginx-config directory, create a file named vaultwarden.conf with:
+
+server {
+    listen 443 ssl;
+    server_name domain_name;
+
+    ssl_certificate     /etc/ssl/certs/vault.local.crt;
+    ssl_certificate_key /etc/ssl/private/vault.local.key;
+
+    location / {
+        proxy_pass http://vaultwarden:80;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+}
+
+
+🔹 This configuration:  
+- Forces HTTPS on your domain.  
+- Proxies requests to the Vaultwarden container.  
+
+---
+
+## 🔐 Step 3: Generate a Self-Signed SSL Certificate
+
+If you don’t already have an SSL certificate, generate one for local testing:
+
+openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
+-keyout ./nginx-certs/vault.local.key \
+-out ./nginx-certs/vault.local.crt
+
+
+🔹 Fill in the required details (CN should match domain_name).  
+🔹 Place the generated files inside ./nginx-certs/.  
+
+---
+
+## ▶️ Step 4: Start the Services
+
+Run:
+
+docker compose up -d
+
+
+Check containers:
+
+docker ps
+
+
+- Vaultwarden should be running on port 8000 internally.  
+- Nginx should be serving HTTPS on https://domain_name.  
+
+---
+
+## ✅ Step 5: Access Vaultwarden
+
+- Open: https://domain_name  
+- Admin portal: https://domain_name/admin (use your ADMIN_TOKEN)  
+
+---
+
+## 🎯 Summary
+
+You now have:
+- Vaultwarden running in Docker.  
+- Nginx reverse proxy with HTTPS enabled.  
+- Secure, self-hosted password manager ready for use.
diff --git a/Web Servers & Reverse Proxies/Traefik/1-Information.md b/Web Servers & Reverse Proxies/Traefik/1-Information.md
deleted file mode 100644
index 4f2c538..0000000
--- a/Web Servers & Reverse Proxies/Traefik/1-Information.md	
+++ /dev/null
@@ -1,83 +0,0 @@
-# 🚦 **Traefik Overview**
-
-**Traefik** is a **modern reverse proxy** and load balancer that makes deploying, securing, and managing microservices easier.
-
----
-
-## 🔄 **Core Concepts**
-
-### 1️⃣ **Entrypoint** 🛬
-
-* The starting point for **incoming requests**.
-* Example: `:80` for HTTP or `:443` for HTTPS.
-
-### 2️⃣ **Router** 🚏
-
-* Decides **where a request should go** based on rules.
-* Connects **entrypoints** to **services**.
-
-### 3️⃣ **Service** 🛠️
-
-* The actual application or backend that processes the request.
-
----
-
-## 🧩 **Routers Details**
-
-**Routers** can have:
-
-1. **Middleware** 🧱
-
-   * Modify requests/responses before reaching the service.
-   * Examples:
-
-     * `StripPrefix` ➡️ Remove part of the URL path.
-     * `RateLimit` ➡️ Limit request rate.
-     * `Auth` ➡️ Add authentication.
-
-2. **Rules** 📜
-
-   * Define **how to match a request**.
-   * Examples:
-
-     * `Host("example.com")`
-     * `PathPrefix("/api")`
-
----
-
-## ⚙️ **Traefik Configuration Types**
-
-1. **Static Configuration** 🗂️
-
-   * Defines **Traefik’s own behavior**.
-   * Example: entrypoints, providers, log level.
-   * Set in `traefik.yml` or CLI args.
-
-2. **Dynamic Configuration** 📡
-
-   * Defines **how Traefik routes requests**.
-   * Example: routers, services, middlewares.
-   * Comes from files, Kubernetes CRDs, or Docker labels.
-
----
-
-## 🔗 **Request Flow**
-
-```
-Request  
-   ⬇️  
- Entrypoint 🛬  
-   ⬇️  
- Router 🚏  
-   ⬇️  
- Middleware 1 🧱 → Middleware 2 🧱  
-   ⬇️  
- Service 🛠️  
-```
-
----
-
-## 🌟 **Summary**
-
-Traefik acts like a **smart traffic cop** 🚓 for your microservices, ensuring that requests go exactly where they should, with the right rules and transformations applied along the way.
-

From dccb881589448e5a96949f0afbf85f034612f135 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Fri, 5 Sep 2025 13:49:18 +0330
Subject: [PATCH 080/116] screen command

---
 Terminal Multiplexers/screen.md | 60 +++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)
 create mode 100644 Terminal Multiplexers/screen.md

diff --git a/Terminal Multiplexers/screen.md b/Terminal Multiplexers/screen.md
new file mode 100644
index 0000000..b6b7b67
--- /dev/null
+++ b/Terminal Multiplexers/screen.md	
@@ -0,0 +1,60 @@
+# 🖥️ Mastering `screen` (Terminal Multiplexer)
+
+`screen` is a **terminal multiplexer**. It allows you to:
+
+✨ Start a terminal session that stays alive even if you disconnect.
+✨ Run multiple shell sessions inside a single terminal.
+✨ Detach and reattach to sessions later.
+
+---
+
+## 🚀 Basic Commands
+
+### ▶️ Create a new shell
+
+```bash
+screen
+```
+
+### 📝 Create a new shell with a specific name
+
+```bash
+screen -S session_name
+```
+
+### 📜 Show all active sessions
+
+```bash
+screen -ls
+```
+
+### 🔗 Reattach to a session
+
+```bash
+screen -r session_name
+```
+
+---
+
+## 🛑 Closing Sessions
+
+### ❌ Exit a session (from inside)
+
+```bash
+exit
+```
+
+### 💣 Kill a specific session
+
+```bash
+screen -X -S session_name quit
+```
+
+---
+
+## 🌟 Pro Tips
+
+* You can **detach** from a session with `Ctrl + A` then `D`.
+* Sessions keep running even if you **log out or disconnect**.
+* Great for **long-running processes** (e.g., servers, builds, SSH tasks).
+

From 772263d985e56276d94b1755dd63c1fb67752071 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Fri, 5 Sep 2025 23:36:38 +0330
Subject: [PATCH 081/116] change terminal doc into linux dir

---
 {Terminal Multiplexers => Linux/Terminal Multiplexers}/screen.md | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename {Terminal Multiplexers => Linux/Terminal Multiplexers}/screen.md (100%)

diff --git a/Terminal Multiplexers/screen.md b/Linux/Terminal Multiplexers/screen.md
similarity index 100%
rename from Terminal Multiplexers/screen.md
rename to Linux/Terminal Multiplexers/screen.md

From 5e4859050ae4c6cbcf0ff69f5f30723a72827d8e Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Sat, 6 Sep 2025 00:09:52 +0330
Subject: [PATCH 082/116] rsync command

---
 Linux/File Copy & Synchronization/rsync.md | 131 +++++++++++++++++++++
 1 file changed, 131 insertions(+)
 create mode 100644 Linux/File Copy & Synchronization/rsync.md

diff --git a/Linux/File Copy & Synchronization/rsync.md b/Linux/File Copy & Synchronization/rsync.md
new file mode 100644
index 0000000..72ecd4e
--- /dev/null
+++ b/Linux/File Copy & Synchronization/rsync.md	
@@ -0,0 +1,131 @@
+# 🔄 Rsync
+
+`rsync` is a powerful command-line tool for syncing files and directories between systems over SSH.
+Here are some useful commands 👇
+
+---
+
+## 📌 Basic Syntax
+
+```bash
+rsync [options] <file_or_dir> <user>@<host>:<target-dir>
+```
+
+or
+
+```bash
+rsync [options] <user>@<host>:<source-dir_or_file> <target-dir>
+```
+
+---
+
+## 📥 Copy from Local ➝ Remote
+
+```bash
+rsync file1.txt radin@192.168.1.10:/home/radin
+```
+
+Verbose mode (shows details):
+
+```bash
+rsync -v file1.txt radin@192.168.1.10:/home/radin
+```
+
+---
+
+## 📤 Copy from Remote ➝ Local
+
+```bash
+rsync -v radin@192.168.1.10:/home/radin/file1.txt /opt
+```
+
+---
+
+## 📦 Archiving
+
+Archive mode (preserves permissions, symlinks, etc.):
+
+```bash
+rsync -va file1.txt radin@192.168.1.10:/home/radin
+```
+
+Archive + compress (gzip):
+
+```bash
+rsync -vaz file1.txt radin@192.168.1.10:/home/radin
+```
+
+With progress bar:
+
+```bash
+rsync -vaz --progress file1.txt radin@192.168.1.10:/home/radin
+```
+
+---
+
+## 🔐 Custom SSH Port
+
+```bash
+rsync -e 'ssh -p 8090' -vaz file1.txt radin@192.168.1.10:/home/radin
+```
+
+---
+
+## 🗑️ Sync with Delete (mirror directories)
+
+Deletes files on destination that don’t exist on source:
+
+```bash
+rsync -vaz --delete dir_test/ radin@192.168.1.10:/home/radin
+```
+
+---
+
+## 🚫 Excluding Files
+
+Exclude `.img` files:
+
+```bash
+rsync -va dir_test/ --exclude '*.img' radin@192.168.1.10:/home/radin
+```
+
+---
+
+## ⚡ Bandwidth Control
+
+Limit transfer speed (in KB/s):
+
+```bash
+rsync -v --bwlimit=2048 file1.txt radin@192.168.1.10:/home/radin
+```
+
+---
+
+## 🧹 Move Instead of Copy
+
+Remove source file after transfer:
+
+```bash
+rsync -v --remove-source-file file1.txt radin@192.168.1.10:/home/radin
+```
+
+---
+
+## ⛔ Ignore Existing Files
+
+Skip already existing files:
+
+```bash
+rsync -v --ignore-existing file1.txt radin@192.168.1.10:/home/radin
+```
+
+---
+
+## 🧹⛔ Combine Options
+
+Remove source + ignore existing:
+
+```bash
+rsync -v --remove-source-file --ignore-existing file1.txt radin@192.168.1.10:/home/radin
+```
+

From 93e99238109fafe237b0e76324c873781e4df653 Mon Sep 17 00:00:00 2001
From: Radin Pirouz <r.pirouz@azkivam.com>
Date: Mon, 8 Sep 2025 10:28:45 +0330
Subject: [PATCH 083/116] added s5cmd doc

---
 Storage/S5CMD/main.md | 94 +++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 94 insertions(+)
 create mode 100644 Storage/S5CMD/main.md

diff --git a/Storage/S5CMD/main.md b/Storage/S5CMD/main.md
new file mode 100644
index 0000000..89103ac
--- /dev/null
+++ b/Storage/S5CMD/main.md
@@ -0,0 +1,94 @@
+# 📘 S5CMD Reference Guide
+
+`s5cmd` is a fast and efficient S3 and local filesystem command-line tool optimized for large-scale data operations.
+
+---
+
+## 🔹 Command Syntax
+
+```bash
+s5cmd [global options] <command> [command options] [arguments...]
+```
+
+---
+
+## ⚙️ Global Options
+
+| Option                  | Description                                    |
+| ----------------------- | ---------------------------------------------- |
+| `--aws-profile string`  | AWS profile to use                             |
+| `--endpoint-url string` | Custom S3 endpoint                             |
+| `--no-sign-request`     | Do not sign requests (for public buckets)      |
+| `--numworkers int`      | Number of parallel workers (**default: 256**)  |
+| `--retry-count int`     | Number of retries for failed requests          |
+| `--json`                | Output logs in JSON format                     |
+| `--log string`          | Log level: `info`, `warning`, `error`, `debug` |
+| `--dry-run`             | Show operations without executing              |
+
+---
+
+## 📂 Common Commands
+
+### 🔍 List Buckets/Objects
+
+```bash
+s5cmd ls s3://bucket_2/
+```
+
+### 🪣 Bucket Management
+
+```bash
+s5cmd mb s3://new-bucket       # Create bucket
+s5cmd rb s3://bucket-name      # Remove bucket
+```
+
+### 📤 Upload Files
+
+```bash
+s5cmd cp local.txt s3://bucket/file.txt
+```
+
+### 📥 Download Files
+
+```bash
+s5cmd cp s3://bucket/file.txt ./local.txt
+s5cmd cp s3://bucket/*.jpg ./photos/
+```
+
+### 🔀 Move/Rename Files
+
+```bash
+s5cmd mv s3://bucket/old.txt s3://bucket/new.txt
+```
+
+### 🗑️ Remove Files
+
+```bash
+s5cmd rm s3://bucket/file.txt
+s5cmd rm --all-versions s3://bucket/file.txt
+```
+
+### 🔄 Synchronization
+
+```bash
+s5cmd sync ./localdir/ s3://bucket/targetdir/
+s5cmd sync s3://bucket/targetdir/ ./localdir/
+```
+
+### 📖 Read File Content
+
+```bash
+s5cmd cat s3://bucket/file.txt
+```
+
+### 📊 Disk Usage
+
+```bash
+s5cmd du s3://bucket/*
+```
+
+### 🔎 Query with S3 Select
+
+```bash
+s5cmd select "select * from s3object s limit 10" s3://bucket/data.csv
+```

From 238e8affa07a700848f60bf8d6d592b911bd9be0 Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Sat, 20 Sep 2025 16:58:22 +0330
Subject: [PATCH 084/116] Update main.md

---
 Storage/S5CMD/main.md | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/Storage/S5CMD/main.md b/Storage/S5CMD/main.md
index 89103ac..6990fd6 100644
--- a/Storage/S5CMD/main.md
+++ b/Storage/S5CMD/main.md
@@ -1,10 +1,10 @@
-# 📘 S5CMD Reference Guide
+# S5CMD Reference Guide
 
 `s5cmd` is a fast and efficient S3 and local filesystem command-line tool optimized for large-scale data operations.
 
 ---
 
-## 🔹 Command Syntax
+## Command Syntax
 
 ```bash
 s5cmd [global options] <command> [command options] [arguments...]
@@ -12,7 +12,7 @@ s5cmd [global options] <command> [command options] [arguments...]
 
 ---
 
-## ⚙️ Global Options
+## Global Options
 
 | Option                  | Description                                    |
 | ----------------------- | ---------------------------------------------- |
@@ -27,67 +27,67 @@ s5cmd [global options] <command> [command options] [arguments...]
 
 ---
 
-## 📂 Common Commands
+## Common Commands
 
-### 🔍 List Buckets/Objects
+### List Buckets/Objects
 
 ```bash
 s5cmd ls s3://bucket_2/
 ```
 
-### 🪣 Bucket Management
+### Bucket Management
 
 ```bash
 s5cmd mb s3://new-bucket       # Create bucket
 s5cmd rb s3://bucket-name      # Remove bucket
 ```
 
-### 📤 Upload Files
+### Upload Files
 
 ```bash
 s5cmd cp local.txt s3://bucket/file.txt
 ```
 
-### 📥 Download Files
+### Download Files
 
 ```bash
 s5cmd cp s3://bucket/file.txt ./local.txt
 s5cmd cp s3://bucket/*.jpg ./photos/
 ```
 
-### 🔀 Move/Rename Files
+### Move/Rename Files
 
 ```bash
 s5cmd mv s3://bucket/old.txt s3://bucket/new.txt
 ```
 
-### 🗑️ Remove Files
+### Remove Files
 
 ```bash
 s5cmd rm s3://bucket/file.txt
 s5cmd rm --all-versions s3://bucket/file.txt
 ```
 
-### 🔄 Synchronization
+### Synchronization
 
 ```bash
 s5cmd sync ./localdir/ s3://bucket/targetdir/
 s5cmd sync s3://bucket/targetdir/ ./localdir/
 ```
 
-### 📖 Read File Content
+### Read File Content
 
 ```bash
 s5cmd cat s3://bucket/file.txt
 ```
 
-### 📊 Disk Usage
+### Disk Usage
 
 ```bash
 s5cmd du s3://bucket/*
 ```
 
-### 🔎 Query with S3 Select
+### Query with S3 Select
 
 ```bash
 s5cmd select "select * from s3object s limit 10" s3://bucket/data.csv

From c215d6f03ef89dba767bd0c87385d0757189f579 Mon Sep 17 00:00:00 2001
From: Radin Pirouz <r.pirouz@azkivam.com>
Date: Tue, 23 Sep 2025 12:26:50 +0330
Subject: [PATCH 085/116] added minio client doc

---
 Storage/Minio/Client/basic.md | 184 ++++++++++++++++++++++++++++++++++
 1 file changed, 184 insertions(+)
 create mode 100644 Storage/Minio/Client/basic.md

diff --git a/Storage/Minio/Client/basic.md b/Storage/Minio/Client/basic.md
new file mode 100644
index 0000000..20ba600
--- /dev/null
+++ b/Storage/Minio/Client/basic.md
@@ -0,0 +1,184 @@
+
+The **MinIO Client (`mc`)** provides a modern alternative to UNIX commands for interacting with S3-compatible object storage.
+This guide summarizes commonly used commands.
+
+---
+
+## Aliases (`mc alias`)
+
+Aliases are used to manage S3 server connections.
+
+* **List all aliases:**
+
+```bash
+mc alias ls
+```
+
+* **List a specific alias:**
+
+```bash
+mc alias ls <mc-server>
+```
+
+* **Remove an alias:**
+
+```bash
+mc alias rm <mc-server>
+```
+
+* **Set a new alias:**
+
+```bash
+mc alias set <object-storage-name> <url> <access-key> <secret-key> --api <s3-version>
+```
+
+* **Export alias to JSON:**
+
+```bash
+mc alias export <mc-server> | tee object-st.json
+```
+
+* **Import alias from JSON:**
+
+```bash
+mc alias import <object-storage-name> <json-file>
+```
+
+---
+
+## Listing Objects (`mc ls`)
+
+* **List bucket contents:**
+
+```bash
+mc ls <mc-server>/<bucket>/<dir>/
+```
+
+* **List with versions:**
+
+```bash
+mc ls --versions <mc-server>/<bucket>/<dir>/
+```
+
+---
+
+## Copying Files (`mc cp`)
+
+* **Upload file to bucket:**
+
+```bash
+mc cp <file-onlocal> <mc-server>/<bucket>/<dir>/
+```
+
+* **Download file from bucket:**
+
+```bash
+mc cp <mc-server>/<bucket>/<dir> <file-onlocal>
+```
+
+* **Download specific version:**
+
+```bash
+mc cp --version-id <version-uuid> <mc-server>/<bucket>/<dir> <file-onlocal>
+```
+
+---
+
+## Viewing Files (`mc cat`)
+
+* **View file contents:**
+
+```bash
+mc cat <mc-server>/<bucket>/<dir>
+```
+
+---
+
+## Moving Files (`mc mv`)
+
+* **Move from local to bucket:**
+
+```bash
+mc mv <file-onlocal> <mc-server>/<bucket>/<dir>/
+```
+
+* **Move specific version from bucket:**
+
+```bash
+mc mv --version-id <version-uuid> <mc-server>/<bucket>/<dir> <file-onlocal>
+```
+
+---
+
+## Removing Files (`mc rm`)
+
+* **Remove file:**
+
+```bash
+mc rm <mc-server>/<bucket>/<dir>/file
+```
+
+* **Force remove specific version:**
+
+```bash
+mc rm --force --version-id <version-uuid> <mc-server>/<bucket>/<dir>/file
+```
+
+---
+
+## Creating Buckets (`mc mb`)
+
+* **Create a bucket:**
+
+```bash
+mc mb <mc-server>/<bucket-name>
+```
+
+* **Create a bucket with versioning:**
+
+```bash
+mc mb --with-versioning <mc-server>/<bucket-name>
+```
+
+* **Create a bucket with object lock:**
+
+```bash
+mc mb --with-lock <mc-server>/<bucket-name>
+```
+
+---
+
+## Removing Buckets (`mc rb`)
+
+* **Remove a bucket:**
+
+```bash
+mc rb <mc-server>/<bucket-name>
+```
+
+* **Force remove a bucket:**
+
+```bash
+mc rb --force <mc-server>/<bucket-name>
+```
+
+---
+
+## Health Check (`mc ping`)
+
+* **Ping a server:**
+
+```bash
+mc ping <mc-server> --count <count-of-ping>
+```
+
+---
+
+## Tree View (`mc tree`)
+
+* **Display bucket tree structure:**
+
+```bash
+mc tree <mc-server>/<bucket>
+```
+

From 9effa6381b66f33bedf61c08e64df292e3a4a3ad Mon Sep 17 00:00:00 2001
From: Radin Pirouz <r.pirouz@azkivam.com>
Date: Tue, 23 Sep 2025 13:06:26 +0330
Subject: [PATCH 086/116] mc admin : access key

---
 Storage/Minio/Admin/01-accesskey.md | 90 +++++++++++++++++++++++++++++
 Storage/Minio/Admin/02-user.md      |  0
 2 files changed, 90 insertions(+)
 create mode 100644 Storage/Minio/Admin/01-accesskey.md
 create mode 100644 Storage/Minio/Admin/02-user.md

diff --git a/Storage/Minio/Admin/01-accesskey.md b/Storage/Minio/Admin/01-accesskey.md
new file mode 100644
index 0000000..7614836
--- /dev/null
+++ b/Storage/Minio/Admin/01-accesskey.md
@@ -0,0 +1,90 @@
+# MinIO Admin: Access Key Management (`mc admin accesskey`)
+
+The **`mc admin accesskey`** command set is used to manage users and access keys on a MinIO server.
+
+---
+
+## Listing Access Keys
+
+* **List all access keys:**
+
+```bash
+mc admin accesskey ls
+```
+
+* **List access keys for a specific user:**
+
+```bash
+mc admin accesskey ls <user>
+```
+
+---
+
+## Creating Access Keys
+
+* **Create a new access key with default settings:**
+
+```bash
+mc admin accesskey create <mc-server>
+```
+
+* **Create a new access key with custom access and secret keys:**
+
+```bash
+mc admin accesskey create <mc-server> --access-key <custom-access> --secret-key <custom-secret>
+```
+
+* **Create a user with temporary expiry duration (e.g., 24 hours):**
+
+```bash
+mc admin accesskey create <mc-server> miniouser --expiry-duration 24h
+```
+
+* **Create a user with a specific expiry date:**
+
+```bash
+mc admin accesskey create <mc-server> --expiry 2026-01-15
+```
+
+* **Create a user with expiry date and custom policy:**
+
+```bash
+mc admin accesskey create <mc-server> --expiry 2026-01-15 --policy /path/to/policy.json
+```
+
+---
+
+## Enabling and Disabling Access Keys
+
+* **Disable an access key:**
+
+```bash
+mc admin accesskey disable <mc-server> <access-key>
+```
+
+* **Enable a disabled access key:**
+
+```bash
+mc admin accesskey enable <mc-server> <access-key>
+```
+
+---
+
+## Access Key Information
+
+* **Get detailed info about an access key:**
+
+```bash
+mc admin accesskey info <mc-server> <access-key>
+```
+
+---
+
+## Removing Access Keys
+
+* **Remove an access key:**
+
+```bash
+mc admin accesskey rm <mc-server> <access-key>
+```
+
diff --git a/Storage/Minio/Admin/02-user.md b/Storage/Minio/Admin/02-user.md
new file mode 100644
index 0000000..e69de29

From 2a1a283de6c0d5baaa6e18aa87f0c31cccbef612 Mon Sep 17 00:00:00 2001
From: Radin Pirouz <r.pirouz@azkivam.com>
Date: Tue, 23 Sep 2025 14:36:14 +0330
Subject: [PATCH 087/116] mc admin: user commands

---
 Storage/Minio/Admin/02-user.md | 55 ++++++++++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)

diff --git a/Storage/Minio/Admin/02-user.md b/Storage/Minio/Admin/02-user.md
index e69de29..c33922e 100644
--- a/Storage/Minio/Admin/02-user.md
+++ b/Storage/Minio/Admin/02-user.md
@@ -0,0 +1,55 @@
+# MinIO Admin: User Management (`mc admin user`)
+
+The **`mc admin user`** command set is used to manage users on a MinIO server.
+
+---
+
+## Listing Users
+
+* **List all users on a server:**
+
+```bash
+mc admin user ls <mc-server>
+```
+
+* **Get detailed info about a specific user:**
+
+```bash
+mc admin user info <mc-server> <user>
+```
+
+---
+
+## Adding Users
+
+* **Add a new user with a secret key:**
+
+```bash
+mc admin user add <mc-server> <newuser> <newusersecret>
+```
+
+---
+
+## Removing Users
+
+* **Remove an existing user:**
+
+```bash
+mc admin user rm <mc-server> <user>
+```
+
+---
+
+## Enabling and Disabling Users
+
+* **Disable a user:**
+
+```bash
+mc admin user disable <mc-server> <user>
+```
+
+* **Enable a previously disabled user:**
+
+```bash
+mc admin user enable <mc-server> <user>
+```

From 08d446ef82f551da625ad368687b5ea6d07e3f69 Mon Sep 17 00:00:00 2001
From: Radin Pirouz <r.pirouz@azkivam.com>
Date: Tue, 23 Sep 2025 16:04:13 +0330
Subject: [PATCH 088/116] mc admin: replication (site to site)

---
 Storage/Minio/Admin/03.replication.md | 58 +++++++++++++++++++++++++++
 1 file changed, 58 insertions(+)
 create mode 100644 Storage/Minio/Admin/03.replication.md

diff --git a/Storage/Minio/Admin/03.replication.md b/Storage/Minio/Admin/03.replication.md
new file mode 100644
index 0000000..07febe5
--- /dev/null
+++ b/Storage/Minio/Admin/03.replication.md
@@ -0,0 +1,58 @@
+# MinIO Admin: Site-to-Site Replication 
+
+The **`mc admin replication`** and **`mc admin replicate`** commands manage replication between MinIO servers.
+
+---
+
+## Checking Replication
+
+* **Get replication configuration info:**
+
+```bash
+mc admin replication info <mc-server>
+```
+
+* **Check replication status:**
+
+```bash
+mc admin replication status <mc-server>
+```
+
+---
+
+## Adding Replication
+
+* **Add a replication between servers (default mode):**
+
+```bash
+mc admin replicate add <mc-server1> <mc-server2> <mc-server3>
+```
+
+* **Add replication in synchronous mode:**
+
+```bash
+mc admin replicate add <mc-server1> <mc-server2> <mc-server3> --mode sync
+```
+
+* **Add replication in asynchronous mode:**
+
+```bash
+mc admin replicate add <mc-server1> <mc-server2> <mc-server3> --mode async
+```
+
+---
+
+## Removing Replication
+
+* **Remove all replication rules on a server:**
+
+```bash
+mc admin replication rm <mc-server1> --all --force
+```
+
+* **Remove specific replication between servers:**
+
+```bash
+mc admin replication rm <mc-server1> <mc-server2> <mc-server3> --force
+```
+

From 20a622d87e0c60fca3205cdbdb70926af9d2f38a Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Fri, 26 Sep 2025 23:20:31 +0330
Subject: [PATCH 089/116] nginx rate limit

---
 .../Nginx/9-ratelimit.md                      | 134 ++++++++++++++++++
 1 file changed, 134 insertions(+)
 create mode 100644 Web Servers & Reverse Proxies/Nginx/9-ratelimit.md

diff --git a/Web Servers & Reverse Proxies/Nginx/9-ratelimit.md b/Web Servers & Reverse Proxies/Nginx/9-ratelimit.md
new file mode 100644
index 0000000..6537485
--- /dev/null
+++ b/Web Servers & Reverse Proxies/Nginx/9-ratelimit.md	
@@ -0,0 +1,134 @@
+# Nginx Rate Limiting Guide
+
+Nginx can control request rates using the **Leaky Bucket algorithm**. This helps prevent abuse, protect resources, and manage traffic efficiently.
+
+---
+
+## Basic Configuration
+
+```nginx
+limit_req_zone $binary_remote_addr zone=mylimit:10m rate=1r/s;
+
+server {
+    server_name files.usethelinux.shop;
+    root /srv/files;
+
+    location / {
+        autoindex on;
+        limit_req zone=mylimit burst=4 nodelay;
+    }
+}
+```
+
+### Explanation:
+
+* `$binary_remote_addr` → Client IP Address
+* `10m` → Zone memory size (10MB) can handle approximately 160,000 addresses
+* `1r/s` → 1 request per second
+* `burst=4` → Allows a peak of 4 requests without delay
+* `nodelay` → Rejects requests immediately when the limit is exceeded
+
+> The rate can also be set lower, e.g., `10r/min` (10 requests per minute)
+
+---
+
+## Two-Stage Configuration (Smooth Bursting)
+
+```nginx
+limit_req_zone $binary_remote_addr zone=mylimit:10m rate=5r/s;
+
+server {
+    server_name files.usethelinux.shop;
+    root /srv/files;
+
+    location / {
+        autoindex on;
+        limit_req zone=mylimit burst=4 delay=2;
+    }
+}
+```
+
+### Behavior:
+
+* Requests 1–7 → Handled at full speed
+* Requests 8–9 → Handled with delay
+* Requests above 9 → Rejected
+
+---
+
+## Advanced Configuration
+
+```nginx
+limit_req_zone $binary_remote_addr zone=mylimit:10m rate=3r/s;
+
+server {
+    server_name files.usethelinux.shop;
+    root /srv/files;
+
+    location / {
+        autoindex on;
+        limit_req zone=mylimit burst=4 delay=2;
+        limit_req_status 403;
+        limit_req_log_level warn;
+    }
+
+    error_log /var/log/nginx/rate-error.log warn;
+}
+```
+
+### Additional Options:
+
+* `limit_req_status` → Status code returned when requests are rejected (e.g., 403)
+* `limit_req_log_level` → Logging level for rate-limit warnings (requires `error_log` configured)
+
+---
+
+## Whitelist Specific IPs
+
+```nginx
+geo $limit {
+    default 1;
+    10.0.0.0/8 0;
+    192.168.0.0/24 0;
+    93.127.222.112/32 0;
+}
+
+map $limit $limit_key {
+    0 "";
+    1 $binary_remote_addr;
+}
+
+limit_req_zone $limit_key zone=mylimit:10m rate=2r/s;
+
+server {
+    server_name files.usethelinux.shop;
+    root /srv/files;
+
+    location / {
+        autoindex on;
+        limit_req zone=mylimit burst=3 delay=1;
+        limit_req_status 403;
+        limit_req_log_level warn;
+    }
+
+    error_log /var/log/nginx/rate-error.log warn;
+}
+```
+
+### Explanation:
+
+* `geo` → Defines a variable with default `1` (all clients)
+* `map` → Applies `limit_req_zone` only to non-whitelisted IPs
+* Whitelisted IPs (value `0`) are not limited, others follow rate limits
+
+---
+
+## Summary
+
+* **`limit_req_zone`** → Defines the rate-limiting key and storage
+* **`limit_req`** → Applies the rate limit to a location
+* **Burst & Delay** → Control traffic spikes smoothly
+* **Whitelist** → Exclude trusted IPs from rate limiting
+* **Logging & Status** → Monitor and handle rejected requests efficiently
+
+

From df66a55c540131586c5ed06a5ba9dbe08d9c6d79 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 27 Sep 2025 09:09:11 +0330
Subject: [PATCH 090/116] fixed replication names minio

---
 Storage/Minio/Admin/{03.replication.md => 03-site-replication.md} | 0
 Storage/Minio/Admin/04-bucket-replication.md                      | 0
 2 files changed, 0 insertions(+), 0 deletions(-)
 rename Storage/Minio/Admin/{03.replication.md => 03-site-replication.md} (100%)
 create mode 100644 Storage/Minio/Admin/04-bucket-replication.md

diff --git a/Storage/Minio/Admin/03.replication.md b/Storage/Minio/Admin/03-site-replication.md
similarity index 100%
rename from Storage/Minio/Admin/03.replication.md
rename to Storage/Minio/Admin/03-site-replication.md
diff --git a/Storage/Minio/Admin/04-bucket-replication.md b/Storage/Minio/Admin/04-bucket-replication.md
new file mode 100644
index 0000000..e69de29

From 12f7d67480b63b659da603eef48f92d53ae567a6 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 27 Sep 2025 11:07:21 +0330
Subject: [PATCH 091/116] bucket replication minio

---
 Storage/Minio/Admin/04-bucket-replication.md | 90 ++++++++++++++++++++
 1 file changed, 90 insertions(+)

diff --git a/Storage/Minio/Admin/04-bucket-replication.md b/Storage/Minio/Admin/04-bucket-replication.md
index e69de29..d53a471 100644
--- a/Storage/Minio/Admin/04-bucket-replication.md
+++ b/Storage/Minio/Admin/04-bucket-replication.md
@@ -0,0 +1,90 @@
+# MinIO Bucket Replication Guide
+
+MinIO bucket replication allows you to synchronize objects across multiple MinIO servers. **Replication requires versioning** to be enabled on all participating buckets.
+
+---
+
+## 1. One-Way Bucket Replication
+
+**Scenario:** `ms-sv1` → `ms-sv2`
+
+**Command:**
+
+```bash
+mc replicate add ms-sv-1/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-2/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+```
+
+This sets up replication from `ms-sv1` to `ms-sv2`. Changes on `ms-sv1` will be mirrored to `ms-sv2`.
+
+---
+
+## 2. Two-Way Bucket Replication
+
+**Scenario:** `ms-sv1` ↔ `ms-sv2`
+
+**Commands:**
+
+```bash
+mc replicate add ms-sv-1/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-2/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+```
+
+```bash
+mc replicate add ms-sv-2/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-1/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+```
+
+This ensures bidirectional synchronization between `ms-sv1` and `ms-sv2`.
+
+---
+
+## 3. Multi-Node Replication
+
+**Scenario:** `ms-sv1`, `ms-sv2`, `ms-sv3`
+
+Set up replication rules for each pair of servers:
+
+**ms-sv1 rules:**
+
+```bash
+mc replicate add ms-sv-1/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-2/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+
+mc replicate add ms-sv-1/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-3/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+```
+
+**ms-sv2 rules:**
+
+```bash
+mc replicate add ms-sv-2/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-1/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+
+mc replicate add ms-sv-2/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-3/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+```
+
+**ms-sv3 rules:**
+
+```bash
+mc replicate add ms-sv-3/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-1/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+
+mc replicate add ms-sv-3/BUCKET \
+   --remote-bucket 'https://USER:PASSWORD@ms-sv-2/BUCKET' \
+   --replicate "delete,delete-marker,existing-objects"
+```
+
+**Notes:**
+
+* Each MinIO deployment has a replication rule for every other node.
+* This setup ensures that any change in one bucket is synchronized across all nodes.

From bef9b7b5b7f4b5f5c4a14967167db0b030ce6740 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sun, 28 Sep 2025 15:38:58 +0330
Subject: [PATCH 092/116] update web servers dir name

---
 {Web Servers & Reverse Proxies => Web-Servers}/CertBot/certbot.md | 0
 .../NextCloud/NextCloud.md                                        | 0
 .../Nginx/1-Information.md                                        | 0
 .../Nginx/2-Installtion.md                                        | 0
 .../Nginx/3-Setup-Web-Server.md                                   | 0
 .../Nginx/4-Reverse-Proxy.md                                      | 0
 .../Nginx/5-Load-Balancer.md                                      | 0
 .../Nginx/6-File-Server.md                                        | 0
 {Web Servers & Reverse Proxies => Web-Servers}/Nginx/7-ssl.md     | 0
 {Web Servers & Reverse Proxies => Web-Servers}/Nginx/8-auth.md    | 0
 .../Nginx/9-ratelimit.md                                          | 0
 11 files changed, 0 insertions(+), 0 deletions(-)
 rename {Web Servers & Reverse Proxies => Web-Servers}/CertBot/certbot.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/NextCloud/NextCloud.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/1-Information.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/2-Installtion.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/3-Setup-Web-Server.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/4-Reverse-Proxy.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/5-Load-Balancer.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/6-File-Server.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/7-ssl.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/8-auth.md (100%)
 rename {Web Servers & Reverse Proxies => Web-Servers}/Nginx/9-ratelimit.md (100%)

diff --git a/Web Servers & Reverse Proxies/CertBot/certbot.md b/Web-Servers/CertBot/certbot.md
similarity index 100%
rename from Web Servers & Reverse Proxies/CertBot/certbot.md
rename to Web-Servers/CertBot/certbot.md
diff --git a/Web Servers & Reverse Proxies/NextCloud/NextCloud.md b/Web-Servers/NextCloud/NextCloud.md
similarity index 100%
rename from Web Servers & Reverse Proxies/NextCloud/NextCloud.md
rename to Web-Servers/NextCloud/NextCloud.md
diff --git a/Web Servers & Reverse Proxies/Nginx/1-Information.md b/Web-Servers/Nginx/1-Information.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/1-Information.md
rename to Web-Servers/Nginx/1-Information.md
diff --git a/Web Servers & Reverse Proxies/Nginx/2-Installtion.md b/Web-Servers/Nginx/2-Installtion.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/2-Installtion.md
rename to Web-Servers/Nginx/2-Installtion.md
diff --git a/Web Servers & Reverse Proxies/Nginx/3-Setup-Web-Server.md b/Web-Servers/Nginx/3-Setup-Web-Server.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/3-Setup-Web-Server.md
rename to Web-Servers/Nginx/3-Setup-Web-Server.md
diff --git a/Web Servers & Reverse Proxies/Nginx/4-Reverse-Proxy.md b/Web-Servers/Nginx/4-Reverse-Proxy.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/4-Reverse-Proxy.md
rename to Web-Servers/Nginx/4-Reverse-Proxy.md
diff --git a/Web Servers & Reverse Proxies/Nginx/5-Load-Balancer.md b/Web-Servers/Nginx/5-Load-Balancer.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/5-Load-Balancer.md
rename to Web-Servers/Nginx/5-Load-Balancer.md
diff --git a/Web Servers & Reverse Proxies/Nginx/6-File-Server.md b/Web-Servers/Nginx/6-File-Server.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/6-File-Server.md
rename to Web-Servers/Nginx/6-File-Server.md
diff --git a/Web Servers & Reverse Proxies/Nginx/7-ssl.md b/Web-Servers/Nginx/7-ssl.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/7-ssl.md
rename to Web-Servers/Nginx/7-ssl.md
diff --git a/Web Servers & Reverse Proxies/Nginx/8-auth.md b/Web-Servers/Nginx/8-auth.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/8-auth.md
rename to Web-Servers/Nginx/8-auth.md
diff --git a/Web Servers & Reverse Proxies/Nginx/9-ratelimit.md b/Web-Servers/Nginx/9-ratelimit.md
similarity index 100%
rename from Web Servers & Reverse Proxies/Nginx/9-ratelimit.md
rename to Web-Servers/Nginx/9-ratelimit.md

From 1c472e4b94c53664b2338ba531c5f7ce1c117542 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sun, 28 Sep 2025 16:38:51 +0330
Subject: [PATCH 093/116] nginx optimization doc

---
 .../{1-Information.md => 01-Information.md}   |   0
 .../{2-Installtion.md => 02-Installtion.md}   |   0
 ...p-Web-Server.md => 03-Setup-Web-Server.md} |   0
 ...4-Reverse-Proxy.md => 04-Reverse-Proxy.md} |   0
 ...5-Load-Balancer.md => 05-Load-Balancer.md} |   0
 .../{6-File-Server.md => 06-File-Server.md}   |   0
 Web-Servers/Nginx/{7-ssl.md => 07-SSL.md}     |   0
 Web-Servers/Nginx/{8-auth.md => 08-Auth.md}   |   0
 .../Nginx/{9-ratelimit.md => 09-Ratelimit.md} |   0
 Web-Servers/Nginx/10-Optimization.md          | 102 ++++++++++++++++++
 10 files changed, 102 insertions(+)
 rename Web-Servers/Nginx/{1-Information.md => 01-Information.md} (100%)
 rename Web-Servers/Nginx/{2-Installtion.md => 02-Installtion.md} (100%)
 rename Web-Servers/Nginx/{3-Setup-Web-Server.md => 03-Setup-Web-Server.md} (100%)
 rename Web-Servers/Nginx/{4-Reverse-Proxy.md => 04-Reverse-Proxy.md} (100%)
 rename Web-Servers/Nginx/{5-Load-Balancer.md => 05-Load-Balancer.md} (100%)
 rename Web-Servers/Nginx/{6-File-Server.md => 06-File-Server.md} (100%)
 rename Web-Servers/Nginx/{7-ssl.md => 07-SSL.md} (100%)
 rename Web-Servers/Nginx/{8-auth.md => 08-Auth.md} (100%)
 rename Web-Servers/Nginx/{9-ratelimit.md => 09-Ratelimit.md} (100%)
 create mode 100644 Web-Servers/Nginx/10-Optimization.md

diff --git a/Web-Servers/Nginx/1-Information.md b/Web-Servers/Nginx/01-Information.md
similarity index 100%
rename from Web-Servers/Nginx/1-Information.md
rename to Web-Servers/Nginx/01-Information.md
diff --git a/Web-Servers/Nginx/2-Installtion.md b/Web-Servers/Nginx/02-Installtion.md
similarity index 100%
rename from Web-Servers/Nginx/2-Installtion.md
rename to Web-Servers/Nginx/02-Installtion.md
diff --git a/Web-Servers/Nginx/3-Setup-Web-Server.md b/Web-Servers/Nginx/03-Setup-Web-Server.md
similarity index 100%
rename from Web-Servers/Nginx/3-Setup-Web-Server.md
rename to Web-Servers/Nginx/03-Setup-Web-Server.md
diff --git a/Web-Servers/Nginx/4-Reverse-Proxy.md b/Web-Servers/Nginx/04-Reverse-Proxy.md
similarity index 100%
rename from Web-Servers/Nginx/4-Reverse-Proxy.md
rename to Web-Servers/Nginx/04-Reverse-Proxy.md
diff --git a/Web-Servers/Nginx/5-Load-Balancer.md b/Web-Servers/Nginx/05-Load-Balancer.md
similarity index 100%
rename from Web-Servers/Nginx/5-Load-Balancer.md
rename to Web-Servers/Nginx/05-Load-Balancer.md
diff --git a/Web-Servers/Nginx/6-File-Server.md b/Web-Servers/Nginx/06-File-Server.md
similarity index 100%
rename from Web-Servers/Nginx/6-File-Server.md
rename to Web-Servers/Nginx/06-File-Server.md
diff --git a/Web-Servers/Nginx/7-ssl.md b/Web-Servers/Nginx/07-SSL.md
similarity index 100%
rename from Web-Servers/Nginx/7-ssl.md
rename to Web-Servers/Nginx/07-SSL.md
diff --git a/Web-Servers/Nginx/8-auth.md b/Web-Servers/Nginx/08-Auth.md
similarity index 100%
rename from Web-Servers/Nginx/8-auth.md
rename to Web-Servers/Nginx/08-Auth.md
diff --git a/Web-Servers/Nginx/9-ratelimit.md b/Web-Servers/Nginx/09-Ratelimit.md
similarity index 100%
rename from Web-Servers/Nginx/9-ratelimit.md
rename to Web-Servers/Nginx/09-Ratelimit.md
diff --git a/Web-Servers/Nginx/10-Optimization.md b/Web-Servers/Nginx/10-Optimization.md
new file mode 100644
index 0000000..937988b
--- /dev/null
+++ b/Web-Servers/Nginx/10-Optimization.md
@@ -0,0 +1,102 @@
+# **Nginx Optimization Guide**
+
+This document provides recommended configurations to optimize **Nginx performance** for high concurrency, low latency, and efficient resource usage.
+
+---
+
+## **1. Core Performance Configuration**
+
+```nginx
+worker_processes auto;
+worker_rlimit_nofile 65535;
+
+events {
+    worker_connections 8192;   
+    multi_accept on;          
+    use epoll;                 
+}
+```
+
+### **Explanation:**
+
+| Directive                    | Description                                                                                                     |
+| ---------------------------- | --------------------------------------------------------------------------------------------------------------- |
+| `worker_processes auto`      | Automatically sets the number of worker processes to match CPU cores. Best practice: match number of CPU cores. |
+| `worker_rlimit_nofile 65535` | Increases the number of file descriptors (FD) Nginx can handle, supporting higher connections.                  |
+| `worker_connections 8192`    | Maximum number of simultaneous connections a worker can handle.                                                 |
+| `multi_accept on`            | Allows a worker to accept multiple new connections at once. Improves performance but increases CPU usage.       |
+| `use epoll`                  | Uses the epoll event model (Linux only). Highly scalable and efficient for non-blocking I/O.                    |
+
+---
+
+## **2. HTTP Optimization**
+
+```nginx
+http {
+    sendfile on;               
+    tcp_nopush on;             
+    tcp_nodelay on;            
+    keepalive_timeout 65;      
+    keepalive_requests 10000;  
+
+    client_max_body_size 50M;  
+    server_tokens off;         
+
+    # Compression
+    gzip on;
+    gzip_comp_level 5;         
+    gzip_min_length 256;
+    gzip_proxied any;
+    gzip_types text/plain text/css application/json application/javascript application/xml+rss;
+}
+```
+
+### **Explanation:**
+
+| Directive                  | Description                                                                                           |
+| -------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `sendfile on`              | Sends files directly from disk to network (zero-copy). Reduces CPU usage and improves response time.  |
+| `tcp_nopush on`            | Sends headers and body together in a single packet for better network efficiency.                     |
+| `tcp_nodelay on`           | Sends small TCP packets immediately, reducing latency for small responses.                            |
+| `keepalive_timeout 65`     | Keeps connections open for 65 seconds after a request (adjustable).                                   |
+| `keepalive_requests 10000` | Maximum number of requests allowed per keepalive connection.                                          |
+| `client_max_body_size 50M` | Limits maximum upload size to prevent DoS attacks.                                                    |
+| `server_tokens off`        | Hides Nginx version in headers and error pages for security.                                          |
+| `gzip on`                  | Enables gzip compression of responses to reduce bandwidth.                                            |
+| `gzip_comp_level 5`        | Compression level (1 = fast, low compression; 9 = slow, maximum compression). 5 is a balanced choice. |
+| `gzip_min_length 256`      | Only compress responses larger than 256 bytes.                                                        |
+| `gzip_proxied any`         | Enable compression even behind reverse proxies.                                                       |
+| `gzip_types`               | Defines content types eligible for compression.                                                       |
+
+---
+
+## **3. Static File Caching**
+
+```nginx
+location ~* \.(jpg|jpeg|png|gif|ico|css|js|woff2?)$ {
+    expires 7d;
+    access_log off;
+    add_header Cache-Control "public, no-transform";
+}
+```
+
+### **Explanation:**
+
+| Directive                                         | Description                                               |     |     |     |     |    |           |                                                               |
+| ------------------------------------------------- | --------------------------------------------------------- | --- | --- | --- | --- | -- | --------- | ------------------------------------------------------------- |
+| `~* .(jpg                                         | jpeg                                                      | png | gif | ico | css | js | woff2?)$` | Regex to match static files (images, styles, scripts, fonts). |
+| `expires 7d`                                      | Sets browser caching for 7 days to reduce server load.    |     |     |     |     |    |           |                                                               |
+| `access_log off`                                  | Disables logging for static files to improve performance. |     |     |     |     |    |           |                                                               |
+| `add_header Cache-Control "public, no-transform"` | Ensures files are cacheable by clients and proxies.       |     |     |     |     |    |           |                                                               |
+
+---
+
+## **Summary of Best Practices**
+
+1. **Worker & Connection Optimization:** Match workers to CPU cores, increase FD limits, and configure events for high concurrency.
+2. **TCP & HTTP Tweaks:** Enable `sendfile`, `tcp_nopush`, and `tcp_nodelay` for low latency and efficient transfers.
+3. **Connection Reuse:** Use `keepalive_timeout` and `keepalive_requests` to reduce overhead of repeated connections.
+4. **Compression:** Enable gzip with balanced compression for reduced bandwidth usage.
+5. **Security & Limits:** Hide Nginx version and set client upload limits to prevent abuse.
+6. **Static Content Caching:** Cache static files with long expiry and disable unnecessary logging.
+

From 6beeea3e5c7d14aecbd4e471e075d0eac47bba0c Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 09:53:08 +0330
Subject: [PATCH 094/116] change dir name orch,container

---
 .../Docker/1-Information.md                                       | 0
 .../Docker/2-Commands.md                                          | 0
 .../Docker/3-Docker-File.md                                       | 0
 .../Docker/4-Docker-Compose.md                                    | 0
 .../Docker/5-Docker-Swarm.md                                      | 0
 .../Docker/Additional.md                                          | 0
 .../Docker/Docker-Dirs.md                                         | 0
 .../Docker/docker-stack-example.yml                               | 0
 .../Kubernetes/1-Information.md                                   | 0
 .../Kubernetes/2-Installtion.md                                   | 0
 .../Kubernetes/3-BasicSetup.md                                    | 0
 .../Kubernetes/Commands/3-Commands.md                             | 0
 .../Kubernetes/Commands/label.md                                  | 0
 .../Kubernetes/Commands/log-debug.md                              | 0
 .../Kubernetes/Commands/node-manage.md                            | 0
 .../Kubernetes/Storage/Longhorn/with-kubectl.md                   | 0
 .../Kubernetes/Storage/Pv.md                                      | 0
 .../Kubernetes/Storage/emptydir_vol.md                            | 0
 .../Kubernetes/etcd-external.md                                   | 0
 .../Kubernetes/workloads/01-NameSpace.md                          | 0
 .../Kubernetes/workloads/02-Pod.md                                | 0
 .../Kubernetes/workloads/03-Replicaset.md                         | 0
 .../Kubernetes/workloads/04-Deployment.md                         | 0
 .../Kubernetes/workloads/05-hpa.md                                | 0
 .../Kubernetes/workloads/06-DaemonSet.md                          | 0
 .../Kubernetes/workloads/07-Jobs.md                               | 0
 .../Kubernetes/workloads/08-Cronjobs.md                           | 0
 .../Kubernetes/workloads/09-Services.md                           | 0
 .../Kubernetes/workloads/10-Deployment-With-Services.md           | 0
 .../Kubernetes/workloads/11-Config-map.md                         | 0
 .../Kubernetes/workloads/12-Resource-quota.md                     | 0
 .../Kubernetes/workloads/13-Secret.md                             | 0
 .../Kubernetes/workloads/14-Ingress.md                            | 0
 .../Kubernetes/workloads/manifests/cronjob.yaml                   | 0
 .../Kubernetes/workloads/manifests/deployment-with-service.yaml   | 0
 .../Kubernetes/workloads/manifests/deployment.yaml                | 0
 .../Kubernetes/workloads/manifests/ds.yml                         | 0
 .../Kubernetes/workloads/manifests/job.yaml                       | 0
 .../Kubernetes/workloads/manifests/namespace.yaml                 | 0
 .../Kubernetes/workloads/manifests/pod.yaml                       | 0
 .../Kubernetes/workloads/manifests/replicaset.yml                 | 0
 .../Kubernetes/workloads/manifests/service.yaml                   | 0
 .../Kubernetes/workloads/manifests/state-full-set.yaml            | 0
 43 files changed, 0 insertions(+), 0 deletions(-)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/1-Information.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/2-Commands.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/3-Docker-File.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/4-Docker-Compose.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/5-Docker-Swarm.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/Additional.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/Docker-Dirs.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Docker/docker-stack-example.yml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/1-Information.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/2-Installtion.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/3-BasicSetup.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Commands/3-Commands.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Commands/label.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Commands/log-debug.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Commands/node-manage.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Storage/Longhorn/with-kubectl.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Storage/Pv.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/Storage/emptydir_vol.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/etcd-external.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/01-NameSpace.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/02-Pod.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/03-Replicaset.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/04-Deployment.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/05-hpa.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/06-DaemonSet.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/07-Jobs.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/08-Cronjobs.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/09-Services.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/10-Deployment-With-Services.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/11-Config-map.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/12-Resource-quota.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/13-Secret.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/14-Ingress.md (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/cronjob.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/deployment-with-service.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/deployment.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/ds.yml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/job.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/namespace.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/pod.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/replicaset.yml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/service.yaml (100%)
 rename {Containerization & Orchestration => Containerization-Orchestration}/Kubernetes/workloads/manifests/state-full-set.yaml (100%)

diff --git a/Containerization & Orchestration/Docker/1-Information.md b/Containerization-Orchestration/Docker/1-Information.md
similarity index 100%
rename from Containerization & Orchestration/Docker/1-Information.md
rename to Containerization-Orchestration/Docker/1-Information.md
diff --git a/Containerization & Orchestration/Docker/2-Commands.md b/Containerization-Orchestration/Docker/2-Commands.md
similarity index 100%
rename from Containerization & Orchestration/Docker/2-Commands.md
rename to Containerization-Orchestration/Docker/2-Commands.md
diff --git a/Containerization & Orchestration/Docker/3-Docker-File.md b/Containerization-Orchestration/Docker/3-Docker-File.md
similarity index 100%
rename from Containerization & Orchestration/Docker/3-Docker-File.md
rename to Containerization-Orchestration/Docker/3-Docker-File.md
diff --git a/Containerization & Orchestration/Docker/4-Docker-Compose.md b/Containerization-Orchestration/Docker/4-Docker-Compose.md
similarity index 100%
rename from Containerization & Orchestration/Docker/4-Docker-Compose.md
rename to Containerization-Orchestration/Docker/4-Docker-Compose.md
diff --git a/Containerization & Orchestration/Docker/5-Docker-Swarm.md b/Containerization-Orchestration/Docker/5-Docker-Swarm.md
similarity index 100%
rename from Containerization & Orchestration/Docker/5-Docker-Swarm.md
rename to Containerization-Orchestration/Docker/5-Docker-Swarm.md
diff --git a/Containerization & Orchestration/Docker/Additional.md b/Containerization-Orchestration/Docker/Additional.md
similarity index 100%
rename from Containerization & Orchestration/Docker/Additional.md
rename to Containerization-Orchestration/Docker/Additional.md
diff --git a/Containerization & Orchestration/Docker/Docker-Dirs.md b/Containerization-Orchestration/Docker/Docker-Dirs.md
similarity index 100%
rename from Containerization & Orchestration/Docker/Docker-Dirs.md
rename to Containerization-Orchestration/Docker/Docker-Dirs.md
diff --git a/Containerization & Orchestration/Docker/docker-stack-example.yml b/Containerization-Orchestration/Docker/docker-stack-example.yml
similarity index 100%
rename from Containerization & Orchestration/Docker/docker-stack-example.yml
rename to Containerization-Orchestration/Docker/docker-stack-example.yml
diff --git a/Containerization & Orchestration/Kubernetes/1-Information.md b/Containerization-Orchestration/Kubernetes/1-Information.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/1-Information.md
rename to Containerization-Orchestration/Kubernetes/1-Information.md
diff --git a/Containerization & Orchestration/Kubernetes/2-Installtion.md b/Containerization-Orchestration/Kubernetes/2-Installtion.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/2-Installtion.md
rename to Containerization-Orchestration/Kubernetes/2-Installtion.md
diff --git a/Containerization & Orchestration/Kubernetes/3-BasicSetup.md b/Containerization-Orchestration/Kubernetes/3-BasicSetup.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/3-BasicSetup.md
rename to Containerization-Orchestration/Kubernetes/3-BasicSetup.md
diff --git a/Containerization & Orchestration/Kubernetes/Commands/3-Commands.md b/Containerization-Orchestration/Kubernetes/Commands/3-Commands.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Commands/3-Commands.md
rename to Containerization-Orchestration/Kubernetes/Commands/3-Commands.md
diff --git a/Containerization & Orchestration/Kubernetes/Commands/label.md b/Containerization-Orchestration/Kubernetes/Commands/label.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Commands/label.md
rename to Containerization-Orchestration/Kubernetes/Commands/label.md
diff --git a/Containerization & Orchestration/Kubernetes/Commands/log-debug.md b/Containerization-Orchestration/Kubernetes/Commands/log-debug.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Commands/log-debug.md
rename to Containerization-Orchestration/Kubernetes/Commands/log-debug.md
diff --git a/Containerization & Orchestration/Kubernetes/Commands/node-manage.md b/Containerization-Orchestration/Kubernetes/Commands/node-manage.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Commands/node-manage.md
rename to Containerization-Orchestration/Kubernetes/Commands/node-manage.md
diff --git a/Containerization & Orchestration/Kubernetes/Storage/Longhorn/with-kubectl.md b/Containerization-Orchestration/Kubernetes/Storage/Longhorn/with-kubectl.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Storage/Longhorn/with-kubectl.md
rename to Containerization-Orchestration/Kubernetes/Storage/Longhorn/with-kubectl.md
diff --git a/Containerization & Orchestration/Kubernetes/Storage/Pv.md b/Containerization-Orchestration/Kubernetes/Storage/Pv.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Storage/Pv.md
rename to Containerization-Orchestration/Kubernetes/Storage/Pv.md
diff --git a/Containerization & Orchestration/Kubernetes/Storage/emptydir_vol.md b/Containerization-Orchestration/Kubernetes/Storage/emptydir_vol.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/Storage/emptydir_vol.md
rename to Containerization-Orchestration/Kubernetes/Storage/emptydir_vol.md
diff --git a/Containerization & Orchestration/Kubernetes/etcd-external.md b/Containerization-Orchestration/Kubernetes/etcd-external.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/etcd-external.md
rename to Containerization-Orchestration/Kubernetes/etcd-external.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/01-NameSpace.md b/Containerization-Orchestration/Kubernetes/workloads/01-NameSpace.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/01-NameSpace.md
rename to Containerization-Orchestration/Kubernetes/workloads/01-NameSpace.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/02-Pod.md b/Containerization-Orchestration/Kubernetes/workloads/02-Pod.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/02-Pod.md
rename to Containerization-Orchestration/Kubernetes/workloads/02-Pod.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/03-Replicaset.md b/Containerization-Orchestration/Kubernetes/workloads/03-Replicaset.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/03-Replicaset.md
rename to Containerization-Orchestration/Kubernetes/workloads/03-Replicaset.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/04-Deployment.md b/Containerization-Orchestration/Kubernetes/workloads/04-Deployment.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/04-Deployment.md
rename to Containerization-Orchestration/Kubernetes/workloads/04-Deployment.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/05-hpa.md b/Containerization-Orchestration/Kubernetes/workloads/05-hpa.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/05-hpa.md
rename to Containerization-Orchestration/Kubernetes/workloads/05-hpa.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/06-DaemonSet.md b/Containerization-Orchestration/Kubernetes/workloads/06-DaemonSet.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/06-DaemonSet.md
rename to Containerization-Orchestration/Kubernetes/workloads/06-DaemonSet.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/07-Jobs.md b/Containerization-Orchestration/Kubernetes/workloads/07-Jobs.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/07-Jobs.md
rename to Containerization-Orchestration/Kubernetes/workloads/07-Jobs.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/08-Cronjobs.md b/Containerization-Orchestration/Kubernetes/workloads/08-Cronjobs.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/08-Cronjobs.md
rename to Containerization-Orchestration/Kubernetes/workloads/08-Cronjobs.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/09-Services.md b/Containerization-Orchestration/Kubernetes/workloads/09-Services.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/09-Services.md
rename to Containerization-Orchestration/Kubernetes/workloads/09-Services.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md b/Containerization-Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md
rename to Containerization-Orchestration/Kubernetes/workloads/10-Deployment-With-Services.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md b/Containerization-Orchestration/Kubernetes/workloads/11-Config-map.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/11-Config-map.md
rename to Containerization-Orchestration/Kubernetes/workloads/11-Config-map.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/12-Resource-quota.md b/Containerization-Orchestration/Kubernetes/workloads/12-Resource-quota.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/12-Resource-quota.md
rename to Containerization-Orchestration/Kubernetes/workloads/12-Resource-quota.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/13-Secret.md b/Containerization-Orchestration/Kubernetes/workloads/13-Secret.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/13-Secret.md
rename to Containerization-Orchestration/Kubernetes/workloads/13-Secret.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/14-Ingress.md b/Containerization-Orchestration/Kubernetes/workloads/14-Ingress.md
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/14-Ingress.md
rename to Containerization-Orchestration/Kubernetes/workloads/14-Ingress.md
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/cronjob.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/cronjob.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/cronjob.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/cronjob.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/deployment-with-service.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/deployment.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/deployment.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/deployment.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/deployment.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/ds.yml b/Containerization-Orchestration/Kubernetes/workloads/manifests/ds.yml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/ds.yml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/ds.yml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/job.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/job.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/job.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/job.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/namespace.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/namespace.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/namespace.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/namespace.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/pod.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/pod.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/pod.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/pod.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/replicaset.yml b/Containerization-Orchestration/Kubernetes/workloads/manifests/replicaset.yml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/replicaset.yml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/replicaset.yml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/service.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/service.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/service.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/service.yaml
diff --git a/Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml
similarity index 100%
rename from Containerization & Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml
rename to Containerization-Orchestration/Kubernetes/workloads/manifests/state-full-set.yaml

From bec8b349be58546a4edf0038be2ea76fb3510e41 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 09:55:15 +0330
Subject: [PATCH 095/116] k8s lifecycle doc

---
 .../Kubernetes/workloads/15-lifecycle.md      | 140 ++++++++++++++++++
 1 file changed, 140 insertions(+)
 create mode 100644 Containerization-Orchestration/Kubernetes/workloads/15-lifecycle.md

diff --git a/Containerization-Orchestration/Kubernetes/workloads/15-lifecycle.md b/Containerization-Orchestration/Kubernetes/workloads/15-lifecycle.md
new file mode 100644
index 0000000..13e2f8e
--- /dev/null
+++ b/Containerization-Orchestration/Kubernetes/workloads/15-lifecycle.md
@@ -0,0 +1,140 @@
+# Kubernetes Lifecycle Hooks: `postStart` and `preStop`
+
+## Overview
+
+In Kubernetes, **lifecycle hooks** allow you to run specific code when a container starts or stops. These hooks are part of a container’s lifecycle and are useful for performing setup and cleanup tasks.
+
+The two main lifecycle hooks are:
+
+* **`postStart`** – Executed immediately after the container starts.
+* **`preStop`** – Executed just before the container stops.
+
+These hooks can be defined inside the container specification in a Pod manifest.
+
+---
+
+## 1. `postStart` Hook
+
+### Description
+
+The `postStart` hook runs **immediately after a container is created**, but before it is marked as *Running*. It can be used to perform initialization tasks that need to occur right after startup.
+
+The `postStart` hook supports two types of actions:
+
+* `exec` – Run a command inside the container.
+* `httpGet` – Send an HTTP request to a specified endpoint inside the container.
+
+### Notes
+
+* The `postStart` hook and the container’s main process run **concurrently**.
+* If the hook fails, the container is considered to have failed and will be restarted according to its restart policy.
+
+### Example
+
+```yaml
+lifecycle:
+  postStart:
+    exec:
+      command: ["/bin/sh", "-c", "echo Container started at $(date) >> /var/log/startup.log"]
+```
+
+Using an HTTP GET action:
+
+```yaml
+lifecycle:
+  postStart:
+    httpGet:
+      path: /startup
+      port: 8080
+```
+
+### Common Use Cases
+
+* Initializing configuration files or environment data.
+* Sending startup notifications to monitoring systems.
+* Preparing application dependencies.
+
+---
+
+## 2. `preStop` Hook
+
+### Description
+
+The `preStop` hook runs **just before a container is terminated**. Kubernetes will execute the hook and wait for it to complete before sending the `SIGTERM` signal to the container’s main process.
+
+This hook is typically used to ensure a **graceful shutdown** of the application.
+
+Like `postStart`, it supports:
+
+* `exec`
+* `httpGet`
+
+### Notes
+
+* The hook must complete within the time defined by `terminationGracePeriodSeconds`.
+* If the hook does not finish within that time, the container will be forcibly terminated.
+
+### Example
+
+```yaml
+lifecycle:
+  preStop:
+    exec:
+      command: ["/bin/sh", "-c", "echo Shutting down... >> /var/log/shutdown.log && sleep 5"]
+```
+
+### Common Use Cases
+
+* Closing active connections.
+* Flushing logs or metrics.
+* Deregistering the service from a load balancer or discovery system.
+* Notifying external systems about the shutdown event.
+
+---
+
+## 3. Full Example
+
+```yaml
+apiVersion: v1
+kind: Pod
+metadata:
+  name: lifecycle-demo
+spec:
+  containers:
+  - name: demo-container
+    image: nginx
+    lifecycle:
+      postStart:
+        exec:
+          command: ["/bin/sh", "-c", "echo 'Container started!' > /usr/share/nginx/html/index.html"]
+      preStop:
+        exec:
+          command: ["/bin/sh", "-c", "echo 'Container stopping...' >> /usr/share/nginx/html/index.html && sleep 10"]
+    terminationGracePeriodSeconds: 15
+```
+
+---
+
+## 4. Best Practices for DevOps Engineers
+
+1. **Handle Signals in Your Application**
+   Ensure your application properly handles `SIGTERM` and `SIGKILL` for clean shutdowns.
+
+2. **Combine Hooks with Grace Periods**
+   Use `preStop` together with `terminationGracePeriodSeconds` to allow sufficient cleanup time.
+
+3. **Monitor Hook Execution**
+   Log hook outputs for debugging and verification.
+
+4. **Avoid Long-Running or Blocking Hooks**
+   Hooks should be lightweight to avoid delaying container lifecycle events.
+
+---
+
+## 5. Summary
+
+| Hook Type   | Trigger Time                       | Purpose           | Common Actions                                    |
+| ----------- | ---------------------------------- | ----------------- | ------------------------------------------------- |
+| `postStart` | Immediately after container starts | Initialization    | Load configs, warm cache, notify service          |
+| `preStop`   | Before container termination       | Graceful shutdown | Flush data, close connections, deregister service |
+

From 1c613282b0b05e6dbc6b318c570cbf9bdbc40dc1 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 09:56:51 +0330
Subject: [PATCH 096/116] k8s lifecycle manifest

---
 .../workloads/manifests/lifecycle.yaml           | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)
 create mode 100644 Containerization-Orchestration/Kubernetes/workloads/manifests/lifecycle.yaml

diff --git a/Containerization-Orchestration/Kubernetes/workloads/manifests/lifecycle.yaml b/Containerization-Orchestration/Kubernetes/workloads/manifests/lifecycle.yaml
new file mode 100644
index 0000000..46f9d46
--- /dev/null
+++ b/Containerization-Orchestration/Kubernetes/workloads/manifests/lifecycle.yaml
@@ -0,0 +1,16 @@
+apiVersion: v1
+kind: Pod
+metadata:
+  name: lifecycle-demo
+spec:
+  containers:
+  - name: demo-container
+    image: nginx
+    lifecycle:
+      postStart:
+        exec:
+          command: ["/bin/sh", "-c", "echo 'Container started!' > /usr/share/nginx/html/index.html"]
+      preStop:
+        exec:
+          command: ["/bin/sh", "-c", "echo 'Container stopping...' >> /usr/share/nginx/html/index.html && sleep 10"]
+    terminationGracePeriodSeconds: 15

From f96378c4806267d9cf9c0d412cfbb4302809e19c Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 10:05:42 +0330
Subject: [PATCH 097/116] k8s limitrange doc

---
 .../Kubernetes/workloads/16-limirange.md      | 104 ++++++++++++++++++
 1 file changed, 104 insertions(+)
 create mode 100644 Containerization-Orchestration/Kubernetes/workloads/16-limirange.md

diff --git a/Containerization-Orchestration/Kubernetes/workloads/16-limirange.md b/Containerization-Orchestration/Kubernetes/workloads/16-limirange.md
new file mode 100644
index 0000000..83d1ab4
--- /dev/null
+++ b/Containerization-Orchestration/Kubernetes/workloads/16-limirange.md
@@ -0,0 +1,104 @@
+## LimitRange in Kubernetes
+
+### Overview
+
+A **LimitRange** in Kubernetes is a namespace-level policy object that defines constraints on the compute resources that individual **Pods** and **Containers** can request and use. It helps ensure that workloads run efficiently and fairly within a shared cluster.
+
+A LimitRange can set:
+
+* Minimum and maximum resource requests and limits
+* Default requests and limits if none are specified by the user
+
+While a **ResourceQuota** enforces limits at the **namespace** level (total resource usage), a **LimitRange** enforces rules at the **Pod or Container** level.
+
+---
+
+### Why Use a LimitRange
+
+In a shared cluster, users might:
+
+* Deploy Pods without specifying any resource requests or limits.
+* Request excessive resources, leading to inefficient utilization.
+
+A LimitRange prevents these issues by:
+
+* Automatically applying default resource values when unspecified.
+* Enforcing minimum and maximum resource thresholds.
+* Ensuring fair distribution of resources among applications.
+
+---
+
+### How It Works
+
+When a Pod or Container is created in a namespace with a LimitRange:
+
+1. The Kubernetes API server checks if resource requests and limits are defined.
+2. If they are not provided, the LimitRange applies the configured default values.
+3. If provided values fall outside the configured minimum or maximum bounds, the API server rejects the creation request.
+
+---
+
+### Example: LimitRange YAML
+
+```yaml
+apiVersion: v1
+kind: LimitRange
+metadata:
+  name: mem-cpu-limits
+  namespace: dev-team
+spec:
+  limits:
+  - type: Container
+    max:
+      cpu: "2"          # Maximum 2 cores per container
+      memory: "2Gi"     # Maximum 2Gi memory per container
+    min:
+      cpu: "200m"       # Minimum 0.2 cores per container
+      memory: "256Mi"   # Minimum 256Mi memory per container
+    default:
+      cpu: "500m"       # Default limit if not specified
+      memory: "512Mi"
+    defaultRequest:
+      cpu: "250m"       # Default request if not specified
+      memory: "256Mi"
+```
+
+---
+
+### Example Behavior
+
+| Scenario | Request/Limit Defined? | Result                                        |
+| -------- | ---------------------- | --------------------------------------------- |
+| None     | No                     | Defaults applied (`250m` CPU, `256Mi` Memory) |
+| Too High | Yes (e.g., 3 CPU)      | Rejected — exceeds max of 2                   |
+| Too Low  | Yes (e.g., 100m CPU)   | Rejected — below min of 200m                  |
+
+---
+
+### Viewing a LimitRange
+
+You can inspect LimitRanges in a namespace using:
+
+```bash
+kubectl get limitrange -n dev-team
+kubectl describe limitrange mem-cpu-limits -n dev-team
+```
+
+---
+
+### LimitRange vs ResourceQuota
+
+| Feature         | LimitRange                       | ResourceQuota                  |
+| --------------- | -------------------------------- | ------------------------------ |
+| Scope           | Per Container/Pod                | Per Namespace                  |
+| Controls        | Min/Max/Default resource values  | Total resource usage           |
+| Purpose         | Enforce sane defaults and bounds | Prevent namespace-wide overuse |
+| Works best with | ResourceQuota                    | LimitRange                     |
+
+---
+
+### Summary
+
+A **LimitRange** ensures that every Pod or Container in a namespace has appropriate resource requests and limits, preventing resource misuse and ensuring cluster stability. It complements **ResourceQuota** to provide complete resource management across both individual workloads and namespaces.
+
+

From ab2cd44f7b486f1b47d3956bbcf642e6cfcc1bd4 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 10:15:42 +0330
Subject: [PATCH 098/116] git: fix dir name

---
 {Code Management => Code-Management}/Git/main.md                  | 0
 {Code Management/Git => Code-Management}/Gitlab/Gitlab-CI/1.md    | 0
 .../Git => Code-Management}/Gitlab/Gitlab-CI/gitlab-ci.yaml       | 0
 .../Git => Code-Management}/Gitlab/Install/baremetal.md           | 0
 4 files changed, 0 insertions(+), 0 deletions(-)
 rename {Code Management => Code-Management}/Git/main.md (100%)
 rename {Code Management/Git => Code-Management}/Gitlab/Gitlab-CI/1.md (100%)
 rename {Code Management/Git => Code-Management}/Gitlab/Gitlab-CI/gitlab-ci.yaml (100%)
 rename {Code Management/Git => Code-Management}/Gitlab/Install/baremetal.md (100%)

diff --git a/Code Management/Git/main.md b/Code-Management/Git/main.md
similarity index 100%
rename from Code Management/Git/main.md
rename to Code-Management/Git/main.md
diff --git a/Code Management/Git/Gitlab/Gitlab-CI/1.md b/Code-Management/Gitlab/Gitlab-CI/1.md
similarity index 100%
rename from Code Management/Git/Gitlab/Gitlab-CI/1.md
rename to Code-Management/Gitlab/Gitlab-CI/1.md
diff --git a/Code Management/Git/Gitlab/Gitlab-CI/gitlab-ci.yaml b/Code-Management/Gitlab/Gitlab-CI/gitlab-ci.yaml
similarity index 100%
rename from Code Management/Git/Gitlab/Gitlab-CI/gitlab-ci.yaml
rename to Code-Management/Gitlab/Gitlab-CI/gitlab-ci.yaml
diff --git a/Code Management/Git/Gitlab/Install/baremetal.md b/Code-Management/Gitlab/Install/baremetal.md
similarity index 100%
rename from Code Management/Git/Gitlab/Install/baremetal.md
rename to Code-Management/Gitlab/Install/baremetal.md

From 83114643c8431c3a4b7c090c991cace8000bb3de Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 10:39:58 +0330
Subject: [PATCH 099/116] git: gitlab cache

---
 Code-Management/Gitlab/Gitlab-Cache.md | 169 +++++++++++++++++++++++++
 1 file changed, 169 insertions(+)
 create mode 100644 Code-Management/Gitlab/Gitlab-Cache.md

diff --git a/Code-Management/Gitlab/Gitlab-Cache.md b/Code-Management/Gitlab/Gitlab-Cache.md
new file mode 100644
index 0000000..b7c4461
--- /dev/null
+++ b/Code-Management/Gitlab/Gitlab-Cache.md
@@ -0,0 +1,169 @@
+# GitLab CI/CD Cache Guide
+
+GitLab provides a caching system for jobs to speed up pipelines by reusing dependencies like `node_modules`, Ruby gems, and other build artifacts. This guide covers how to configure and use caching effectively.
+
+---
+
+## Key Features
+
+* **Cache Storage**: Data is saved in the GitLab Runner and can also be stored in external storage such as S3, MinIO, GCS, etc.
+* **Branch-Specific Caching**: Maintain separate caches per branch, job, or stage.
+* **Fallbacks**: Jobs can pull cache from other branches if the current branch does not have cache.
+* **Simple Cache**: Uses file locks and directory caching for efficiency.
+
+---
+
+## Basic Cache Example
+
+Cache dependencies like Ruby gems and Yarn modules:
+
+```yaml
+test-job:
+  stage: build
+  cache:
+    - key:
+        files:
+          - Gemfile.lock
+      paths:
+        - vendor/ruby
+    - key:
+        files:
+          - yarn.lock
+      paths:
+        - .yarn-cache/
+  script:
+    - bundle config set --local path 'vendor/ruby'
+    - bundle install
+    - yarn install --cache-folder .yarn-cache
+    - echo "Run tests..."
+```
+
+**Behavior**:
+If the lock file (`Gemfile.lock` or `yarn.lock`) changes, the cache is updated automatically.
+
+---
+
+## Branch Cache with Fallbacks
+
+When creating a new branch, it may not have a cache yet. You can pull from the default branch (e.g., `main` or `master`) or a global default cache:
+
+```yaml
+test-job:
+  stage: build
+  cache:
+    - key: cache-$CI_COMMIT_REF_SLUG
+      fallback_keys:
+        - cache-$CI_DEFAULT_BRANCH
+        - cache-default
+      paths:
+        - vendor/ruby
+  script:
+    - bundle config set --local path 'vendor/ruby'
+    - bundle install
+    - echo "Run tests..."
+```
+
+---
+
+## Default Cache Configuration
+
+Define a global cache for all jobs and override it for specific jobs as needed:
+
+```yaml
+default:
+  cache: &global_cache
+    key: $CI_COMMIT_REF_SLUG
+    paths:
+      - node_modules/
+      - public/
+      - vendor/
+    policy: pull-push
+
+job:
+  cache:
+    <<: *global_cache
+    policy: pull  # Override policy for this job
+```
+
+---
+
+## Cache Policies
+
+| Policy    | Description                                            |
+| --------- | ------------------------------------------------------ |
+| pull      | Only fetch the cache, do not update it.                |
+| pull-push | Fetch the cache and update it after the job completes. |
+
+---
+
+## Cache Examples
+
+* **Per Job & Branch**
+
+```yaml
+cache:
+  key: "$CI_JOB_NAME-$CI_COMMIT_REF_SLUG"
+```
+
+* **Per Stage & Branch**
+
+```yaml
+cache:
+  key: "$CI_JOB_STAGE-$CI_COMMIT_REF_SLUG"
+```
+
+---
+
+## Conditional Cache Policy
+
+Update cache only on the default branch; otherwise, just pull:
+
+```yaml
+conditional-policy:
+  rules:
+    - if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
+      variables:
+        POLICY: pull-push
+    - if: $CI_COMMIT_BRANCH != $CI_DEFAULT_BRANCH
+      variables:
+        POLICY: pull
+  stage: build
+  cache:
+    key: gems
+    policy: $POLICY
+    paths:
+      - vendor/bundle
+  script:
+    - echo "This job pulls and pushes the cache depending on the branch"
+    - echo "Downloading dependencies..."
+```
+
+---
+
+## Cache Based on Lock Files
+
+Update cache automatically when `package-lock.json` changes:
+
+```yaml
+default:
+  cache:
+    key:
+      files:
+        - package-lock.json
+    paths:
+      - .npm/
+```
+
+**Tip**: This ensures your npm modules are always synced with the lock file.
+
+---
+
+## Summary
+
+* Use **branch-specific keys** for independent caches.
+* Use **fallback_keys** to share cache between branches.
+* **Policies** control whether cache is updated or only fetched.
+* Use **lock files** to trigger cache updates automatically.
+
+Caching effectively can dramatically reduce build times and maintain clean, efficient pipelines.
+

From 5bb174079eecf73d758fe45079cf61ce80b848d1 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Sat, 4 Oct 2025 12:40:39 +0330
Subject: [PATCH 100/116] gitlab cache added runner config for s3

---
 Code-Management/Gitlab/Gitlab-Cache.md | 76 ++++++++++++++++----------
 1 file changed, 48 insertions(+), 28 deletions(-)

diff --git a/Code-Management/Gitlab/Gitlab-Cache.md b/Code-Management/Gitlab/Gitlab-Cache.md
index b7c4461..79f2932 100644
--- a/Code-Management/Gitlab/Gitlab-Cache.md
+++ b/Code-Management/Gitlab/Gitlab-Cache.md
@@ -1,21 +1,21 @@
 # GitLab CI/CD Cache Guide
 
-GitLab provides a caching system for jobs to speed up pipelines by reusing dependencies like `node_modules`, Ruby gems, and other build artifacts. This guide covers how to configure and use caching effectively.
+GitLab CI/CD provides a caching mechanism to speed up pipeline execution by reusing dependencies and build artifacts such as `node_modules`, Ruby gems, or compiled binaries. This guide covers how to configure, optimize, and manage caching effectively.
 
 ---
 
-## Key Features
+## Key Features of GitLab Cache
 
-* **Cache Storage**: Data is saved in the GitLab Runner and can also be stored in external storage such as S3, MinIO, GCS, etc.
-* **Branch-Specific Caching**: Maintain separate caches per branch, job, or stage.
-* **Fallbacks**: Jobs can pull cache from other branches if the current branch does not have cache.
-* **Simple Cache**: Uses file locks and directory caching for efficiency.
+* **Cache Storage**: Cache data is stored in the GitLab Runner and can optionally be persisted in external storage such as S3, MinIO, Google Cloud Storage (GCS), or Azure Blob Storage.
+* **Branch-Specific Caching**: Create independent caches per branch, job, or pipeline stage to avoid conflicts.
+* **Fallbacks**: Jobs can retrieve cache from other branches if the current branch has no cache yet.
+* **Simple & Efficient**: Uses file locks and directory caching to maximize efficiency without complex configurations.
 
 ---
 
 ## Basic Cache Example
 
-Cache dependencies like Ruby gems and Yarn modules:
+A typical caching configuration for Ruby gems and Yarn modules:
 
 ```yaml
 test-job:
@@ -39,13 +39,34 @@ test-job:
 ```
 
 **Behavior**:
-If the lock file (`Gemfile.lock` or `yarn.lock`) changes, the cache is updated automatically.
+If the lock file (`Gemfile.lock` or `yarn.lock`) changes, the cache is updated automatically, ensuring dependencies remain consistent with the project.
 
 ---
 
-## Branch Cache with Fallbacks
+## Configuring GitLab Runner to Use S3 Cache
 
-When creating a new branch, it may not have a cache yet. You can pull from the default branch (e.g., `main` or `master`) or a global default cache:
+You can configure the GitLab Runner to save cache to S3 storage as follows:
+
+```toml
+[[runners]]
+  [runners.cache]
+    Type = "s3"
+    [runners.cache.s3]
+      ServerAddress = "s3.example.com"
+      AccessKey = "access-key"
+      SecretKey = "secret-key"
+      BucketName = "runner"
+      Insecure = true  # true = http, false = https
+    [runners.cache.gcs]
+    [runners.cache.azure]
+  [runners.docker]
+```
+
+---
+
+## Branch-Specific Cache with Fallbacks
+
+When a new branch does not yet have a cache, it can use fallback caches from other branches:
 
 ```yaml
 test-job:
@@ -67,7 +88,7 @@ test-job:
 
 ## Default Cache Configuration
 
-Define a global cache for all jobs and override it for specific jobs as needed:
+Define a global cache and override it per job as necessary:
 
 ```yaml
 default:
@@ -82,30 +103,30 @@ default:
 job:
   cache:
     <<: *global_cache
-    policy: pull  # Override policy for this job
+    policy: pull  # Overrides global policy for this job
 ```
 
 ---
 
 ## Cache Policies
 
-| Policy    | Description                                            |
-| --------- | ------------------------------------------------------ |
-| pull      | Only fetch the cache, do not update it.                |
-| pull-push | Fetch the cache and update it after the job completes. |
+| Policy    | Description                                       |
+| --------- | ------------------------------------------------- |
+| pull      | Fetches cache without updating it                 |
+| pull-push | Fetches cache and updates it after job completion |
 
 ---
 
 ## Cache Examples
 
-* **Per Job & Branch**
+**Per Job & Branch**:
 
 ```yaml
 cache:
   key: "$CI_JOB_NAME-$CI_COMMIT_REF_SLUG"
 ```
 
-* **Per Stage & Branch**
+**Per Stage & Branch**:
 
 ```yaml
 cache:
@@ -116,7 +137,7 @@ cache:
 
 ## Conditional Cache Policy
 
-Update cache only on the default branch; otherwise, just pull:
+Update cache only on the default branch while other branches only fetch:
 
 ```yaml
 conditional-policy:
@@ -142,7 +163,7 @@ conditional-policy:
 
 ## Cache Based on Lock Files
 
-Update cache automatically when `package-lock.json` changes:
+Automatically update cache when lock files change, e.g., `package-lock.json`:
 
 ```yaml
 default:
@@ -154,16 +175,15 @@ default:
       - .npm/
 ```
 
-**Tip**: This ensures your npm modules are always synced with the lock file.
+**Tip**: Using lock files ensures that cached dependencies are always consistent with the project’s declared versions.
 
 ---
 
-## Summary
+## Best Practices Summary
 
-* Use **branch-specific keys** for independent caches.
-* Use **fallback_keys** to share cache between branches.
-* **Policies** control whether cache is updated or only fetched.
-* Use **lock files** to trigger cache updates automatically.
-
-Caching effectively can dramatically reduce build times and maintain clean, efficient pipelines.
+* Use **branch-specific keys** for independent caches to avoid conflicts.
+* Use **fallback_keys** to share caches across branches.
+* Use **cache policies** to control whether cache is updated or only fetched.
+* Leverage **lock files** to trigger cache updates automatically.
 
+Proper caching can dramatically reduce build times, improve pipeline efficiency, and ensure consistent builds across branches and environments.

From 6e65d930006a331d21ee3061652bb76052ac0915 Mon Sep 17 00:00:00 2001
From: root <pirouz.radin@yahoo.com>
Date: Mon, 6 Oct 2025 14:23:41 +0330
Subject: [PATCH 101/116] nginx route proxy doc

---
 Web-Servers/Nginx/11-Route-Proxy.md | 119 ++++++++++++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 Web-Servers/Nginx/11-Route-Proxy.md

diff --git a/Web-Servers/Nginx/11-Route-Proxy.md b/Web-Servers/Nginx/11-Route-Proxy.md
new file mode 100644
index 0000000..d47e2b5
--- /dev/null
+++ b/Web-Servers/Nginx/11-Route-Proxy.md
@@ -0,0 +1,119 @@
+## 1. Purpose
+
+This document describes how **NGINX handles route mapping** when used as a reverse proxy.
+It explains how `location`, `proxy_pass`, and related directives determine the **final upstream URL** sent to backend services.
+
+---
+
+## 2. Core Directives
+
+### 2.1 `location`
+
+Defines which incoming request path should be matched.
+
+**Example**
+
+```nginx
+location /api/ { ... }
+```
+
+This block is triggered for any request beginning with `/api/`, such as `/api/users` or `/api/data/info`.
+
+---
+
+### 2.2 `proxy_pass`
+
+Defines the target backend (upstream) to which the request will be forwarded.
+
+The **syntax of `proxy_pass`** determines how the URI is rewritten.
+This is the most important aspect of route handling.
+
+---
+
+## 3. URI Rewriting Logic
+
+The effect of `proxy_pass` depends on the **presence of a trailing slash `/`** after the upstream URL.
+
+| Case                          | Configuration                                                      | Example Request | Upstream Request                  | Result                                                                  |
+| ----------------------------- | ------------------------------------------------------------------ | --------------- | --------------------------------- | ----------------------------------------------------------------------- |
+| **A. Trailing Slash Present** | `proxy_pass http://127.0.0.1:5000/;`                               | `/api/users`    | `http://127.0.0.1:5000/users`     | Keeps the part after `/api/`. **Recommended** for most reverse proxies. |
+| **B. No Trailing Slash**      | `proxy_pass http://127.0.0.1:5000;`                                | `/api/users`    | `http://127.0.0.1:5000/api/users` | Appends the full location path; can cause incorrect routing.            |
+| **C. Using Rewrite**          | `rewrite ^/api/(.*)$ /$1 break; proxy_pass http://127.0.0.1:5000;` | `/api/users`    | `http://127.0.0.1:5000/users`     | Manually removes `/api` prefix before forwarding.                       |
+
+---
+
+## 4. Recommended Routing Pattern
+
+A clean and predictable configuration for separate routes:
+
+```nginx
+server {
+    listen 80;
+    server_name example.com;
+
+    # Route for API
+    location /api/ {
+        proxy_pass http://127.0.0.1:5000/;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+
+    # Route for Frontend
+    location /app/ {
+        proxy_pass http://127.0.0.1:3000/;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+}
+```
+
+This configuration ensures:
+
+* `/api/...` → backend at port `5000`
+* `/app/...` → frontend at port `3000`
+* Path components after `/api/` or `/app/` are preserved correctly.
+
+---
+
+## 5. Common Routing Issues
+
+| Symptom                                             | Likely Cause                                               | Fix                                           |
+| --------------------------------------------------- | ---------------------------------------------------------- | --------------------------------------------- |
+| Backend receives wrong path (e.g. `/api/api/users`) | Missing trailing slash in `proxy_pass`                     | Add `/` to the end of the `proxy_pass` target |
+| Backend receives empty path                         | Using `rewrite` incorrectly or missing URI in `proxy_pass` | Verify the rewrite pattern and use `break`    |
+| Redirects loop or wrong host in backend             | Missing `proxy_set_header Host $host;`                     | Include required proxy headers                |
+| HTTPS backend errors                                | Backend expects HTTPS but `proxy_pass` uses HTTP           | Use `proxy_pass https://...;`                 |
+
+---
+
+## 6. Testing Routing
+
+Use `curl` to validate routing:
+
+```bash
+curl -v http://example.com/api/users
+```
+
+Check the backend logs to confirm that the incoming path matches the expected `/users`.
+
+Test configuration before reload:
+
+```bash
+sudo nginx -t
+sudo systemctl reload nginx
+```
+
+---
+
+## 7. Summary
+
+* The `location` directive defines which incoming route to match.
+* The `proxy_pass` directive determines how the URI is forwarded.
+* The **presence of a trailing slash** in `proxy_pass` is the key factor controlling route rewriting.
+* Optional `rewrite` rules can further customize paths.
+* Always test with `nginx -t` and verify backend behavior.
+

From fb8e743e4e4b170fcd6c346970cfd3fbe61f4a82 Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Mon, 6 Oct 2025 22:09:57 +0330
Subject: [PATCH 102/116] Create 12-Example-Config.md

---
 Web-Servers/Nginx/12-Example-Config.md | 115 +++++++++++++++++++++++++
 1 file changed, 115 insertions(+)
 create mode 100644 Web-Servers/Nginx/12-Example-Config.md

diff --git a/Web-Servers/Nginx/12-Example-Config.md b/Web-Servers/Nginx/12-Example-Config.md
new file mode 100644
index 0000000..70c4a52
--- /dev/null
+++ b/Web-Servers/Nginx/12-Example-Config.md
@@ -0,0 +1,115 @@
+# Nginx Reverse Proxy Configuration — `files.usethelinux.shop`
+
+## Overview
+
+This Nginx configuration serves two main purposes:
+
+1. **Static file listing** from `/srv/files/` under the `/nginx-files/` path.
+2. **Reverse proxy to MinIO** running on `http://127.0.0.1:9001` for all other requests.
+
+The configuration also sets headers to ensure proper client information forwarding, support for WebSockets, and correct host resolution.
+
+---
+
+## Server Block
+
+```nginx
+server {
+    listen 80;
+    server_name files.usethelinux.shop;
+
+    error_log /var/log/nginx/file-error.log warn;
+    access_log /var/log/nginx/file-access.log;
+```
+
+* **listen 80;** — The server listens on HTTP port 80.
+* **server_name files.usethelinux.shop;** — Responds to requests for this domain.
+* **error_log** and **access_log** — Define custom log files for debugging and access tracking.
+
+---
+
+## Location `/nginx-files/` — Static File Listing
+
+```nginx
+location /nginx-files/ {
+    alias /srv/files/;
+    autoindex on;
+    autoindex_exact_size off;
+    autoindex_localtime on;
+}
+```
+
+* **alias /srv/files/;** — Maps the URL path `/nginx-files/` to the filesystem path `/srv/files/`.
+* **autoindex on;** — Enables directory listing.
+* **autoindex_exact_size off;** — Shows file sizes in human-readable format instead of exact bytes.
+* **autoindex_localtime on;** — Displays file modification times in the server’s local timezone.
+
+---
+
+## Location `/` — MinIO Reverse Proxy
+
+```nginx
+location / {
+    proxy_pass http://127.0.0.1:9001;
+    proxy_http_version 1.1;
+    proxy_set_header Upgrade $http_upgrade;
+    proxy_set_header Connection "upgrade";
+    proxy_set_header Host $host;
+    proxy_set_header X-Real-IP $remote_addr;
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_set_header X-Forwarded-Proto $scheme;
+}
+```
+
+### proxy_pass
+
+* **proxy_pass [http://127.0.0.1:9001](http://127.0.0.1:9001);** — Forwards all requests to the MinIO server running on localhost port 9001.
+
+### proxy_http_version
+
+* **proxy_http_version 1.1;** — Ensures the proxy uses HTTP/1.1, required for WebSocket support and persistent connections.
+
+### proxy_set_header
+
+1. **Upgrade $http_upgrade;**
+
+   * Passes the `Upgrade` header from the client, needed for WebSocket connections.
+   * Allows MinIO (or any WebSocket-enabled service) to handle protocol upgrades properly.
+
+2. **Connection "upgrade";**
+
+   * Indicates that the connection may be upgraded (e.g., to WebSocket).
+   * Works with the `Upgrade` header to maintain persistent connections.
+
+3. **Host $host;**
+
+   * Sends the original `Host` header from the client to the upstream server.
+   * Ensures that MinIO knows which hostname was requested and can generate correct URLs.
+
+4. **X-Real-IP $remote_addr;**
+
+   * Forwards the client’s IP address to the upstream server.
+   * Useful for logging, rate limiting, and IP-based access control.
+
+5. **X-Forwarded-For $proxy_add_x_forwarded_for;**
+
+   * Maintains a list of all IP addresses the request has passed through (client → proxy → upstream).
+   * Helps upstream services identify the original client IP when multiple proxies are involved.
+
+6. **X-Forwarded-Proto $scheme;**
+
+   * Passes the original protocol (`http` or `https`) used by the client.
+   * Important for generating correct links, redirects, or enforcing HTTPS in the upstream service.
+
+---
+
+### Summary
+
+This configuration ensures:
+
+* Efficient serving of static files with directory listing.
+* Proper reverse proxying to MinIO with support for WebSockets.
+* Accurate client information forwarding for logging and security.
+* Compatibility with applications that depend on the original `Host` and protocol.
+
+

From da309f2d12109548bd78b162c5b7e3b5a924b7ef Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Mon, 6 Oct 2025 22:10:51 +0330
Subject: [PATCH 103/116] Update 12-Example-Config.md

---
 Web-Servers/Nginx/12-Example-Config.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Web-Servers/Nginx/12-Example-Config.md b/Web-Servers/Nginx/12-Example-Config.md
index 70c4a52..9f9e1d6 100644
--- a/Web-Servers/Nginx/12-Example-Config.md
+++ b/Web-Servers/Nginx/12-Example-Config.md
@@ -1,5 +1,4 @@
-# Nginx Reverse Proxy Configuration — `files.usethelinux.shop`
-
+# Nginx Reverse Proxy Configuration
 ## Overview
 
 This Nginx configuration serves two main purposes:

From 24c0327649a46b670f3bb65b5383fca9f993fa4d Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Mon, 6 Oct 2025 22:11:21 +0330
Subject: [PATCH 104/116] Update 12-Example-Config.md

---
 Web-Servers/Nginx/12-Example-Config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Web-Servers/Nginx/12-Example-Config.md b/Web-Servers/Nginx/12-Example-Config.md
index 9f9e1d6..074ce50 100644
--- a/Web-Servers/Nginx/12-Example-Config.md
+++ b/Web-Servers/Nginx/12-Example-Config.md
@@ -15,14 +15,14 @@ The configuration also sets headers to ensure proper client information forwardi
 ```nginx
 server {
     listen 80;
-    server_name files.usethelinux.shop;
+    server_name example.com;
 
     error_log /var/log/nginx/file-error.log warn;
     access_log /var/log/nginx/file-access.log;
 ```
 
 * **listen 80;** — The server listens on HTTP port 80.
-* **server_name files.usethelinux.shop;** — Responds to requests for this domain.
+* **server_name example.com;** — Responds to requests for this domain.
 * **error_log** and **access_log** — Define custom log files for debugging and access tracking.
 
 ---

From cf2e9f9691350438dbbd65c628c1f3510253a7cf Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Tue, 7 Oct 2025 23:14:45 +0330
Subject: [PATCH 105/116] crictl doc

---
 .../Kubernetes/Crtctl/main.md                 | 180 ++++++++++++++++++
 1 file changed, 180 insertions(+)
 create mode 100644 Containerization-Orchestration/Kubernetes/Crtctl/main.md

diff --git a/Containerization-Orchestration/Kubernetes/Crtctl/main.md b/Containerization-Orchestration/Kubernetes/Crtctl/main.md
new file mode 100644
index 0000000..2cd2a7e
--- /dev/null
+++ b/Containerization-Orchestration/Kubernetes/Crtctl/main.md
@@ -0,0 +1,180 @@
+# **crictl: CLI for CRI-Compatible Container Runtimes**
+
+## Overview
+
+`crictl` is a **command-line interface** for **Container Runtime Interface (CRI)**–compatible runtimes such as **containerd** and **CRI-O**, primarily used within Kubernetes environments.
+
+It provides node-level visibility and control over pods, containers, and images. While it resembles Docker CLI in syntax, it is designed for **debugging** and **inspection**, not for managing workloads outside Kubernetes control.
+
+`crictl` is part of the **[cri-tools](https://github.com/kubernetes-sigs/cri-tools)** project, which also includes `critest`.
+
+---
+
+## Installation
+
+1. Navigate to the [cri-tools releases page](https://github.com/kubernetes-sigs/cri-tools/releases) to find the version compatible with your Kubernetes or CRI runtime.
+2. Download and install `crictl`:
+
+   ```bash
+   VERSION="v1.33.0"
+   wget https://github.com/kubernetes-sigs/cri-tools/releases/download/$VERSION/crictl-$VERSION-linux-amd64.tar.gz
+   tar zxvf crictl-$VERSION-linux-amd64.tar.gz
+   sudo mv crictl /usr/local/bin/
+   ```
+
+   *(Adjust version and architecture as needed.)*
+3. Clean up the tarball if desired.
+4. Verify installation:
+
+   ```bash
+   crictl --version
+   ```
+
+---
+
+## Configuration and Endpoints
+
+`crictl` communicates with CRI runtimes using socket endpoints.
+
+### Configuration Methods
+
+You can configure endpoints via:
+
+* **Command-line flags**: `--runtime-endpoint`, `--image-endpoint`
+* **Environment variables**:
+  `CONTAINER_RUNTIME_ENDPOINT`, `IMAGE_SERVICE_ENDPOINT`
+* **Configuration file**: Default path `/etc/crictl.yaml`
+* **Custom config file**: Use `--config=<path>`
+
+### Example `/etc/crictl.yaml`
+
+```yaml
+runtime-endpoint: unix:///var/run/containerd/containerd.sock
+image-endpoint:  unix:///var/run/containerd/containerd.sock
+timeout: 10
+debug: true
+```
+
+If no endpoint is provided, `crictl` attempts to connect to a list of known sockets, which can slow operations.
+
+### Modifying Configuration
+
+```bash
+crictl config --set debug=true
+crictl config --get debug
+```
+
+Additional configuration parameters include:
+
+* `pull-image-on-create`
+* `disable-pull-on-run`
+
+---
+
+## Global Options
+
+| Flag                        | Description                                |
+| --------------------------- | ------------------------------------------ |
+| `-h`, `--help`              | Display help and usage information         |
+| `-v`, `--version`           | Display crictl and runtime version details |
+| `--runtime-endpoint <path>` | Specify CRI runtime socket                 |
+| `--image-endpoint <path>`   | Specify CRI image service socket           |
+| `--timeout <duration>`      | Connection timeout (e.g., `5s`)            |
+| `-D`, `--debug`             | Enable verbose output                      |
+| `--config <path>`           | Specify a custom config file               |
+
+---
+
+## Common Commands
+
+### Status and Information
+
+| Command          | Description                                           |
+| ---------------- | ----------------------------------------------------- |
+| `crictl version` | Display version and runtime API info                  |
+| `crictl info`    | Show runtime health, plugin states, and configuration |
+
+### Pods / Pod Sandboxes
+
+| Command                             | Description                        |
+| ----------------------------------- | ---------------------------------- |
+| `crictl pods`                       | List all pod sandboxes on the node |
+| `crictl inspectp <POD_ID>`          | Inspect a specific pod sandbox     |
+| `crictl runp <sandbox-config.json>` | Create a new pod sandbox           |
+| `crictl stopp <POD_ID>`             | Stop a pod sandbox                 |
+| `crictl rmp <POD_ID>`               | Remove a pod sandbox               |
+
+### Containers
+
+| Command                                                                | Description                              |
+| ---------------------------------------------------------------------- | ---------------------------------------- |
+| `crictl ps` / `crictl ps -a`                                           | List running / all containers            |
+| `crictl inspect <CONTAINER_ID>`                                        | Inspect a specific container             |
+| `crictl create <POD_ID> <container-config.json> <sandbox-config.json>` | Create a container in a pod              |
+| `crictl start <CONTAINER_ID>`                                          | Start a container                        |
+| `crictl exec -i -t <CONTAINER_ID> <command>`                           | Execute a command inside a container     |
+| `crictl stop <CONTAINER_ID>`                                           | Stop a running container                 |
+| `crictl rm <CONTAINER_ID>`                                             | Remove a stopped container               |
+| `crictl stats`                                                         | Show CPU and memory usage for containers |
+
+### Images
+
+| Command                   | Description                   |
+| ------------------------- | ----------------------------- |
+| `crictl images`           | List available images         |
+| `crictl inspecti <IMAGE>` | Inspect image metadata        |
+| `crictl pull <IMAGE>`     | Pull an image from a registry |
+| `crictl rmi <IMAGE>`      | Remove an image               |
+| `crictl load <tarball>`   | Load an image from a tar file |
+
+---
+
+## Best Practices and Caveats
+
+* **Kubelet cleanup:** Containers or pods created manually with `crictl` may be removed by the kubelet since they’re not managed by the Kubernetes control plane. Use for debugging only.
+* **Permissions:** Root privileges or socket access are often required to communicate with the runtime.
+* **Version compatibility:** Always match your `crictl` version to your Kubernetes or CRI runtime.
+* **Timeout tuning:** Adjust `--timeout` or configuration to avoid connection failures.
+* **Not a Docker replacement:** Although similar in command structure, `crictl` interacts directly with the CRI layer and may not support all Docker features.
+
+---
+
+## Example Debugging Workflow
+
+1. SSH into a Kubernetes node.
+2. Check runtime health:
+
+   ```bash
+   crictl info
+   crictl version
+   ```
+3. List pod sandboxes:
+
+   ```bash
+   crictl pods
+   ```
+4. Inspect a pod:
+
+   ```bash
+   crictl inspectp <POD_ID>
+   ```
+5. List and inspect containers:
+
+   ```bash
+   crictl ps -a
+   crictl inspect <CONTAINER_ID>
+   ```
+6. Execute into or inspect logs:
+
+   ```bash
+   crictl exec -it <CONTAINER_ID> sh
+   ```
+7. Clean up stuck containers or unused images:
+
+   ```bash
+   crictl stop <CONTAINER_ID>
+   crictl rm <CONTAINER_ID>
+   crictl rmi <IMAGE>
+   ```
+
+This workflow is typically used for **node-level debugging**, especially when `kubectl` cannot access or display runtime state.

From e65d9f43802c4eba7ca4297867a13c8fe1057ece Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Tue, 7 Oct 2025 23:18:48 +0330
Subject: [PATCH 106/116] update certbot doc

---
 Web-Servers/CertBot/certbot.md | 100 ++++++++++++++++++++++-----------
 1 file changed, 68 insertions(+), 32 deletions(-)

diff --git a/Web-Servers/CertBot/certbot.md b/Web-Servers/CertBot/certbot.md
index 9000c1c..8bd7153 100644
--- a/Web-Servers/CertBot/certbot.md
+++ b/Web-Servers/CertBot/certbot.md
@@ -1,54 +1,70 @@
-# 🔐 Certbot – SSL Certificate Management Guide
+# 🔐 Certbot 
 
 ## 📦 Install Certbot
 
 ```bash
-apt install certbot
+sudo apt update
+sudo apt install certbot python3-certbot-nginx -y
 ```
 
-Installs **Certbot**, the free tool to automatically obtain and manage SSL/TLS certificates from **Let's Encrypt**.
+*Installs Certbot and the Nginx plugin to automatically manage certificates.*
 
 ---
 
 ## 🖥️ Method 1 – Standalone Mode
 
 ```bash
-certbot certonly --standalone -d www.example.com
+sudo certbot certonly --standalone -d www.example.com
 ```
 
-💡 **Standalone mode** runs its own temporary web server to complete the verification.
+💡 **Standalone mode** runs its own temporary server for domain verification.
 
-* Use when no web server (Apache/Nginx) is running on the same port.
-* Certificates will be saved in:
+* Use if **Nginx is not running** on port 80/443.
+* Certificates saved in:
 
-  * All versions: `/etc/letsencrypt/archive/`
-  * Latest version (symlink): `/etc/letsencrypt/live/`
+  * `/etc/letsencrypt/live/<domain>/` → latest version (symlink)
+  * `/etc/letsencrypt/archive/<domain>/` → all versions
 
 ---
 
 ## 🌐 Method 2 – Webroot Mode
 
 ```bash
-certbot certonly --webroot --webroot-path <path> -d <domain>
+sudo certbot certonly --webroot -w /var/www/html -d www.example.com
 ```
 
-📌 **Webroot mode** places a verification file in your website's public directory.
+💡 **Webroot mode** places verification files in your website’s public folder.
 
-* `<path>` = your website's document root (e.g., `/var/www/html`)
-* Use when your site is already running and accessible.
+* `<path>` = Nginx document root
+* Use if Nginx is running and serving your site.
 
 ---
 
-## 🛠️ Method 3 – Manual DNS Challenge
+## 🛠️ Method 3 – Nginx Plugin (Auto Configuration)
 
 ```bash
-certbot certonly --manual --preferred-challenges dns -d <domain>
+sudo certbot --nginx -d www.example.com -d example.com
 ```
 
-🔹 **DNS mode** requires you to manually add a TXT record to your domain’s DNS.
+💡 **Nginx plugin** automatically:
 
-* Best for **wildcard** certificates (`*.example.com`)
-* Works even without a running web server.
+* Obtains SSL certificate
+* Configures HTTPS in Nginx
+* Adds HTTP → HTTPS redirect
+* Reloads Nginx
+
+---
+
+## 🌱 Method 4 – Manual DNS Challenge (Wildcard)
+
+```bash
+sudo certbot certonly --manual --preferred-challenges dns -d "*.example.com" -d example.com
+```
+
+💡 **DNS challenge** is required for wildcard certificates or if HTTP verification isn’t possible.
+
+* Add TXT record as instructed by Certbot
+* Works even if Nginx is down or port 80 is blocked
 
 ---
 
@@ -57,38 +73,58 @@ certbot certonly --manual --preferred-challenges dns -d <domain>
 ### Automatic Renewal
 
 ```bash
-certbot renew
+sudo certbot renew
 ```
 
-* Renews all certificates close to expiration.
+* Renews all certificates nearing expiration
 
 ### Force Renewal
 
 ```bash
-certbot renew --force-renewal
+sudo certbot renew --force-renewal
 ```
 
-* Renews certificates **immediately**, even if not expiring soon.
+* Immediately renews certificates, even if not near expiry
+
+### Test Renewal
+
+```bash
+sudo certbot renew --dry-run
+```
+
+* Tests renewal without making changes
 
 ---
 
-## 📅 Tips
-
-* Certificates expire every **90 days** — always set up **auto-renew**.
-* Test renewal without changes:
+## 🔄 Reload Nginx After Renewal
 
 ```bash
-certbot renew --dry-run
+sudo systemctl reload nginx
 ```
 
-* Restart your web server after renewal to apply new certificates:
+* Apply new certificates without downtime
+
+*Tip:* You can add a **deploy-hook** for automatic reload:
 
 ```bash
-systemctl restart nginx
-# or
-systemctl restart apache2
+sudo certbot renew --deploy-hook "systemctl reload nginx"
 ```
 
 ---
 
-✨ **With Certbot, your HTTPS setup can be fast, free, and automatic!** 🔒🚀
+## 📅 Tips & Best Practices
+
+* Certificates expire every **90 days** — enable **auto-renewal**.
+* Keep `/etc/letsencrypt/` **backed up** (contains keys and configs).
+* Use **staging** for testing to avoid hitting rate limits:
+
+```bash
+sudo certbot --staging --nginx -d www.example.com
+```
+
+* Monitor renewal logs: `/var/log/letsencrypt/letsencrypt.log`
+
+---
+
+✨ **Result:** Fully automated HTTPS for Nginx with Let’s Encrypt certificates. Fast, free, and secure! 🔒🚀
+

From 80dab9ae5f129d951c7bcaeeb9ee009307bf61d3 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Wed, 8 Oct 2025 20:15:41 +0330
Subject: [PATCH 107/116] update pv & pvc doc

---
 .../Kubernetes/Storage/Pv.md                  | 143 +++++++++++-------
 1 file changed, 90 insertions(+), 53 deletions(-)

diff --git a/Containerization-Orchestration/Kubernetes/Storage/Pv.md b/Containerization-Orchestration/Kubernetes/Storage/Pv.md
index 9a8138a..935fe4f 100644
--- a/Containerization-Orchestration/Kubernetes/Storage/Pv.md
+++ b/Containerization-Orchestration/Kubernetes/Storage/Pv.md
@@ -1,77 +1,95 @@
-# 🌐 Kubernetes Persistent Volumes (PV) Cheat Sheet
+# Kubernetes Persistent Volumes (PV) Cheat Sheet
 
-## 📦 What is a Persistent Volume (PV)?
+## What is a Persistent Volume (PV)?
 
 A **Persistent Volume (PV)** is a piece of storage in a Kubernetes cluster that can be:
 
-- **Pre-provisioned** by an administrator, or  
-- **Dynamically provisioned** using a **StorageClass**.
+* **Pre-provisioned** by an administrator, or
+* **Dynamically provisioned** using a **StorageClass**.
 
-> PVs allow data to **persist beyond the lifecycle of individual Pods**.
+PVs allow data to **persist beyond the lifecycle of individual Pods**.
 
 ---
 
-## 📁 PV Storage Options
+## PV Storage Options
 
-### 1. **HostPath**
-- Mounts a file or directory from the host node’s filesystem into a Pod.
-- Only suitable for **single-node testing or development** environments.
+### 1. HostPath
 
-### 2. **Persistent Volume (PV) & Persistent Volume Claim (PVC)**
-- **PV**: Represents the actual physical or virtual storage resource.
-- **PVC**: A user's request for specific storage resources and access modes.
+* Mounts a file or directory from the host node’s filesystem into a Pod.
+* Suitable **only for local development or single-node clusters** such as Minikube or Kind.
+* Not recommended for production workloads.
+
+### 2. NFS
+
+* Network File System; allows multiple Pods and nodes to share storage.
+* Recommended for shared or distributed environments.
+
+### 3. Cloud Volumes
+
+* **AWS:** `awsElasticBlockStore`
+* **GCP:** `gcePersistentDisk`
+* **Azure:** `azureDisk` or `azureFile`
+* **CSI Drivers:** Preferred modern approach for all major clouds and on-prem solutions.
 
 ---
 
-## 🧱 Kubernetes Storage Architecture
+## Kubernetes Storage Architecture
 
-1. **Persistent Volume (PV)** – The actual storage unit, managed by the admin or provisioned dynamically.  
-2. **Persistent Volume Claim (PVC)** – A user’s request for a certain amount and type of storage.
+1. **Persistent Volume (PV)** – Represents the actual storage resource, managed by the cluster admin or a dynamic provisioner.
+2. **Persistent Volume Claim (PVC)** – A user request for storage with specific size and access requirements.
+3. **StorageClass** – Defines how dynamic provisioning should occur (provisioner, reclaim policy, parameters).
 
 ---
 
-## 🔄 PV Lifecycle Phases
+## PV Lifecycle Phases
 
-| **State**     | **Description**                             |
-|---------------|---------------------------------------------|
-| Provisioning  | PV is being created or initialized.         |
-| Binding       | PV is bound to a PVC.                       |
-| Using         | PV is in use by a Pod.                      |
-| Releasing     | PVC is deleted; PV becomes unbound.         |
-| Reclaiming    | Based on reclaim policy:                    |
-|               | - `Delete`: Remove the storage.             |
-|               | - `Recycle`: Basic scrub (deprecated).      |
-|               | - `Retain`: Manual cleanup required.        |
+| State         | Description                                              |
+| ------------- | -------------------------------------------------------- |
+| **Available** | PV is ready to be bound.                                 |
+| **Bound**     | PV is bound to a PVC.                                    |
+| **Released**  | PVC was deleted; PV is unbound but data may still exist. |
+| **Failed**    | Automatic cleanup failed.                                |
+
+### Reclaim Policies:
+
+* **Delete:** Removes the underlying storage resource.
+* **Retain:** Keeps data for manual recovery.
+* **Recycle:** Deprecated (previously used to scrub the volume).
 
 ---
 
-## 🔒 PV Access Modes
+## PV Access Modes
 
-| **Mode**   | **Description**                                 |
-|------------|-------------------------------------------------|
-| `RWO`      | **ReadWriteOnce** – One node can read/write.    |
-| `ROX`      | **ReadOnlyMany** – Multiple nodes can read.     |
-| `RWX`      | **ReadWriteMany** – Multiple nodes can read/write. |
-| `RWOP`     | **ReadWriteOncePod** – Only one Pod can mount it with read/write access. |
+| Mode                      | Description                                                          |
+| ------------------------- | -------------------------------------------------------------------- |
+| `ReadWriteOnce` (RWO)     | One node can read/write.                                             |
+| `ReadOnlyMany` (ROX)      | Many nodes can read.                                                 |
+| `ReadWriteMany` (RWX)     | Many nodes can read/write.                                           |
+| `ReadWriteOncePod` (RWOP) | Only one Pod can mount it with read/write access (Kubernetes ≥1.22). |
 
 ---
 
-## 🛠️ CLI Commands to Manage PVs & PVCs
+## CLI Commands to Manage PVs & PVCs
 
 ```bash
 # List all Persistent Volumes
 kubectl get pv
 
 # List all Persistent Volume Claims
-kubectl get pvc
+kubectl get pvc -A
 
-# Edit a PVC
-kubectl edit pvc -n <namespace> <pvc-name>
+# Describe a specific PV or PVC
+kubectl describe pv <pv-name>
+kubectl describe pvc <pvc-name> -n <namespace>
+
+# Delete a PV or PVC
+kubectl delete pv <pv-name>
+kubectl delete pvc <pvc-name> -n <namespace>
 ```
 
 ---
 
-## 🚀 Example: Deployment with `hostPath` Volume
+## Example: Deployment with `hostPath` Volume
 
 ```yaml
 apiVersion: apps/v1
@@ -83,11 +101,11 @@ spec:
   replicas: 3
   selector:
     matchLabels:
-      name: nginx
+      app: nginx
   template:
     metadata:
       labels:
-        name: nginx
+        app: nginx
     spec:
       containers:
         - name: nginx
@@ -104,18 +122,15 @@ spec:
             type: DirectoryOrCreate
 ```
 
-### Valid `hostPath` Types:
-- `DirectoryOrCreate`
-- `Directory`
-- `FileOrCreate`
-- `File`
-- `Socket`
-- `CharDevice`
-- `BlockDevice`
+**Valid `hostPath` Types:**
+`DirectoryOrCreate`, `Directory`, `FileOrCreate`, `File`, `Socket`, `CharDevice`, `BlockDevice`
 
 ---
 
-## 📄 Example: Static Persistent Volume (PV)
+## Example: Static Persistent Volume (PV)
+
+**Important:** A PV **must specify a volume source type** (this was the cause of your validation error).
+For example, this corrected PV uses `hostPath`:
 
 ```yaml
 apiVersion: v1
@@ -128,11 +143,14 @@ spec:
   accessModes:
     - ReadWriteMany
   persistentVolumeReclaimPolicy: Retain
+  storageClassName: manual
+  hostPath:
+    path: /mnt/data/pv001
 ```
 
 ---
 
-## 📄 Example: Persistent Volume Claim (PVC)
+## Example: Persistent Volume Claim (PVC)
 
 ```yaml
 apiVersion: v1
@@ -146,16 +164,18 @@ spec:
   resources:
     requests:
       storage: 64Mi
+  storageClassName: manual
 ```
 
-> ✅ To bind a PVC to a specific PV, add `volumeName: <pv-name>` in the PVC spec:
+To bind this PVC to a specific PV manually:
+
 ```yaml
 volumeName: pv001
 ```
 
 ---
 
-## 🌐 NFS-Based Persistent Volume
+## NFS-Based Persistent Volume
 
 ### Persistent Volume (PV)
 
@@ -199,7 +219,7 @@ spec:
 
 ---
 
-## 🏗️ Static StorageClass for Pre-Provisioned Volumes
+## Static StorageClass for Pre-Provisioned Volumes
 
 ```yaml
 apiVersion: storage.k8s.io/v1
@@ -207,4 +227,21 @@ kind: StorageClass
 metadata:
   name: nginx-files
 provisioner: kubernetes.io/no-provisioner
+volumeBindingMode: WaitForFirstConsumer
+reclaimPolicy: Retain
 ```
+
+---
+
+## Recommended Additions
+
+1. **Always include `storageClassName`** to ensure predictable binding.
+2. **Set `volumeBindingMode: WaitForFirstConsumer`** in StorageClasses for node-aware provisioning.
+3. **Avoid using `hostPath` in multi-node clusters**; use NFS or CSI drivers.
+4. **Check events** for troubleshooting PV/PVC binding:
+
+   ```bash
+   kubectl describe pvc <pvc-name> -n <namespace>
+   ```
+5. **Automate cleanup** with proper reclaim policies or storage lifecycle controllers.
+

From 564fa3c97fc8f696e4f8d0b3ff79886b6d3dc55b Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Wed, 8 Oct 2025 20:16:21 +0330
Subject: [PATCH 108/116] change pv doc name

---
 .../Kubernetes/Storage/{Pv.md => pv-pvc.md}                       | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename Containerization-Orchestration/Kubernetes/Storage/{Pv.md => pv-pvc.md} (100%)

diff --git a/Containerization-Orchestration/Kubernetes/Storage/Pv.md b/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
similarity index 100%
rename from Containerization-Orchestration/Kubernetes/Storage/Pv.md
rename to Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md

From 34d19fe29e09f9307bca754f0f3998cdda9f0e69 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Wed, 8 Oct 2025 23:54:00 +0330
Subject: [PATCH 109/116] update pvc and pvc doc

---
 .../Kubernetes/Storage/pv-pvc.md              | 157 +++++++++++-------
 1 file changed, 94 insertions(+), 63 deletions(-)

diff --git a/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md b/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
index 935fe4f..3cba506 100644
--- a/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
+++ b/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
@@ -1,81 +1,80 @@
-# Kubernetes Persistent Volumes (PV) Cheat Sheet
+# **Kubernetes Persistent Volumes (PV) – Technical Reference Guide**
 
-## What is a Persistent Volume (PV)?
+## **1. Overview**
 
-A **Persistent Volume (PV)** is a piece of storage in a Kubernetes cluster that can be:
+A **Persistent Volume (PV)** is a storage resource in Kubernetes that allows data to persist beyond the lifecycle of Pods.
+Persistent Volumes can be:
 
-* **Pre-provisioned** by an administrator, or
+* **Pre-provisioned** by a cluster administrator, or
 * **Dynamically provisioned** using a **StorageClass**.
 
-PVs allow data to **persist beyond the lifecycle of individual Pods**.
-
 ---
 
-## PV Storage Options
+## **2. PV Storage Options**
 
-### 1. HostPath
+### **2.1 HostPath**
 
-* Mounts a file or directory from the host node’s filesystem into a Pod.
-* Suitable **only for local development or single-node clusters** such as Minikube or Kind.
-* Not recommended for production workloads.
+* Mounts a directory or file from the host node’s filesystem into a Pod.
+* Suitable only for **local development** or **single-node clusters** (e.g., Minikube, Kind).
+* **Not recommended** for production environments.
 
-### 2. NFS
+### **2.2 NFS**
 
-* Network File System; allows multiple Pods and nodes to share storage.
-* Recommended for shared or distributed environments.
+* Uses Network File System (NFS) to allow multiple Pods and nodes to share storage.
+* Recommended for **shared or distributed** setups.
 
-### 3. Cloud Volumes
+### **2.3 Cloud Volumes**
 
 * **AWS:** `awsElasticBlockStore`
 * **GCP:** `gcePersistentDisk`
 * **Azure:** `azureDisk` or `azureFile`
-* **CSI Drivers:** Preferred modern approach for all major clouds and on-prem solutions.
+* **CSI Drivers:** Preferred for all modern cloud and on-prem environments.
 
 ---
 
-## Kubernetes Storage Architecture
+## **3. Kubernetes Storage Architecture**
 
-1. **Persistent Volume (PV)** – Represents the actual storage resource, managed by the cluster admin or a dynamic provisioner.
-2. **Persistent Volume Claim (PVC)** – A user request for storage with specific size and access requirements.
-3. **StorageClass** – Defines how dynamic provisioning should occur (provisioner, reclaim policy, parameters).
+1. **Persistent Volume (PV):** Represents the actual storage resource, either statically created or dynamically provisioned.
+2. **Persistent Volume Claim (PVC):** A user request for storage of specific size and access modes.
+3. **StorageClass:** Defines dynamic provisioning behavior (provisioner, reclaim policy, parameters).
 
 ---
 
-## PV Lifecycle Phases
+## **4. PV Lifecycle Phases**
 
-| State         | Description                                              |
-| ------------- | -------------------------------------------------------- |
-| **Available** | PV is ready to be bound.                                 |
-| **Bound**     | PV is bound to a PVC.                                    |
-| **Released**  | PVC was deleted; PV is unbound but data may still exist. |
-| **Failed**    | Automatic cleanup failed.                                |
+| **State**     | **Description**                                  |
+| ------------- | ------------------------------------------------ |
+| **Available** | PV is ready to be bound to a claim.              |
+| **Bound**     | PV is bound to a PVC.                            |
+| **Released**  | PVC was deleted; PV is unbound but retains data. |
+| **Failed**    | Automatic cleanup failed.                        |
 
-### Reclaim Policies:
+### **Reclaim Policies**
 
-* **Delete:** Removes the underlying storage resource.
-* **Retain:** Keeps data for manual recovery.
-* **Recycle:** Deprecated (previously used to scrub the volume).
+* **Delete:** Deletes the underlying storage resource.
+* **Retain:** Keeps the data for manual recovery.
+* **Recycle:** Deprecated (was used to scrub the volume).
 
 ---
 
-## PV Access Modes
+## **5. PV Access Modes**
 
-| Mode                      | Description                                                          |
-| ------------------------- | -------------------------------------------------------------------- |
-| `ReadWriteOnce` (RWO)     | One node can read/write.                                             |
-| `ReadOnlyMany` (ROX)      | Many nodes can read.                                                 |
-| `ReadWriteMany` (RWX)     | Many nodes can read/write.                                           |
-| `ReadWriteOncePod` (RWOP) | Only one Pod can mount it with read/write access (Kubernetes ≥1.22). |
+| **Access Mode**           | **Description**                                             |
+| ------------------------- | ----------------------------------------------------------- |
+| `ReadWriteOnce` (RWO)     | Volume can be mounted as read-write by a single node.       |
+| `ReadOnlyMany` (ROX)      | Volume can be mounted read-only by multiple nodes.          |
+| `ReadWriteMany` (RWX)     | Volume can be mounted as read-write by multiple nodes.      |
+| `ReadWriteOncePod` (RWOP) | Volume can be mounted read-write by a single Pod. (≥ v1.22) |
 
 ---
 
-## CLI Commands to Manage PVs & PVCs
+## **6. CLI Commands**
 
 ```bash
 # List all Persistent Volumes
 kubectl get pv
 
-# List all Persistent Volume Claims
+# List all Persistent Volume Claims (across all namespaces)
 kubectl get pvc -A
 
 # Describe a specific PV or PVC
@@ -89,7 +88,7 @@ kubectl delete pvc <pvc-name> -n <namespace>
 
 ---
 
-## Example: Deployment with `hostPath` Volume
+## **7. Example: Deployment with HostPath Volume**
 
 ```yaml
 apiVersion: apps/v1
@@ -122,15 +121,12 @@ spec:
             type: DirectoryOrCreate
 ```
 
-**Valid `hostPath` Types:**
+**Valid `hostPath` types:**
 `DirectoryOrCreate`, `Directory`, `FileOrCreate`, `File`, `Socket`, `CharDevice`, `BlockDevice`
 
 ---
 
-## Example: Static Persistent Volume (PV)
-
-**Important:** A PV **must specify a volume source type** (this was the cause of your validation error).
-For example, this corrected PV uses `hostPath`:
+## **8. Example: Static Persistent Volume (PV)**
 
 ```yaml
 apiVersion: v1
@@ -150,7 +146,7 @@ spec:
 
 ---
 
-## Example: Persistent Volume Claim (PVC)
+## **9. Example: Persistent Volume Claim (PVC)**
 
 ```yaml
 apiVersion: v1
@@ -165,19 +161,14 @@ spec:
     requests:
       storage: 64Mi
   storageClassName: manual
-```
-
-To bind this PVC to a specific PV manually:
-
-```yaml
-volumeName: pv001
+  volumeName: pv001
 ```
 
 ---
 
-## NFS-Based Persistent Volume
+## **10. Example: NFS-Based PV and PVC**
 
-### Persistent Volume (PV)
+### **Persistent Volume (PV)**
 
 ```yaml
 apiVersion: v1
@@ -199,7 +190,7 @@ spec:
     server: 192.168.6.160
 ```
 
-### Persistent Volume Claim (PVC)
+### **Persistent Volume Claim (PVC)**
 
 ```yaml
 apiVersion: v1
@@ -219,7 +210,7 @@ spec:
 
 ---
 
-## Static StorageClass for Pre-Provisioned Volumes
+## **11. Example: Static StorageClass**
 
 ```yaml
 apiVersion: storage.k8s.io/v1
@@ -233,15 +224,55 @@ reclaimPolicy: Retain
 
 ---
 
-## Recommended Additions
+## **12. Example: Nginx Deployment Using PVC**
 
-1. **Always include `storageClassName`** to ensure predictable binding.
-2. **Set `volumeBindingMode: WaitForFirstConsumer`** in StorageClasses for node-aware provisioning.
-3. **Avoid using `hostPath` in multi-node clusters**; use NFS or CSI drivers.
-4. **Check events** for troubleshooting PV/PVC binding:
+```yaml
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+  name: nginx
+  namespace: web-app
+spec:
+  replicas: 1
+  selector:
+    matchLabels:
+      app_type: nginx-web
+  template:
+    metadata:
+      labels:
+        app_type: nginx-web
+    spec:
+      containers:
+        - name: nginx
+          image: nginx:latest
+          ports:
+            - containerPort: 80
+          volumeMounts:
+            - name: nginx-configs-volume
+              mountPath: /etc/nginx/conf.d/default.conf
+              subPath: reverse_proxy.conf
+            - name: nginx-logs-volume
+              mountPath: /var/log/nginx
+      volumes:
+        - name: nginx-configs-volume
+          configMap:
+            name: nginx-configs
+        - name: nginx-logs-volume
+          persistentVolumeClaim:
+            claimName: nginx-pvc
+```
+
+---
+
+## **13. Best Practices and Recommendations**
+
+1. **Always specify `storageClassName`** for predictable PV/PVC binding.
+2. **Use `volumeBindingMode: WaitForFirstConsumer`** to ensure node-aware provisioning.
+3. **Avoid `hostPath`** in multi-node or production clusters; use NFS or CSI drivers instead.
+4. **Monitor events** for troubleshooting binding issues:
 
    ```bash
    kubectl describe pvc <pvc-name> -n <namespace>
    ```
-5. **Automate cleanup** with proper reclaim policies or storage lifecycle controllers.
+5. **Implement proper reclaim policies** or automated cleanup mechanisms for storage lifecycle management.
 

From 8565b4051e9f08a1e51fade738f673851a28e4f8 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Thu, 9 Oct 2025 13:10:37 +0330
Subject: [PATCH 110/116] added redis py code

---
 Caching/redis/Codes/Simple_python.py | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)
 create mode 100644 Caching/redis/Codes/Simple_python.py

diff --git a/Caching/redis/Codes/Simple_python.py b/Caching/redis/Codes/Simple_python.py
new file mode 100644
index 0000000..6bf4e9f
--- /dev/null
+++ b/Caching/redis/Codes/Simple_python.py
@@ -0,0 +1,22 @@
+import redis
+
+method=int(input("Enter Method: (1.Read/2.Write): "))
+
+r = redis.Redis(host="ip", port=6379,db=0)
+
+
+if (method == 1):
+    key=str(input("enter key name: "))
+    value=r.get(key)
+    if value == None:
+        print("Undefined Key")
+        exit
+    else:
+        print(value.decode('utf-8'))
+elif (method == 2):
+    key=str(input("enter key name: "))
+    value=str(input("enter value: "))
+    r.set(key,value)
+else:
+    print("Incorrect Input")
+    exit
\ No newline at end of file

From 090912bd637eb425cd67b994ef14b06eed04b7a1 Mon Sep 17 00:00:00 2001
From: RadinPirouz <pirouz.radin@yahoo.com>
Date: Wed, 15 Oct 2025 11:25:32 +0330
Subject: [PATCH 111/116] temp code for doc

---
 Caching/redis/Codes/api-json.py               |  28 +++
 Caching/redis/Codes/api-set-get.py            |  26 +++
 .../Codes/{Simple_python.py => set-get.py}    |   0
 Caching/redis/python-redis.md                 | 172 ++++++++++++++++++
 Databases/Mariadb/python-mysql.py             |  22 +++
 5 files changed, 248 insertions(+)
 create mode 100644 Caching/redis/Codes/api-json.py
 create mode 100644 Caching/redis/Codes/api-set-get.py
 rename Caching/redis/Codes/{Simple_python.py => set-get.py} (100%)
 create mode 100644 Caching/redis/python-redis.md
 create mode 100644 Databases/Mariadb/python-mysql.py

diff --git a/Caching/redis/Codes/api-json.py b/Caching/redis/Codes/api-json.py
new file mode 100644
index 0000000..9e1b6d4
--- /dev/null
+++ b/Caching/redis/Codes/api-json.py
@@ -0,0 +1,28 @@
+from fastapi import FastAPI
+from pydantic import BaseModel
+import redis
+
+# Connect to Redis
+r = redis.Redis(host="192.168.6.160", port=30553, db=0, decode_responses=True)
+
+app = FastAPI()
+
+# For sending JSON data
+class Item(BaseModel):
+    key: str
+    value: str | None = None   # make value optional
+
+@app.get("/")
+def home():
+    return {"message": "Redis API is working!"}
+
+# Set key/value using JSON body
+@app.post("/set")
+def set_json(item: Item):
+    r.set(item.key, item.value)
+    return {"message": f"Saved {item.key} = {item.value}"}
+
+@app.post("/get")
+def get_json(item: Item):
+    value = r.get(item.key)
+    return {"Key": f"{value}"}
\ No newline at end of file
diff --git a/Caching/redis/Codes/api-set-get.py b/Caching/redis/Codes/api-set-get.py
new file mode 100644
index 0000000..077adea
--- /dev/null
+++ b/Caching/redis/Codes/api-set-get.py
@@ -0,0 +1,26 @@
+from fastapi import FastAPI
+import redis
+
+# connect to redis (make sure redis is running locally)
+r = redis.Redis(host="localhost", port=6379, db=0, decode_responses=True)
+
+app = FastAPI()
+
+@app.get("/")
+def home():
+    return {"message": "Redis API is working!"}
+
+# Set a key/value
+@app.post("/set/{key}/{value}")
+def set_key(key: str, value: str):
+    r.set(key, value)
+    return {"message": f"Key '{key}' set with value '{value}'"}
+
+# Get a key/value
+@app.get("/get/{key}")
+def get_key(key: str):
+    value = r.get(key)
+    if value:
+        return {"key": key, "value": value}
+    else:
+        return {"error": f"Key '{key}' not found"}
diff --git a/Caching/redis/Codes/Simple_python.py b/Caching/redis/Codes/set-get.py
similarity index 100%
rename from Caching/redis/Codes/Simple_python.py
rename to Caching/redis/Codes/set-get.py
diff --git a/Caching/redis/python-redis.md b/Caching/redis/python-redis.md
new file mode 100644
index 0000000..363b4dc
--- /dev/null
+++ b/Caching/redis/python-redis.md
@@ -0,0 +1,172 @@
+# Python + Redis Quick Guide
+
+This document explains how to set up Python, connect to Redis, and perform basic cache operations.
+
+---
+
+## 1. Setup
+
+Install Python and create a virtual environment:
+
+```bash
+sudo apt install python3-full
+python3 -m venv .venv
+source .venv/bin/activate
+```
+
+---
+
+## 2. Connect and Test Redis Connection
+
+```python
+import redis
+
+r = redis.Redis(host='localhost', port=6379, db=0)
+print(r.ping())  # Should print True
+```
+
+**Expected Output:**
+
+```
+True
+```
+
+---
+
+## 3. Caching Scenario Example
+
+This example demonstrates caching data in Redis with a TTL (Time To Live).
+
+```python
+import redis
+import time
+
+r = redis.Redis(host='localhost', port=6379, db=0)
+
+def get_data_from_db():
+    print("Fetching from DB...")
+    time.sleep(2)  # Simulate slow query
+    return {"user": "alice", "age": 30}
+
+def get_user(user_id):
+    cache_key = f"user:{user_id}"
+    
+    # Check cache first
+    cached = r.get(cache_key)
+    if cached:
+        print("Cache hit")
+        return eval(cached)
+    
+    # Fetch from DB
+    data = get_data_from_db()
+    
+    # Store in Redis with TTL (10 seconds)
+    r.set(cache_key, str(data), ex=10)
+    return data
+
+print(get_user(1))
+print(get_user(1))  # Should hit cache
+```
+
+---
+
+## 4. Connect, Set, and Get Example
+
+```python
+import redis
+
+r = redis.Redis(host="192.168.6.160", port=6379, db=0)
+
+r.set('name', 'radin')
+
+name = r.get('name')
+print(name)
+print(name.decode("utf-8"))
+```
+
+---
+
+## 5. Interactive Read/Write Example
+
+```python
+import redis
+
+method = int(input("Enter Method: (1.Read/2.Write) "))
+
+r = redis.Redis(host="192.168.6.160", port=6379, db=0)
+
+if method == 1:
+    key = str(input("Enter key name: "))
+    value = r.get(key)
+    if value is None:
+        print("Undefined Key")
+    else:
+        print(value)
+elif method == 2:
+    key = str(input("Enter key name: "))
+    value = str(input("Enter value: "))
+    r.set(key, value)
+else:
+    print("Incorrect Input")
+```
+
+---
+
+## 6. Professional Version (Improved Code)
+
+```python
+import redis
+import sys
+
+def connect_redis(host="192.168.6.160", port=6379, db=0):
+    """Establish a connection to Redis."""
+    try:
+        client = redis.Redis(host=host, port=port, db=db, decode_responses=True)
+        # Test connection
+        client.ping()
+        return client
+    except redis.ConnectionError as e:
+        print(f"Error connecting to Redis: {e}")
+        sys.exit(1)
+
+def read_key(client):
+    """Read a key from Redis."""
+    key = input("Enter key name: ").strip()
+    value = client.get(key)
+    if value is None:
+        print("Undefined Key")
+    else:
+        print(f"Value: {value}")
+
+def write_key(client):
+    """Write a key-value pair to Redis."""
+    key = input("Enter key name: ").strip()
+    value = input("Enter value: ").strip()
+    client.set(key, value)
+    print(f"Successfully set key '{key}' with value '{value}'.")
+
+def main():
+    client = connect_redis()
+
+    print("Select Method:")
+    print("1. Read")
+    print("2. Write")
+    
+    try:
+        method = int(input("Enter method (1 or 2): ").strip())
+    except ValueError:
+        print("Invalid input. Please enter 1 or 2.")
+        sys.exit(1)
+
+    if method == 1:
+        read_key(client)
+    elif method == 2:
+        write_key(client)
+    else:
+        print("Incorrect input. Please enter 1 or 2.")
+        sys.exit(1)
+
+if __name__ == "__main__":
+    main()
+```
+
diff --git a/Databases/Mariadb/python-mysql.py b/Databases/Mariadb/python-mysql.py
new file mode 100644
index 0000000..d69a937
--- /dev/null
+++ b/Databases/Mariadb/python-mysql.py
@@ -0,0 +1,22 @@
+import mysql.connector
+
+# Connect to the database
+conn = mysql.connector.connect(
+    host="localhost",
+    user="your_user",
+    password="your_password",
+    database="your_database"
+)
+
+cursor = conn.cursor()
+
+# Run a query
+cursor.execute("SELECT * FROM your_table;")
+
+# Fetch and print results
+for row in cursor.fetchall():
+    print(row)
+
+# Close connection
+cursor.close()
+conn.close()

From 9ec8d268ca3cc23c0c96f56a925e7c802876eaab Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Sun, 9 Nov 2025 11:11:43 +0330
Subject: [PATCH 112/116] Update 11-tar.md

---
 Linux/Basic Administration/11-tar.md | 68 ++++++++++++++++------------
 1 file changed, 40 insertions(+), 28 deletions(-)

diff --git a/Linux/Basic Administration/11-tar.md b/Linux/Basic Administration/11-tar.md
index d574979..4f637ed 100644
--- a/Linux/Basic Administration/11-tar.md	
+++ b/Linux/Basic Administration/11-tar.md	
@@ -1,6 +1,6 @@
-# 📦 Linux Compression & Archiving Cheatsheet
+# Linux Compression & Archiving Cheatsheet
 
-## 🔧 Tar Command Basics
+## Tar Command Basics
 
 The `tar` command is used to create, extract, and manage archive files.
 
@@ -10,16 +10,20 @@ The `tar` command is used to create, extract, and manage archive files.
 tar [options] [archive_name.tar] [file(s)/directory]
 ```
 
-### 🛠 Create a `.tar` Archive
+---
+
+### Create a `.tar` Archive
 
 ```bash
 tar -cf archive_file.tar file1 file2 dir1
 ```
 
+**Options:**
+
 * `-c`: Create a new archive
 * `-f`: Specify the archive file name
 
-### 🛠 Create with Verbose Output
+### Create with Verbose Output
 
 ```bash
 tar -cvf archive_file.tar file1 file2 dir1
@@ -27,12 +31,14 @@ tar -cvf archive_file.tar file1 file2 dir1
 
 * `-v`: Verbose mode (shows progress)
 
-### 📂 Extract a `.tar` Archive
+### Extract a `.tar` Archive
 
 ```bash
 tar -xf archive_file.tar
 ```
 
+or
+
 ```bash
 tar -xvf archive_file.tar
 ```
@@ -41,11 +47,11 @@ tar -xvf archive_file.tar
 
 ---
 
-## 🗜 Gzip Compression
+## Gzip Compression
 
-**Gzip** (GNU zip) is a fast, commonly used compression tool.
+**Gzip** (GNU zip) is a fast and widely used compression tool.
 
-### 🔧 Create `.tar.gz` Archive
+### Create a `.tar.gz` Archive
 
 ```bash
 tar -czf archive_file.tar.gz file1 file2 dir1
@@ -53,29 +59,31 @@ tar -czf archive_file.tar.gz file1 file2 dir1
 
 * `-z`: Compress using gzip
 
-### 🔧 Verbose Creation
+### Verbose Creation
 
 ```bash
 tar -czvf archive_file.tar.gz file1 file2 dir1
 ```
 
-### 📂 Extract `.tar.gz`
+### Extract `.tar.gz`
 
 ```bash
 tar -xzf archive_file.tar.gz
 ```
 
+or
+
 ```bash
 tar -xzvf archive_file.tar.gz
 ```
 
 ---
 
-## 🗜 Bzip2 Compression
+## Bzip2 Compression
 
-**Bzip2** offers better compression than gzip but is slower.
+**Bzip2** provides better compression than gzip but at the cost of speed.
 
-### 🔧 Create `.tar.bz2` Archive
+### Create a `.tar.bz2` Archive
 
 ```bash
 tar -cjf archive_file.tar.bz2 file1 file2 dir1
@@ -83,29 +91,31 @@ tar -cjf archive_file.tar.bz2 file1 file2 dir1
 
 * `-j`: Compress using bzip2
 
-### 🔧 Verbose Creation
+### Verbose Creation
 
 ```bash
 tar -cjvf archive_file.tar.bz2 file1 file2 dir1
 ```
 
-### 📂 Extract `.tar.bz2`
+### Extract `.tar.bz2`
 
 ```bash
 tar -xjf archive_file.tar.bz2
 ```
 
+or
+
 ```bash
 tar -xjvf archive_file.tar.bz2
 ```
 
 ---
 
-## 🗜 XZ Compression
+## XZ Compression
 
-**XZ** provides the best compression ratios but is the slowest.
+**XZ** offers the best compression ratio but is the slowest option.
 
-### 🔧 Create `.tar.xz` Archive
+### Create a `.tar.xz` Archive
 
 ```bash
 tar -cJf archive_file.tar.xz file1 file2 dir1
@@ -113,31 +123,33 @@ tar -cJf archive_file.tar.xz file1 file2 dir1
 
 * `-J`: Compress using xz
 
-### 🔧 Verbose Creation
+### Verbose Creation
 
 ```bash
 tar -cJvf archive_file.tar.xz file1 file2 dir1
 ```
 
-### 📂 Extract `.tar.xz`
+### Extract `.tar.xz`
 
 ```bash
 tar -xJf archive_file.tar.xz
 ```
 
+or
+
 ```bash
 tar -xJvf archive_file.tar.xz
 ```
 
 ---
 
-## 📊 Compression Format Comparison
+## Compression Format Comparison
 
-| Feature             | `gzip`       | `bzip2`    | `xz`      |
-| ------------------- | ------------ | ---------- | --------- |
-| Compression Speed   | Fast         | Slow       | Slowest   |
-| Decompression Speed | Fast         | Slower     | Moderate  |
-| Compression Ratio   | Good         | Better     | **Best**  |
-| File Extension      | `.tar.gz`    | `.tar.bz2` | `.tar.xz` |
-| Common Use          | Web, general | Backups    | Archival  |
+| Feature             | gzip        | bzip2      | xz        |
+| ------------------- | ----------- | ---------- | --------- |
+| Compression Speed   | Fast        | Slow       | Slowest   |
+| Decompression Speed | Fast        | Slower     | Moderate  |
+| Compression Ratio   | Good        | Better     | Best      |
+| File Extension      | `.tar.gz`   | `.tar.bz2` | `.tar.xz` |
+| Common Use          | General/Web | Backups    | Archival  |
 

From cc57ee1cafa9a55eaac193f07cc39edeee108a2a Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Sun, 9 Nov 2025 12:45:21 +0330
Subject: [PATCH 113/116] added find command

---
 Linux/Basic Administration/29-find.md | 313 ++++++++++++++++++++++++++
 1 file changed, 313 insertions(+)
 create mode 100644 Linux/Basic Administration/29-find.md

diff --git a/Linux/Basic Administration/29-find.md b/Linux/Basic Administration/29-find.md
new file mode 100644
index 0000000..29ab26c
--- /dev/null
+++ b/Linux/Basic Administration/29-find.md	
@@ -0,0 +1,313 @@
+# `find` — quick reference & practical documentation
+
+This is a compact, practical reference for the Unix/Linux `find` command aimed at DevOps engineers and system administrators. It covers common options, tests, actions, operators, examples (safe and practical) and performance tips.
+
+---
+
+# Synopsis
+
+```
+find [path...] [expression]
+```
+
+If no `path` is given, `find` searches the current directory (`.`). `expression` is evaluated left-to-right and can contain tests, actions and operators.
+
+---
+
+# Basic behaviour
+
+* `find` walks directory trees recursively by default.
+* An *expression* evaluates to true/false; when true, the default action `-print` (or whatever action is specified) is executed.
+* You can control traversal order with `-depth` and `-maxdepth`/`-mindepth`.
+* `-prune` prevents descending into directories.
+
+---
+
+# Common options and switches
+
+* `-H` : follow symbolic links specified on the command line.
+* `-L` : follow all symbolic links.
+* `-P` : never follow symbolic links (default).
+* `-xdev` : don't descend into directories on other filesystems (useful when walking `/`).
+* `-mindepth N` : do not apply tests/actions to files at depth < N.
+* `-maxdepth N` : do not descend past depth N.
+* `-depth` : process directory contents before the directory itself (useful for safe deletes).
+* `-mount` : same as `-xdev` (GNU find).
+
+---
+
+# Common tests (predicates)
+
+* `-name pattern` : match basename with shell globbing (case-sensitive). Pattern uses shell wildcards (`*`, `?`, `[]`).
+* `-iname pattern` : case-insensitive `-name`.
+* `-path pattern` : match the whole path (slash-separated) with shell globbing.
+* `-ipath pattern` : case-insensitive `-path`.
+* `-regex pattern` : match full path with regular expression (syntax differs by `find` implementation; GNU `find` defaults to Emacs regex).
+* `-type c` : file type; `f` = regular file, `d` = directory, `l` = symlink, `c` = character device, `b` = block device, `p` = FIFO, `s` = socket.
+* `-perm mode` : file permission test. Modes:
+
+  * octal: `-perm 0644` (exact)
+  * symbolic: `-perm -u=w` (any of the bits), `-perm /u=w` (any), `-perm -0644` (all bits set)
+  * GNU `find` also accepts `/mode` to mean "any of the bits".
+* `-user name` / `-uid uid` : owner.
+* `-group name` / `-gid gid` : group.
+* `-size n[cwbk]` : file size; default 512-byte blocks for some `find` versions; most use 1K blocks for `k`. GNU `find` suffixes:
+
+  * `c` = bytes
+  * `k` = kilobytes
+  * `M` = megabytes
+  * `G` = gigabytes
+  * `+n` = greater than n, `-n` = less than n, `n` = exactly n
+* `-mtime n` / `-atime n` / `-ctime n` : modified / accessed / changed time in 24-hour periods; `-mtime +7` older than 7 days, `-mtime -7` less than 7 days, `-mtime 7` exactly 7.
+* `-mmin n`, `-amin n`, `-cmin n` : minutes.
+* `-newer file` : newer than file (can be combined with `!` to negate).
+* `-empty` : empty file or directory.
+* `-links n` : number of hard links.
+* `-readable` / `-writable` / `-executable` : access checks from running user perspective.
+
+---
+
+# Common actions
+
+* `-print` : print path (often default; some implementations require explicit `-print` with complex expressions).
+* `-print0` : print paths separated by NUL (safe with whitespace/newlines).
+* `-ls` : list file using `ls -dils` style.
+* `-exec command {} \;` : run `command` once per matched file. `{}` is replaced by the current path. The `\;` terminator must be escaped or quoted.
+* `-exec command {} +` : optimized form; appends multiple matches to command arguments like `xargs` (more efficient).
+* `-ok command {} \;` : like `-exec` but prompts the user before each execution.
+* `-delete` : delete matched files/directories (be careful; obeys ordering and `-depth`).
+* `-prune` : exclude directory from descent (returns true; often used with `-o`).
+* `-quit` : stop after first match (very efficient when used with `-print`).
+* `-mindepth N`, `-maxdepth N` already described; they behave like tests.
+
+---
+
+# Operator precedence (GNU `find` style)
+
+* Parentheses `(` `)` group expressions. They must be escaped or quoted: `\( ... \)` or `'(' ... ')'`.
+* `!` or `-not` : logical NOT (unary).
+* `-a` or implicit concatenation : logical AND.
+* `-o` or `-or` : logical OR.
+* Evaluation is left-to-right; `-a` has higher precedence than `-o`. Use parentheses to be explicit.
+* Common pitfall: mixing `-prune` and `-o` requires careful grouping:
+  Example pattern to exclude `dir`:
+
+  ```
+  find . -path ./dir -prune -o -print
+  ```
+
+  This means: if path is `./dir` prune it (and `-prune` returns true) otherwise (`-o`) `-print`.
+
+---
+
+# Typical practical examples
+
+Search examples assume `bash` shell; escape parentheses and semicolons as needed.
+
+1. Find files by name (case-sensitive)
+
+```
+find /var/log -type f -name "syslog*"
+```
+
+2. Case-insensitive:
+
+```
+find /home -type f -iname "*.jpg"
+```
+
+3. Find empty directories:
+
+```
+find /path -type d -empty
+```
+
+4. Delete `*.tmp` files safely (print first, then delete)
+
+```
+find /data -type f -name "*.tmp" -print
+find /data -type f -name "*.tmp" -delete
+```
+
+Or safer with confirmation:
+
+```
+find /data -type f -name "*.tmp" -ok rm {} \;
+```
+
+5. Find and remove files older than 30 days (safe: use `-print` first)
+
+```
+find /var/log -type f -mtime +30 -print
+find /var/log -type f -mtime +30 -exec rm -- {} +
+```
+
+Prefer `-exec ... +` over `-exec ... \;` for efficiency.
+
+6. Remove directories older than 30 days (use `-depth` to ensure files inside are removed first)
+
+```
+find /tmp -depth -type d -mtime +30 -exec rm -rf -- {} +
+```
+
+`-delete` may also be used but beware of ordering; `-depth` ensures children processed before parent.
+
+7. Find files with spaces and handle them safely:
+
+```
+find /srv -type f -name "*.conf" -print0 | xargs -0 grep -H "pattern"
+```
+
+8. Find files larger than 100 MiB:
+
+```
+find / -type f -size +100M -print
+```
+
+9. Find files newer than a reference file:
+
+```
+find /web -type f -newer /tmp/deploy_marker -print
+```
+
+10. Find and run a command on many files (batching):
+
+```
+find /data -type f -name "*.log" -exec gzip -- {} +
+```
+
+11. Exclude a directory (`dir_to_skip`) while listing everything else:
+
+```
+find . -path "./dir_to_skip" -prune -o -print
+```
+
+12. Only search one level (non-recursive):
+
+```
+find . -maxdepth 1 -type f -print
+```
+
+13. Find broken symlinks:
+
+```
+find / -xtype l -print
+```
+
+Note: `-xtype` tests the target type; `-L` changes behavior of `-type`.
+
+14. Use `-printf` to customize output (GNU find):
+
+```
+find . -type f -printf "%p\t%k KB\t%TY-%Tm-%Td %TH:%TM:%TS\n"
+```
+
+`-printf` supports format sequences (`%p` path, `%s` bytes, `%k` KB blocks, `%TY` year, ...). Exact spec depends on implementation (GNU has extensive options).
+
+15. Stop at first match (fast):
+
+```
+find /usr -type f -name "passwd" -print -quit
+```
+
+16. Find files modified within last 15 minutes:
+
+```
+find /var -type f -mmin -15
+```
+
+---
+
+# Safe deletion checklist
+
+* Always `-print` or `-ls` first to verify matches.
+* Prefer `-exec rm -- {} +` or use `-delete` with `-depth` if required.
+* Watch out for `-maxdepth`/`-mindepth` to avoid accidental top-level deletions.
+* Use `-print0` + `xargs -0` when passing to other utilities.
+* Consider using `-ok` for destructive changes in interactive contexts.
+
+---
+
+# Performance & scalability tips
+
+* Limit scope: pass explicit starting paths instead of `.` or `/` when possible.
+* Use `-maxdepth` and `-mindepth` to reduce traversal.
+* Use `-xdev` to avoid crossing filesystem boundaries (speeds up root scans).
+* Combine fast tests early (e.g., `-type f -name "*.log"` rather than `-name` alone) because find evaluates left-to-right; short-circuiting happens when possible.
+* Prefer `-exec ... +` to `-exec ... \;` to reduce process spawn overhead.
+* Use `-prune` to skip large tree branches that aren’t needed.
+* On very large trees consider tools optimized for indexing (e.g., `locate` / `mlocate`, `fd`, or ripgrep for content search). `find` is always consistent but traverses the disk each run.
+
+---
+
+# Portability notes
+
+* Behavior, available tests/actions and argument formats vary slightly between implementations (GNU `find` vs BSD `find` vs BusyBox). Examples above assume GNU `find` when using `-printf`, `-delete`, `-quit` or suffixes like `M`/`G` for sizes.
+* When writing scripts for mixed environments, try to stick to portable tests: `-name`, `-type`, `-mtime`, `-print`, `-exec ... \;`. Check `/usr/bin/find --version` or `man find` on target hosts.
+
+---
+
+# Gotchas & common pitfalls
+
+* Shell globbing vs `find` globbing: `-name "*.txt"` is matched by `find` and must be quoted to prevent shell expansion.
+* `-perm` exact vs any-bit semantics differ across versions; test on target system.
+* `-regex` matches the whole path, not just basename; regex dialect differs (use `-regextype posix-extended` on GNU `find` to set type).
+* `-delete` will fail if used before tests that select children (order matters). Use `-depth` or test ordering appropriately.
+* Beware of running `find` as root with `-exec rm -rf {}` — very dangerous if expression is wrong. Always verify output.
+* `-maxdepth`/`-mindepth` may not be supported in very old `find` implementations.
+
+---
+
+# Exit status
+
+* `0` : at least one match and command completed successfully.
+* `1` : no matches were found (behavior can vary).
+* `>1` : an error occurred (e.g., permission errors or malformed expression).
+  Note: exact meanings can depend on implementation.
+
+---
+
+# Useful combinations
+
+* Find files and preserve relative paths for tar:
+
+```
+cd /path && find . -type f -name "*.conf" -print0 | tar --null -T - -czf confs.tar.gz
+```
+
+* Find and change ownership or permissions:
+
+```
+find /srv/www -type f -name "*.php" -exec chown www-data:www-data {} +
+find /srv/www -type d -exec chmod 755 {} +
+```
+
+* Search content in matched files:
+
+```
+find /app -type f -name "*.py" -print0 | xargs -0 grep -n "TODO"
+```
+
+---
+
+# Related commands/tools
+
+* `locate` / `mlocate` : fast filename lookup (uses database).
+* `fd` : simpler, faster user-friendly alternative to `find` (not always installed).
+* `xargs` : pass batches of arguments to commands (careful with spaces; use `-print0` + `xargs -0`).
+* `stat` : detailed file metadata for a single file.
+* `rm`, `tar`, `gzip`, `chown`, `chmod`, `rsync` : commonly used alongside `find`.
+
+---
+
+# Quick cheatsheet (most-used patterns)
+
+* Find files by name: `find /path -type f -name "pattern"`
+* Case-insensitive: `-iname`
+* Size bigger than 100M: `-size +100M`
+* Modified > 7 days: `-mtime +7`
+* Delete old files: `find /dir -type f -mtime +30 -exec rm -- {} +`
+* Print NUL-separated: `-print0`
+* Safe prune: `find . -path ./skip -prune -o -print`
+* Batch exec: `-exec cmd {} +`
+* Stop on first: `-print -quit`

From 89a8b2a0df24a9025f0036cd6b816e8642a550dc Mon Sep 17 00:00:00 2001
From: RadinPirouz <75082987+RadinPirouz@users.noreply.github.com>
Date: Tue, 11 Nov 2025 16:39:45 +0330
Subject: [PATCH 114/116] added web socker doc for nginx

---
 Web-Servers/Nginx/12-WebSocket.md             | 144 ++++++++++++++++++
 ...12-Example-Config.md => Example-Config.md} |   0
 2 files changed, 144 insertions(+)
 create mode 100644 Web-Servers/Nginx/12-WebSocket.md
 rename Web-Servers/Nginx/{12-Example-Config.md => Example-Config.md} (100%)

diff --git a/Web-Servers/Nginx/12-WebSocket.md b/Web-Servers/Nginx/12-WebSocket.md
new file mode 100644
index 0000000..75a3085
--- /dev/null
+++ b/Web-Servers/Nginx/12-WebSocket.md
@@ -0,0 +1,144 @@
+# WebSocket and Nginx Reverse Proxy Configuration Guide
+
+## 1. Introduction
+
+**WebSocket** is a **bi-directional, full-duplex communication protocol** that operates over a **single TCP connection**. Unlike traditional HTTP, where the client sends a request and the server responds, WebSocket allows both client and server to send messages to each other at any time during the session.
+
+This makes it highly suitable for **real-time applications** such as chat systems, live dashboards, and streaming services.
+
+---
+
+## 2. How WebSocket Works
+
+### Traditional HTTP
+
+In HTTP:
+
+* The client sends a request.
+* The server sends a response.
+* The connection is then closed (unless using persistent connections).
+
+### WebSocket
+
+In WebSocket:
+
+* The client initiates an **HTTP request** with special headers to **upgrade** the connection from HTTP to WebSocket.
+* The server accepts the upgrade and switches protocols.
+* Once established, both sides can exchange data freely over a persistent TCP connection.
+
+---
+
+## 3. Establishing a WebSocket Connection
+
+### Client → Server (Upgrade Request)
+
+The WebSocket connection starts as a standard HTTP request with additional headers:
+
+```http
+GET /chat HTTP/1.1
+Host: example.com
+Upgrade: websocket
+Connection: Upgrade
+Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==
+Sec-WebSocket-Version: 13
+```
+
+### Server → Client (Upgrade Response)
+
+If the server supports WebSocket, it responds with:
+
+```http
+HTTP/1.1 101 Switching Protocols
+Upgrade: websocket
+Connection: Upgrade
+Sec-WebSocket-Accept: s3pPLMBiTxaQ9kYGzzhZRbK+xOo=
+```
+
+---
+
+## 4. Header Explanation
+
+* **Upgrade:**
+  Indicates the protocol the client wants to switch to (in this case, `websocket`).
+
+* **Connection:**
+  Must include the value `Upgrade` to signal the intention to upgrade the connection.
+
+* **Sec-WebSocket-Key:**
+  A randomly generated Base64-encoded value (16 bytes) sent by the client.
+  It ensures a unique connection and prevents cross-protocol attacks.
+
+* **Sec-WebSocket-Version:**
+  Specifies the WebSocket protocol version the client supports.
+  Most servers use **version 13**.
+  If not supported, the server responds with:
+
+  ```http
+  HTTP/1.1 426 Upgrade Required
+  Sec-WebSocket-Version: 13
+  ```
+
+* **Sec-WebSocket-Accept:**
+  Returned by the server as proof that it successfully accepted the handshake.
+  It’s derived from the client’s `Sec-WebSocket-Key` using a predefined GUID.
+
+---
+
+## 5. HTTP Version Requirement
+
+WebSocket requires **HTTP/1.1 or higher** because:
+
+* **HTTP/1.0** opens a new TCP connection for each request, leading to high overhead.
+* **HTTP/1.1** introduced **persistent connections (Keep-Alive)**, allowing multiple requests to share a single TCP connection.
+
+For example:
+
+* In HTTP/1.0, downloading 4 images would open 4 separate TCP connections.
+* In HTTP/1.1, one TCP connection can handle all 4 requests.
+
+WebSocket leverages this concept to maintain a **single long-lived TCP connection** between the client and server.
+
+---
+
+## 6. Enabling WebSocket Support in Nginx
+
+When using Nginx as a **reverse proxy**, the connection upgrade must be explicitly configured.
+
+### Example Configuration
+
+```nginx
+location / {
+    proxy_pass http://backend:8080;
+    proxy_set_header Upgrade $http_upgrade;
+    proxy_set_header Connection "upgrade";
+    proxy_set_header Host $host;
+    proxy_http_version 1.1;
+}
+```
+
+### Explanation
+
+* **proxy_pass:**
+  Forwards the request to the backend service.
+
+* **proxy_set_header Upgrade $http_upgrade;**
+  Passes the `Upgrade` header from the client to the backend.
+
+* **proxy_set_header Connection "upgrade";**
+  Ensures Nginx forwards the `Connection: Upgrade` header required for WebSocket.
+
+* **proxy_http_version 1.1;**
+  Enables HTTP/1.1 support in proxying, required for WebSocket functionality.
+
+---
+
+## 7. Summary
+
+| Feature               | Description                                                                         |
+| --------------------- | ----------------------------------------------------------------------------------- |
+| Protocol              | Bi-directional, full-duplex                                                         |
+| Base Protocol         | HTTP/1.1                                                                            |
+| Upgrade Mechanism     | HTTP 101 Switching Protocols                                                        |
+| Persistent Connection | Yes                                                                                 |
+| Key Headers           | Upgrade, Connection, Sec-WebSocket-Key, Sec-WebSocket-Version, Sec-WebSocket-Accept |
+| Nginx Requirement     | Must enable `proxy_http_version 1.1` and pass upgrade headers                       |
diff --git a/Web-Servers/Nginx/12-Example-Config.md b/Web-Servers/Nginx/Example-Config.md
similarity index 100%
rename from Web-Servers/Nginx/12-Example-Config.md
rename to Web-Servers/Nginx/Example-Config.md

From 1507aef2734194a615e398dcd1441b07736f61f4 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Fri, 21 Nov 2025 14:55:36 +0330
Subject: [PATCH 115/116] update kuber pv doc

---
 .../Kubernetes/Storage/pv-pvc.md              | 269 ++++++------------
 1 file changed, 86 insertions(+), 183 deletions(-)

diff --git a/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md b/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
index 3cba506..7ca1d2b 100644
--- a/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
+++ b/Containerization-Orchestration/Kubernetes/Storage/pv-pvc.md
@@ -1,94 +1,71 @@
-# **Kubernetes Persistent Volumes (PV) – Technical Reference Guide**
+# 🌐 Kubernetes: Persistent Volumes (PV) Cheat Sheet
 
-## **1. Overview**
+## 📦 What is a Persistent Volume (PV)?
 
-A **Persistent Volume (PV)** is a storage resource in Kubernetes that allows data to persist beyond the lifecycle of Pods.
-Persistent Volumes can be:
-
-* **Pre-provisioned** by a cluster administrator, or
-* **Dynamically provisioned** using a **StorageClass**.
+A **Persistent Volume** is a piece of storage in a Kubernetes cluster that has been provisioned by an administrator or dynamically provisioned using **StorageClasses**.
 
 ---
 
-## **2. PV Storage Options**
+## 📁 PV Storage Options
 
-### **2.1 HostPath**
+1. **HostPath**
 
-* Mounts a directory or file from the host node’s filesystem into a Pod.
-* Suitable only for **local development** or **single-node clusters** (e.g., Minikube, Kind).
-* **Not recommended** for production environments.
+   * Mounts a file or directory from the host node’s filesystem into your Pod.
 
-### **2.2 NFS**
+2. **Using PV and PVC**
 
-* Uses Network File System (NFS) to allow multiple Pods and nodes to share storage.
-* Recommended for **shared or distributed** setups.
-
-### **2.3 Cloud Volumes**
-
-* **AWS:** `awsElasticBlockStore`
-* **GCP:** `gcePersistentDisk`
-* **Azure:** `azureDisk` or `azureFile`
-* **CSI Drivers:** Preferred for all modern cloud and on-prem environments.
+   * **PV (Persistent Volume):** The actual storage resource.
+   * **PVC (Persistent Volume Claim):** A request for storage by a user.
 
 ---
 
-## **3. Kubernetes Storage Architecture**
+## 🧱 Kubernetes Storage Layers
 
-1. **Persistent Volume (PV):** Represents the actual storage resource, either statically created or dynamically provisioned.
-2. **Persistent Volume Claim (PVC):** A user request for storage of specific size and access modes.
-3. **StorageClass:** Defines dynamic provisioning behavior (provisioner, reclaim policy, parameters).
+1. **Persistent Volume (PV)**
+2. **Persistent Volume Claim (PVC)**
 
 ---
 
-## **4. PV Lifecycle Phases**
+## 🔄 PV Lifecycle States
 
-| **State**     | **Description**                                  |
-| ------------- | ------------------------------------------------ |
-| **Available** | PV is ready to be bound to a claim.              |
-| **Bound**     | PV is bound to a PVC.                            |
-| **Released**  | PVC was deleted; PV is unbound but retains data. |
-| **Failed**    | Automatic cleanup failed.                        |
-
-### **Reclaim Policies**
-
-* **Delete:** Deletes the underlying storage resource.
-* **Retain:** Keeps the data for manual recovery.
-* **Recycle:** Deprecated (was used to scrub the volume).
+| State        | Description                                          |
+| ------------ | ---------------------------------------------------- |
+| Provisioning | Kubernetes is preparing the PV.                      |
+| Binding      | The PV is bound to a PVC.                            |
+| Using        | The bound PV is being used by a Pod.                 |
+| Releasing    | PVC is deleted; PV is no longer bound.               |
+| Reclaiming   | PV is reclaimed using one of the following policies: |
+|              |     • `Delete` – Remove the storage                  |
+|              |     • `Recycle` – Basic scrub (deprecated)           |
+|              |     • `Retain` – Manual reclaim                      |
 
 ---
 
-## **5. PV Access Modes**
+## 🔒 PV Access Modes
 
-| **Access Mode**           | **Description**                                             |
-| ------------------------- | ----------------------------------------------------------- |
-| `ReadWriteOnce` (RWO)     | Volume can be mounted as read-write by a single node.       |
-| `ReadOnlyMany` (ROX)      | Volume can be mounted read-only by multiple nodes.          |
-| `ReadWriteMany` (RWX)     | Volume can be mounted as read-write by multiple nodes.      |
-| `ReadWriteOncePod` (RWOP) | Volume can be mounted read-write by a single Pod. (≥ v1.22) |
+| Mode   | Description                                 |
+| ------ | ------------------------------------------- |
+| `RWO`  | **ReadWriteOnce** – One node can read/write |
+| `ROX`  | **ReadOnlyMany** – Many nodes read-only     |
+| `RWX`  | **ReadWriteMany** – Many nodes read/write   |
+| `RWOP` | **ReadWriteOncePod** – One Pod only         |
 
 ---
 
-## **6. CLI Commands**
+## 🛠️ Check PVs via CLI
 
 ```bash
-# List all Persistent Volumes
 kubectl get pv
-
-# List all Persistent Volume Claims (across all namespaces)
-kubectl get pvc -A
-
-# Describe a specific PV or PVC
-kubectl describe pv <pv-name>
-kubectl describe pvc <pvc-name> -n <namespace>
-
-# Delete a PV or PVC
-kubectl delete pv <pv-name>
-kubectl delete pvc <pvc-name> -n <namespace>
 ```
 
+```bash
+kubectl get pvc
+```
+
+
 ---
 
-## **7. Example: Deployment with HostPath Volume**
+## 🚀 Example: Deployment using HostPath Volume
 
 ```yaml
 apiVersion: apps/v1
@@ -96,15 +73,19 @@ kind: Deployment
 metadata:
   name: app-1
   namespace: dev
+  labels:
+    label1: test1
+    app.kubernetes.io/label2: test2
 spec:
   replicas: 3
   selector:
     matchLabels:
-      app: nginx
+      app.kubernetes.io/label2: test2
   template:
     metadata:
       labels:
-        app: nginx
+        app.kubernetes.io/label2: test2
+        os: linux
     spec:
       containers:
         - name: nginx
@@ -113,166 +94,88 @@ spec:
             - containerPort: 80
           volumeMounts:
             - name: nginx-log
-              mountPath: /var/log/nginx
+              mountPath: /var/log/nginx  
       volumes:
         - name: nginx-log
           hostPath:
             path: /root/nginx/logs
-            type: DirectoryOrCreate
 ```
 
-**Valid `hostPath` types:**
-`DirectoryOrCreate`, `Directory`, `FileOrCreate`, `File`, `Socket`, `CharDevice`, `BlockDevice`
-
 ---
 
-## **8. Example: Static Persistent Volume (PV)**
+## 📂 Example: PersistentVolume with NFS
 
 ```yaml
 apiVersion: v1
 kind: PersistentVolume
 metadata:
-  name: pv001
+  name: pv1
 spec:
-  capacity:
-    storage: 128Mi
-  accessModes:
+  capacity: 
+    storage: 5Gi
+  volumeMode: Filesystem
+  accessModes: 
     - ReadWriteMany
-  persistentVolumeReclaimPolicy: Retain
-  storageClassName: manual
-  hostPath:
-    path: /mnt/data/pv001
-```
-
----
-
-## **9. Example: Persistent Volume Claim (PVC)**
-
-```yaml
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: pvc-2
-  namespace: db
-spec:
-  accessModes:
-    - ReadWriteOnce
-  resources:
-    requests:
-      storage: 64Mi
-  storageClassName: manual
-  volumeName: pv001
-```
-
----
-
-## **10. Example: NFS-Based PV and PVC**
-
-### **Persistent Volume (PV)**
-
-```yaml
-apiVersion: v1
-kind: PersistentVolume
-metadata:
-  name: pv-nfs-2
-spec:
-  capacity:
-    storage: 128Mi
-  accessModes:
-    - ReadWriteMany
-  persistentVolumeReclaimPolicy: Retain
-  storageClassName: nginx-files
+  persistentVolumeReclaimPolicy: Recycle
+  storageClassName: custom-name
   mountOptions:
     - hard
-    - nfsvers=4.2
+    - nfsvers=4.1
   nfs:
-    path: /root/Nginx_Files
-    server: 192.168.6.160
+    path: /nfs/data
+    server: 192.168.1.10
 ```
 
-### **Persistent Volume Claim (PVC)**
 
-```yaml
-apiVersion: v1
-kind: PersistentVolumeClaim
-metadata:
-  name: pvc-1
-  namespace: db
-spec:
-  volumeName: pv-nfs-2
-  accessModes:
-    - ReadWriteMany
-  resources:
-    requests:
-      storage: 64Mi
-  storageClassName: nginx-files
-```
 
----
-
-## **11. Example: Static StorageClass**
-
-```yaml
-apiVersion: storage.k8s.io/v1
-kind: StorageClass
-metadata:
-  name: nginx-files
-provisioner: kubernetes.io/no-provisioner
-volumeBindingMode: WaitForFirstConsumer
-reclaimPolicy: Retain
-```
-
----
-
-## **12. Example: Nginx Deployment Using PVC**
 
 ```yaml
 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: nginx
-  namespace: web-app
+  name: app-1
+  namespace: dev
+  labels:
+    label1: test1
+    app.kubernetes.io/label2: test2
 spec:
-  replicas: 1
+  replicas: 3
   selector:
     matchLabels:
-      app_type: nginx-web
+      app.kubernetes.io/label2: test2
   template:
     metadata:
       labels:
-        app_type: nginx-web
+        app.kubernetes.io/label2: test2
+        os: linux
     spec:
       containers:
         - name: nginx
-          image: nginx:latest
+          image: nginx
           ports:
             - containerPort: 80
           volumeMounts:
-            - name: nginx-configs-volume
-              mountPath: /etc/nginx/conf.d/default.conf
-              subPath: reverse_proxy.conf
-            - name: nginx-logs-volume
-              mountPath: /var/log/nginx
-      volumes:
-        - name: nginx-configs-volume
-          configMap:
-            name: nginx-configs
-        - name: nginx-logs-volume
-          persistentVolumeClaim:
-            claimName: nginx-pvc
-```
-
+            - name: nginx-log
+              mountPath: /var/log/nginx  
+          volumes:
+            - name: nginx-log
+              persisentVolumeClaim:
+                claimName: pv1
 ---
 
-## **13. Best Practices and Recommendations**
-
-1. **Always specify `storageClassName`** for predictable PV/PVC binding.
-2. **Use `volumeBindingMode: WaitForFirstConsumer`** to ensure node-aware provisioning.
-3. **Avoid `hostPath`** in multi-node or production clusters; use NFS or CSI drivers instead.
-4. **Monitor events** for troubleshooting binding issues:
-
-   ```bash
-   kubectl describe pvc <pvc-name> -n <namespace>
-   ```
-5. **Implement proper reclaim policies** or automated cleanup mechanisms for storage lifecycle management.
+apiVersion: v1
+kind: persisentVolumeClaim
+metadata:
+    name: pvc1
+    namespace: ns-test
+spec:
+    accessModes: 
+        - ReadWriteMany
+    resources:
+        requests:
+            storage: 1Gi
+        limits:
+            storage: 2Gi        
+    storageClassName: custom-name
+```
 

From e063bb8c7c7bc983492080b3cf628d61462c7089 Mon Sep 17 00:00:00 2001
From: radinpirouz <pirouz.radin@yahoo.com>
Date: Sat, 22 Nov 2025 22:30:51 +0330
Subject: [PATCH 116/116] added dozzle doc

---
 .../Tools/Dozzle/01-Information.md            |  90 +++++++++++
 .../Tools/Dozzle/02-On-Docker.md              | 153 ++++++++++++++++++
 2 files changed, 243 insertions(+)
 create mode 100644 Containerization-Orchestration/Tools/Dozzle/01-Information.md
 create mode 100644 Containerization-Orchestration/Tools/Dozzle/02-On-Docker.md

diff --git a/Containerization-Orchestration/Tools/Dozzle/01-Information.md b/Containerization-Orchestration/Tools/Dozzle/01-Information.md
new file mode 100644
index 0000000..f339293
--- /dev/null
+++ b/Containerization-Orchestration/Tools/Dozzle/01-Information.md
@@ -0,0 +1,90 @@
+# **Dozzle – Real-Time Docker Log Viewer**
+
+## **Overview**
+
+**Dozzle** is an open-source, lightweight, web-based log viewer designed to simplify monitoring and debugging Docker containers. Sponsored by **Docker OSS** and actively maintained by **Amir Raminfar**, Dozzle provides real-time log streaming with an intuitive and efficient UI.
+
+Optimized for developers, DevOps engineers, and system administrators, Dozzle offers:
+
+* **Live log streaming** directly from containers
+* **Search and filtering capabilities**
+* **JSON log support** with intelligent color coding
+* **A minimal footprint**, making it ideal for any environment
+
+Dozzle is distributed under the **MIT license**, ensuring free and open use across development and production workflows.
+
+---
+
+## **Key Features**
+
+### **🔹 Real-Time Log Streaming**
+
+Instantly view logs as they are generated, enabling faster debugging and container monitoring.
+
+### **🔹 Web-Based Interface**
+
+No need for additional CLI commands—open your browser and start exploring logs immediately.
+
+### **🔹 Lightweight & Fast**
+
+Runs with minimal resource usage, suitable for both development setups and production Docker hosts.
+
+### **🔹 Simple Installation**
+
+Deployable with a single Docker command or via Docker Compose. No complex setup required.
+
+### **🔹 Secure Local Access**
+
+Works by reading the Docker daemon socket (`/var/run/docker.sock`), ensuring direct and secure interaction with local containers.
+
+---
+
+## **Installation & Setup**
+
+### **Using Docker CLI (Recommended)**
+
+The simplest way to run Dozzle is by mounting the Docker socket file:
+
+* The Docker socket is typically located at:
+  **`/var/run/docker.sock`**
+* Dozzle listens on **port 8080** by default, but you can remap it using `-p` if needed.
+
+```bash
+docker run -d \
+  --name dozzle \
+  -p 8080:8080 \
+  -v /var/run/docker.sock:/var/run/docker.sock \
+  amir20/dozzle:latest
+```
+
+Once running, access Dozzle at:
+➡️ **[http://localhost:8080](http://localhost:8080)**
+
+---
+
+## **Using Docker Compose**
+
+For environments managed with Compose, use the following configuration:
+
+```yaml
+services:
+  dozzle:
+    image: amir20/dozzle:latest
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock
+    ports:
+      - 8080:8080
+```
+
+Start the service:
+
+```bash
+docker compose up -d
+```
+
+---
+
+## **Swarm Deployment**
+
+Dozzle can also be deployed as a Swarm service for distributed environments.
+
diff --git a/Containerization-Orchestration/Tools/Dozzle/02-On-Docker.md b/Containerization-Orchestration/Tools/Dozzle/02-On-Docker.md
new file mode 100644
index 0000000..fc44956
--- /dev/null
+++ b/Containerization-Orchestration/Tools/Dozzle/02-On-Docker.md
@@ -0,0 +1,153 @@
+# **Dozzle Deployment Modes**
+
+Dozzle offers multiple deployment modes to support a variety of architectures—from single-host setups to distributed multi-node clusters. Depending on your environment, you can run Dozzle in one of the following modes:
+
+* **Standard Mode (default)** – Local logs from the Docker engine
+* **Agent Mode** – Remote hosts exposed securely via TLS
+* **Swarm Mode** – Distributed mesh network for Docker Swarm clusters
+* **Hybrid (Swarm + Standalone Agents)** – Combine both for maximum flexibility
+
+This section explains how each mode works and provides production-ready deployment examples.
+
+---
+
+# **1. Agent Mode**
+
+Agent mode allows a Dozzle instance to expose its host’s container logs to other Dozzle servers over a secure **TLS-encrypted channel**. This is ideal for:
+
+* Managing multiple remote Docker hosts
+* Viewing logs from distributed machines in a single Dozzle UI
+* Secure cross-host communication without VPNs
+
+In agent mode, Dozzle runs with the `agent` subcommand and listens for remote connections.
+
+---
+
+## **Deploying a Dozzle Agent**
+
+```yaml
+services:
+  dozzle-agent:
+    image: amir20/dozzle:latest
+    command: agent
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock:ro
+    ports:
+      - 7007:7007
+```
+
+### **Customizing Agent Identity**
+
+Agents can be assigned human-readable names using the `DOZZLE_HOSTNAME` variable:
+
+```yaml
+environment:
+  - DOZZLE_HOSTNAME=my-special-name
+```
+
+---
+
+## **Connecting a Dozzle Instance to One or More Agents**
+
+Define the remote agents in the `DOZZLE_REMOTE_AGENT` variable. Multiple agents should be comma-separated.
+
+```yaml
+services:
+  dozzle:
+    image: amir20/dozzle:latest
+    environment:
+      - DOZZLE_REMOTE_AGENT=agent1:7007,agent2:7007
+    ports:
+      - 8080:8080
+```
+
+Once launched, the UI will display the remote agent hosts alongside local containers.
+
+---
+
+# **2. Swarm Mode**
+
+Dozzle supports a special **Swarm Mode** designed for distributed Docker Swarm environments. When enabled, Dozzle automatically forms a **secure, fully encrypted mTLS mesh network** between all Dozzle nodes in the cluster.
+
+### **Key features of Swarm Mode**
+
+* Automatic discovery of all Dozzle instances
+* Encrypted communication using mTLS
+* Support for grouping logs by:
+
+  * Docker stacks (`com.docker.stack.namespace`)
+  * Docker Compose projects (`com.docker.compose.project`)
+  * Swarm services (`com.docker.swarm.service.name`)
+
+Swarm Mode is the recommended deployment method for multi-node clusters.
+
+---
+
+## **Deploying Dozzle in Swarm Mode**
+
+Use `mode: global` to deploy Dozzle on every node:
+
+```yaml
+services:
+  dozzle:
+    image: amir20/dozzle:latest
+    environment:
+      - DOZZLE_MODE=swarm
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock
+    ports:
+      - 8080:8080
+    networks:
+      - dozzle
+    deploy:
+      mode: global
+networks:
+  dozzle:
+    driver: overlay
+```
+
+### **Important:**
+
+**Swarm mode cannot use Docker socket-proxy.**
+This is a Docker limitation—Swarm services cannot directly access individual proxy instances, and Dozzle requires that direct access.
+
+---
+
+# **3. Adding Standalone Agents to Swarm Mode (v8.8.x+)**
+
+Starting with **v8.8.x**, Dozzle allows you to mix **standalone agents** with a **Swarm-mode deployment**. Remote agents will appear as additional nodes in the Dozzle UI.
+
+Example configuration:
+
+```yaml
+services:
+  dozzle:
+    image: amir20/dozzle:latest
+    environment:
+      - DOZZLE_MODE=swarm
+      - DOZZLE_REMOTE_AGENT=agent:7007
+    volumes:
+      - /var/run/docker.sock:/var/run/docker.sock
+    ports:
+      - 8080:8080
+    networks:
+      - dozzle
+    deploy:
+      mode: global
+networks:
+  dozzle:
+    driver: overlay
+```
+
+This hybrid approach is ideal when part of your infrastructure runs in Swarm and other nodes run standalone Docker.
+
+---
+
+# **Summary**
+
+| Mode                        | Best For                         | Key Features                         |
+| --------------------------- | -------------------------------- | ------------------------------------ |
+| **Standard**                | Single-host setups               | Local logs, simplest deployment      |
+| **Agent Mode**              | Remote nodes, non-Swarm clusters | TLS-secured remote access            |
+| **Swarm Mode**              | Multi-node Swarm clusters        | mTLS mesh networking, auto-discovery |
+| **Hybrid (Swarm + Agents)** | Mixed environments               | Combine Swarm nodes + remote agents  |