easy-setup-webhook-production

Automate git pulls, changed-file detection, and conditional Laravel and Node.js builds via a deploy webhook.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/maxirodr/easy-setup-webhook-production --skill easy-setup-webhook-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: easy-setup-webhook-production
Source: https://github.com/maxirodr/easy-setup-webhook-production/tree/main/skills/fullstack-deploy-webhook
Command: npx skills add https://github.com/maxirodr/easy-setup-webhook-production --skill easy-setup-webhook-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill adds a production-ready deploy webhook endpoint to automate git pulls, detect changed files, and run conditional builds for Laravel and Node.js backends, reducing manual deployment steps.

Core Features & Use Cases

  • Conditional builds: only run composer, migrations, and frontend builds when relevant files change.
  • Per-request GitHub PAT and token-based authentication with IP throttling and a 7-day ban to protect deployments.
  • Works with Laravel and Node.js (Express + PM2) backends and can coordinate frontend assets across multiple directories.

Quick Start

Trigger the webhook by saying "add a deploy webhook" in your project or via the slash/API to start a secure, conditional deployment.

Frequently Asked Questions about easy-setup-webhook-production

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

FAQPage Schema
How do I set up a secure deploy webhook for Laravel and Node.js?

A deploy webhook automates git pulls and detects changed files to run conditional builds for Laravel and Node.js backends. It enforces security with token validation, IP throttling, and per-request GitHub PATs to protect automated deployments.

Can I run conditional frontend builds across multiple directories during a webhook deploy?

Yes, conditional frontend builds can run across multiple directories. The webhook detects changed files and coordinates frontend asset builds only when relevant files change, handling path and permission concerns in common hosting environments.

Does the webhook deployment handle safe-directory and permission issues in standard hosting environments?

Yes, the deploy webhook handles safe-directory and permission issues in common hosting environments. It ensures reliable operation by automatically addressing path and permission concerns during git pulls and conditional builds for Laravel and Node.js.

How do I secure automated git pull webhooks against unauthorized access?

Secure automated git pull webhooks using token-based authentication and IP throttling. The system enforces a 7-day ban for unauthorized access attempts and utilizes per-request GitHub PATs to protect Laravel and Node.js deployment pipelines.

What is the best way to only run database migrations when backend files change?

Using a conditional build webhook is the best way to run database migrations only when backend files change. It detects changed files and executes composer, migrations, and frontend builds only when relevant files are modified during the git pull.

Why does my Node.js PM2 deploy webhook fail to execute commands due to path issues?

Node.js PM2 deploy webhooks often fail due to path and permission issues. The webhook ensures reliable operation by addressing path, permission, and safe-directory concerns in common hosting environments to prevent command execution failures.