<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pipeline on Kliku Kliku</title><link>https://klikukliku.dev/tags/pipeline/</link><description>Recent content in Pipeline on Kliku Kliku</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 16 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://klikukliku.dev/tags/pipeline/index.xml" rel="self" type="application/rss+xml"/><item><title>Hugo + GitHub Actions: a simple deployment pipeline</title><link>https://klikukliku.dev/posts/deploy-hugo-by-github-actions/</link><pubDate>Tue, 16 Dec 2025 00:00:00 +0000</pubDate><guid>https://klikukliku.dev/posts/deploy-hugo-by-github-actions/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The simplest way to automatically deploy a Hugo site is this: keep the whole project in a GitHub repository, and let GitHub Actions build the site on every push and upload the generated public/ directory to your server over SSH using rsync.​&lt;/p&gt;
&lt;h2 id="assumptions"&gt;Assumptions&lt;/h2&gt;
&lt;p&gt;Here I assume two things.&lt;/p&gt;
&lt;p&gt;First, you already have a working Hugo project locally. For example, you created it with &lt;code&gt;hugo new site your_site&lt;/code&gt; and you checked that running the &lt;code&gt;hugo&lt;/code&gt; command locally correctly generates the public/ directory.​&lt;/p&gt;</description></item></channel></rss>