# wahidsaidmaroc/devopssitewebhtmldocker architecture

> Architecture diagram of the GitHub repository wahidsaidmaroc/devopssitewebhtmldocker, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-05-22). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/wahidsaidmaroc/devopssitewebhtmldocker
- Repository: https://github.com/wahidsaidmaroc/devopssitewebhtmldocker

## Overview

##### Project type and purpose
- This is a small static‐site project (“DevOpsSiteWebHTMLDocker”) that serves two HTML pages (`index.html` and `contact.html`) using an HTTP server inside a Docker container.
- It includes a GitHub Actions CI/CD pipeline (`.github/workflows/cicdproject.yaml`) which builds the Docker image and pushes/deploys it.

##### File structure
- Top level
- `.github/workflows/cicdproject.yaml`: defines CI/CD steps
- `dockerfile`: instructions to build the container image
- `README.md`: one‐line description
- `source/`
- `index.html` and `contact.html`: static content
- No backend code, no database—purely static HTML served via a container.

##### Key insights from the README
- Project name and intent: “DevOps SiteWeb HTML avec Docker”
- Emphasis on Dockerization and a DevOps pipeline.

a. Main components
1. Developer machine (writes HTML, pushes to repo)
2. GitHub repository (hosted code + Dockerfile + CI config)
3. GitHub Actions runner (CI/CD)
4. Docker Image Registry (Docker Hub or GitHub Container Registry)
5. Production environment (Docker host or Kubernetes cluster)
6. End user’s web browser
b. Relationships and interactions
- Developer → pushes code → GitHub repo
- GitHub Actions → on push → pulls source + Dockerfile → builds image → pushes image to registry
- Deployment step → pulls image from registry → deploys container on production host
- End user → HTTP request → containerized web server → serves HTML
c. Architectural patterns
- CICD pipeline for build→test→deploy
- Containerization of static site
d. Relevant technologies
- GitHub Actions for CI/CD
- Docker CLI & Dockerfile
- Docker registry (Docker Hub/GCR)
- HTTP server inside container (e.g., nginx)
- GitHub repository

## Diagram (Mermaid)

```mermaid
flowchart TD
    Developer["Developer"]:::actor

    subgraph "GitHub Repository"
        README["README.md"]:::code
        DockerfileNode["Dockerfile"]:::code
        Index["index.html"]:::code
        Contact["contact.html"]:::code
        CIConfig[".github/workflows/cicdproject.yaml"]:::ci
    end

    GitHubActions["GitHub Actions Runner"]:::ci
    DockerRegistry["Docker Registry"]:::infra
    ProdHost["Production Host"]:::infra
    EndUser["End User"]:::actor

    Developer -->|"push"| README
    README -->|"trigger CI/CD"| GitHubActions
    GitHubActions -->|"build image"| DockerRegistry
    DockerRegistry -->|"deploy image"| ProdHost
    EndUser -->|"HTTP request"| ProdHost
    ProdHost -->|"serve HTML response"| EndUser

    click Index "https://github.com/wahidsaidmaroc/devopssitewebhtmldocker/blob/main/source/index.html"
    click Contact "https://github.com/wahidsaidmaroc/devopssitewebhtmldocker/blob/main/source/contact.html"
    click DockerfileNode "https://github.com/wahidsaidmaroc/devopssitewebhtmldocker/tree/main/dockerfile"
    click CIConfig "https://github.com/wahidsaidmaroc/devopssitewebhtmldocker/blob/main/.github/workflows/cicdproject.yaml"
    click README "https://github.com/wahidsaidmaroc/devopssitewebhtmldocker/blob/main/README.md"

    classDef actor fill:#f9f,stroke:#333,stroke-width:1px
    classDef code fill:#ccf,stroke:#333,stroke-width:1px
    classDef ci fill:#fcf8e3,stroke:#333,stroke-width:1px
    classDef infra fill:#cfc,stroke:#333,stroke-width:1px
```
