<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webhook on Terminal</title>
    <link>https://blog.panther.fun/tags/webhook/</link>
    <description>Recent content in Webhook on Terminal</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 30 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.panther.fun/tags/webhook/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to deploy with GitHub Webhook and Caddy</title>
      <link>https://blog.panther.fun/posts/how-to-deploy-with-gh-webhook-and-caddy/</link>
      <pubDate>Tue, 30 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.panther.fun/posts/how-to-deploy-with-gh-webhook-and-caddy/</guid>
      <description>&lt;blockquote&gt;&#xA;&lt;p&gt;In this post I will showcase my deployment pipeline setup to deliver updates to my blog an portfolio websites with the help of GitHub webhooks. I keep it as generalized as possible, however, some specifics are inevitable, though adaptable to other systems and tooling.&lt;/p&gt;&#xA;&lt;/blockquote&gt;&#xA;&lt;h2 id=&#34;the-problem&#34;&gt;The problem&lt;/h2&gt;&#xA;&lt;p&gt;I needed a way to instantly update my websites on my self-hosted werver, as it got really tedious to go in and pull in the changes from remote, then reload the webserver and do this for more and more sites (currently I run 3).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
