Local Development¶

Purpose¶

Get AkshayaBazaar running on your own Windows machine - either the lightweight Docker Compose stack for day-to-day feature work, or the full local k3d/K3s + Helm stack that mirrors real staging/production for infrastructure work.

Two local setups, two different jobs¶

	Docker Compose	Local k3d/K3s
What it's for	Day-to-day app development (hot reload, fast iteration)	Testing Kubernetes/Helm/NetworkPolicy changes before they touch real staging
Files	`docker-compose.yml` + `docker-compose.dev.yml`	`helm/akshayabazaar/` + `helm/akshayabazaar/values-local-staging.yaml`
Start command	`docker compose -f docker-compose.yml -f docker-compose.dev.yml up`	`.\scripts\build.ps1 -Local` then `.\scripts\deploy-local.ps1`
Full guide	Docker	Kubernetes → k3d

Most day-to-day feature work only needs Docker Compose. The k3d/K3s stack matters when you're changing helm/, terraform/, NetworkPolicy, or anything that only manifests as a Kubernetes- level bug (this project's own environments/local/README.md "Common failure scenarios" documents several bugs that were only reproducible this way).

Pages in this section¶

Prerequisites - every tool this repository's tooling assumes is on PATH, and how to check/install each one on Windows.
First-time setup - the exact sequence from a fresh clone to a working local stack.
Troubleshooting - the specific failures already diagnosed live against this project's own local k3d cluster.

The validated local staging configuration¶

Context:      k3d-akshaya-staging
Namespace:    staging
Helm release: akshaya-local
Host:         staging.akshaya.local
Ingress port: 80

Last validated result: .\scripts\verify-staging.ps1 → 14 PASS, 0 WARNING, 0 FAIL. Full command and output: Kubernetes → Helm and Operations → Verification.