git-multibranch

Automate Git deployments by configuring a bare repository with post-receive hooks that automatically deploy main and dev branches to separate web server directories. Set up SSH authentication, initialize branches, create per-branch deployment paths, and trigger deployments via hook scripts on each push.

SSH authentication for Git deployment requires configuring SSH keys for deployment users, setting appropriate file permissions on the bare repository, and restricting shell access to deployment scripts only. This ensures secure, automated pushes trigger deployments without manual intervention.

Post-receive hooks are scripts executed automatically after Git receives a push. They detect which branch was pushed, checkout the code to the corresponding deployment directory, and restart services. This eliminates manual deployment steps for each branch.

Yes. Create dedicated deployment directories for each branch (e.g., /var/www/main, /var/www/dev), configure your web server to serve from the appropriate path, and use post-receive hooks to checkout branch-specific code into the correct directory on each push.

Prerequisites include SSH key setup for deployment users, a bare Git repository on the deployment server, web server installation and configuration, and knowledge of post-receive hook scripting. Verify SSH connectivity and repository initialization before testing branch deployments.

Bare repositories have no working directory, preventing accidental edits and corruption. They're designed specifically for receiving pushes via SSH and are ideal for triggering automated workflows through post-receive hooks without conflicting with live code.