configure-git-webserver

Configure bare Git repositories with post-receive hooks for automated web deployment.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Zurybr/lefarma-skills --skill configure-git-webserver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-git-webserver
Source: https://github.com/Zurybr/lefarma-skills/tree/main/letta/benchmarks/trajectory-only/configure-git-webserver
Command: npx skills add https://github.com/Zurybr/lefarma-skills --skill configure-git-webserver

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of deploying web content to a server simply by pushing changes to a Git repository, eliminating manual deployment steps.

Core Features & Use Cases

  • Automated Deployment: Pushing to a designated Git branch triggers an automatic deployment to a web server.
  • Bare Repository Setup: Guides through setting up a Git repository specifically for deployment purposes.
  • Post-Receive Hooks: Configures the necessary Git hooks to execute deployment scripts.
  • Web Server Integration: Provides options for setting up a web server to serve the deployed content.
  • Use Case: A developer can push code updates to a main branch in a Git repository, and the changes are instantly reflected on the live website without manual intervention.

Quick Start

Follow the steps in this skill to set up a bare Git repository at /git/server and configure a post-receive hook to deploy content to /var/www/html.

Frequently Asked Questions about configure-git-webserver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up push to deploy for a web server using Git?

Push to deploy is configured by setting up a bare Git repository and using a post-receive hook to automatically deploy pushed content to your web server directory. This automates web deployment without manual steps.

What is a bare Git repository and why is it needed for automated deployment?

A bare Git repository is a repository without a working directory, used specifically for deployment to receive pushed code. It acts as the central hub where post-receive hooks trigger automated content deployment to the web server.

How do Git post-receive hooks work for web deployment?

Git post-receive hooks are scripts executed automatically after changes are pushed to a repository. For web deployment, these hooks check out the pushed content and copy it to the web server's serving directory for live updates.

Can I use push to deploy for serving content on any web server?

Push to deploy can be integrated with web servers to serve deployed content from a specified directory. The setup requires configuring the web server to point to the deployment path and managing appropriate file permissions.

What permissions and verification steps are needed for a Git push to deploy workflow?

Git push to deploy requires proper permission management for repository and web server directories to ensure successful execution of post-receive hooks. Verification strategies are established to confirm reliable automated deployments and service persistence.