Skip to main content
In this lesson we’ll review the source code and Git repositories used in the demo. You’ll see how the GitOps repo (ArgoCD) holds Kubernetes manifests, while the application repo contains the PHP app, images, Dockerfile, and CI scripts. This walkthrough shows how the repositories, Dockerfile, and manifests fit together in a GitOps + CI/CD workflow.
A presentation slide reading "Demo — Git Repositories and Application Walkthrough" with the title shown in purple blocks on the left and a large white card with a small teal film camera icon on the right.

​
Overview: Repositories used in the demo

The setup uses two Git repositories hosted in Gitea:
  • A GitOps repository (ArgoCD) that contains Kubernetes manifests (Deployment and Service) used by ArgoCD to create resources in the cluster.
  • An application repository (Solar System) that contains the PHP application source, static assets, a Dockerfile, and CI scripts used by the Jenkins pipeline.
Quick summary: Open the ArgoCD/GitOps repository to inspect the manifests. In the Jenkins-demo directory you’ll find Kubernetes manifests such as deployment.yaml and service.yaml. ArgoCD continuously monitors this repository and applies detected changes to the cluster (via periodic polling or webhook-driven refresh).
A dark-themed code hosting repository page (looks like Gitea) showing commit/branch info and a file listing. Visible files include deployment.yaml and service.yaml, with buttons for New File, Upload File and history.

​
Application repository: Solar System (PHP)

The Solar System repository contains a small PHP + HTML web application. Key parts include:
  • index.php — the single-page app that references images and CSS-like styles.
  • images/ — PNG assets such as solar-system-9.png and background.png.
  • Dockerfile — builds the container image from the official PHP Apache base.
  • Jenkinsfile and pr.sh — CI pipeline scripts used by Jenkins to build and push images, and to trigger deployments.
A dark-themed Gitea repository page for "siddharth/solar-system" showing a Simple PHP app (63 commits, 1 branch, ~13 MiB) and a visible HTTP clone URL. The file list and recent commits are shown, including images, Dockerfile, Jenkinsfile, index.php and pr.sh.

​
index.php — how the page uses repository images

The page is a compact PHP/HTML file. The most important configurable parts are which solar-system image and which background image are used. The CSS references the repository’s raw file URLs to render both the rotating solar system graphic and the page background. A representative snippet:
Notes:
  • The CSS uses absolute raw URLs from the Gitea server so the page can load images directly from the repo.
  • You can swap the image filenames in these URLs to change visuals without touching the Docker image — useful for rapid UI updates.

​
Dockerfile — building the container image

The repo includes a simple Dockerfile that copies the application files into the Apache web root and exposes port 80. This is sufficient for containerizing the PHP app:
This Dockerfile:
  • Uses the official php:7.4-apache base image.
  • Copies index.php and the images directory into /var/www/html.
  • Exposes port 80 for HTTP traffic.

​
CI pipeline files

The repository also contains CI-related files (for example Jenkinsfile and pr.sh) that Jenkins uses to build and push the container image, run tests, or trigger downstream steps such as updating the GitOps repository. In a typical pipeline:
  1. Jenkins pulls the application repo.
  2. Jenkins builds the Docker image using the Dockerfile.
  3. The image is pushed to a container registry.
  4. GitOps manifests are updated (or a new image tag is written into the ArgoCD repo), and ArgoCD applies the change.
ArgoCD continuously watches the GitOps repository. Any changes to the manifests will be detected and applied automatically — keep the manifests in the GitOps repo up to date to reflect the desired cluster state.

Watch Video