Durable operational lessons for future agents and maintainers.
helm repo updatewithout a repository name updates every repo configured on the user's machine. This can fail because of unrelated broken repos and block the installer even whenhttps://charts.aurva.ai/is healthy.- Installer logic should configure Aurva with
helm repo add aiostack https://charts.aurva.ai/ --force-updateand then runhelm repo update aiostack. - When Helm commands fail in installer scripts, print Helm's actual stderr/stdout so users are not left with a generic error.
- Root
index.yamland rootaiostack-*.tgzfiles form the chart repository. - Keep
index.yamlaligned with packages that exist at repo root. - Current retention policy: keep
aiostackchart versions>= 3.0.0; do not reintroduce1.xor2.xchart packages unless explicitly asked.
- The docs app lives in
newdocs/and uses Bun. - The docs Docker image should use Debian slim, not Alpine, because native dependencies like
better-sqlite3can fall back to musl/native builds and fail innode-gyp. - The docs Dockerfile currently targets Node 26.
- Do not run local Docker builds unless explicitly asked.
- The GitHub workflow
Build & Publish — Docs Siteis.github/workflows/bake.yamland is manually dispatchable with ataginput.
kcis not guaranteed to exist; usekubectl.- Confirm context before patching Kubernetes.
- Known staging docs target:
- namespace:
aiostack-docs - deployment:
aiostack-docs - container:
aiostack-docs - image repository:
asia-south1-docker.pkg.dev/aurva-gcp/aiostack-docs/aiostack-docs
- namespace:
- After patching, run
kubectl rollout status deployment/aiostack-docs -n aiostack-docs --timeout=180s.