02 — Folder Structure

Your repository must follow this exact layout. The DevOps automation depends on files being in these exact locations.

your-app/
├── .github/
│   └── workflows/
│       └── ci.yml              # Pipeline: builds image, pushes to ECR, deploys to the K8s cluster (required)
├── dockerfiles/
│   ├── Dockerfile              # Instructions for packaging your app into a container (required)
│   └── .dockerignore           # Files to exclude from the container build (recommended)
├── kubernetes/
│   ├── deployment.yaml         # How Kubernetes runs your app — 2 copies minimum (required)
│   ├── service.yaml            # How Kubernetes routes traffic to your app (required)
│   └── configmap.yaml          # Non-sensitive config values (only if needed)
└── source/
    ├── (your app source files) # package.json / requirements.txt / pom.xml live HERE, not at repo root
    └── README.md               # Documents every environment variable your app needs (required)

Rules

• The Docker build context is the repository root: builds run as docker build -f dockerfiles/Dockerfile . — so all COPY paths in the Dockerfile are relative to the repo root (e.g. COPY source/package*.json ./), not relative to dockerfiles/.
• Your dependency manifest (package.json, requirements.txt, etc.) belongs inside source/ with the rest of the app code.
• Extra top-level files are allowed (README.md, docs/, .gitignore, .env.example) — but the required files must be exactly where shown above.
• Do not commit build outputs (node_modules/, dist/, __pycache__/, target/) — exclude them via .gitignore and dockerfiles/.dockerignore.

Prompt tip

"Organise the project with this exact folder structure: .github/workflows/, dockerfiles/, kubernetes/, and source/. All application code and the dependency manifest go inside source/. The Docker build context is the repository root."