GitHub Integration & Webhook Deployment | B A C Documentation

Learn how to securely link your GitHub account and configure auto-deploy webhooks.

B A C leverages automated Git Webhooks to provide continuous deployment (CI/CD). Whenever you push updates to your linked repository branch, our staging servers automatically fetch the new code, build dependencies, and update your live app with zero downtime.

Step-by-Step GitHub Webhook Setup

Open Webhook Settings in Console On your Console dashboard, locate the application you want to link. If Auto-Deploy is enabled, click the Config button under the Webhook/Auto-Deploy column to open the credential parameters.

Navigate to GitHub Webhooks Go to your GitHub repository in your browser. Click on the Settings tab in the repository menu, then select Webhooks in the left sidebar. Click on the "Add webhook" button in the top-right.

Fill Payload Details Copy the parameters from your console config popup and paste them exactly into the GitHub fields:

Payload URL: https://officialbac.in/api/webhook/github

Content type: application/json

Secret: Your secure repository-specific token from the console

Save & Activate Under "Which events would you like to trigger this webhook?", select "Just the push event". Ensure the "Active" checkbox is checked, and click "Add webhook". GitHub will send a test ping, which should show a green checkmark indicating a successful link.

Deployment Cycle Workflow

1. Developer Push

You push new code commits to your main repository branch.

2. Webhook Event

GitHub sends a secure POST request to the B A C ingress webhook URL.

3. Automated Build

B A C pulls the code, installs dependencies, and runs compilers.

4. Hot Swap

The process manager restarts and performs a zero-downtime hot swap.

Webhook Troubleshooting FAQ

Q: GitHub displays a red warning icon next to the webhook?

This indicates a connection failure. Check that the Payload URL is spelled correctly and matches the secure https://officialbac.in/... endpoint. Ensure you did not copy any trailing whitespace.

Q: GitHub says 200 OK, but my application didn't update?

Verify that you pushed commits to the branch configured in your app settings (typically main or master). Pushes to other branches will be filtered out by the router to prevent dev-build leaks.

Q: The build starts but my application goes into stopped state?

This is usually a dependency or build error (e.g. syntax error, missing environment variable, or failed database connection). Navigate to the app details console in the dashboard and open stderr.log to see the exact crash stack trace.

Secure Integrity Protection: All payload requests are cryptographically validated by our ingress node using your repository-specific secret. If the GitHub request signature does not match your secret, the request is immediately rejected to prevent execution spoofing.