Vibinex helps you understand the changes in your codebase. Vibinex helps you:
You can choose to turn on/off each feature individually. There are Feature Flags on the Vibinex settings page to turn the PR comment or the automatic review assignment on or off. The highlighting features are delivered through the Chrome extension, which you can disable if you don't want to see the highlights.
The diagram below describes the architecture of Vibinex. It consists of 3 components: 3. Vibinex DPU: Marked as the "Backend #1" in the below diagram, the DPU (Data Processing Unit) is docker container the processes your code. It has no public endpoints for maximum privacy & security. 2. Vibinex server: Marked as the "Backend #2" in the below diagram, the server is the main backend of Vibinex. It triggers the DPU when a PR is created or changed and acts as the backend for the browser extension.
A DPU stands for Data Processing Unit. It is a docker container that processes all the sensitive data, i.e. your codebase. Self-hosting the DPU on your own VMs provides the highest privacy.
There are just 2 steps to setting up Vibinex:
You can set up the DPU on your repositories either as an owner of the repository or a member. When you set it up as an owner, webhooks are added on your repository that automatically trigger DPU when a pull request is created or updated. When you set it up as a member, you need to manually trigger the DPU when a pull request when you want to process it.
Follow this guide for a quick set up.