How oneconvergence/dkubex-helm works
Project type and purpose
• This is not a traditional “app” codebase but a Helm-based deployment repository. It contains two distinct Helm charts—“dkubex” and “securellm”—plus an index.yaml to serve them from a chart repo.
• Purpose: package and manage Kubernetes releases of the dkubex service and the securellm stack (which itself pulls in a Supabase subchart).
File structure
• Top level:
• README.md (high-level repo description)
• dkubex/ (Helm chart for dkubex service)
• securellm/ (Helm chart for securellm stack)
• index.yaml (Helm chart repository index)
• dkubex/ contains Chart.yaml, values.yaml, and a templates/ folder with ConfigMap, ServiceAccount, hooks (pre-upgrade, uninstall), install manifests.
• securellm/ contains its own Chart.yaml, values.yaml, templates/ (ingress & securellm Deployment), plus a charts/supabase/ subdirectory.
• charts/supabase/ is a full subchart with templates broken into auth/, db/, kong/, rest/ directories, each defining Deployments, Services, Ingresses, Roles, PVCs, etc.
README
• Minimal description: “Repository to hold dkubex helm release charts.”