<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Ci-Cd on Panic! At The Terminal</title>
		<link>https://blog.nousiainen.xyz/tags/ci-cd/</link>
		<description>Recent content in Ci-Cd on Panic! At The Terminal</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 24 Oct 2026 21:16:14 +0300</lastBuildDate>
		
			<atom:link href="https://blog.nousiainen.xyz/tags/ci-cd/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Automatically Deploy a Hugo Site with GitLab CI/CD</title>
				<link>https://blog.nousiainen.xyz/docs/automation/gitlab-ci-hugo-deployment/</link>
				<pubDate>Sat, 24 Oct 2026 20:50:54 +0300</pubDate>
				<guid>https://blog.nousiainen.xyz/docs/automation/gitlab-ci-hugo-deployment/</guid>
				<description>&lt;h1 id=&#34;automatically-deploy-a-hugo-site-with-gitlab-cicd&#34;&gt;&#xA;  Automatically Deploy a Hugo Site with GitLab CI/CD&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#automatically-deploy-a-hugo-site-with-gitlab-cicd&#34;&gt;#&lt;/a&gt;&#xA;&lt;/h1&gt;&#xA;&lt;p&gt;I wanted publishing a change to this site to be more than a reminder to log in to the server and run Hugo by hand. My GitLab pipeline connects to my Hugo server and builds the site there when I push to &lt;code&gt;master&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This setup uses a self-hosted GitLab Runner that can reach the Hugo server on my home network. The pipeline does not upload a build artifact: the server has its own checkout of the blog repository, and the deploy job pulls the latest changes before running Hugo.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
