bgevconsultancy turns Helm-v2 into a Clava deployment package
The fork pairs a cleaner Clava identity with a practical route to run the platform on your own infrastructure.
Most of this thread is fork housekeeping: replacing leftover Mike visual assets and simplifying configuration examples so they reflect only the services still in use.
The meaningful addition is self-hosted deployment packaging. It gives an organisation a documented, container-based way to bring up the application outside the fork's existing hosted setup. That matters because deployment control is often a procurement and risk question, not just an engineering preference.
- On-prem deployment materials: a starting point for teams that want to operate the platform in their own environment.
The GitHub changes are worth a closer look for anyone assessing whether Clava can fit an internal hosting model.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?