<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Git on Comprofix</title>
    <link>http://localhost:1313/tags/git/</link>
    <description>Recent content in Git on Comprofix</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Sep 2024 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/tags/git/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Continuous Integration &amp; Continuous Deployment</title>
      <link>http://localhost:1313/post/2024-09-21-websitedeployment/</link>
      <pubDate>Sat, 21 Sep 2024 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/post/2024-09-21-websitedeployment/</guid>
      <description>&lt;p&gt;Since the reset of the website, I have been working on getting it to auto build and deploy using &lt;a href=&#34;https://docs.gitea.com/usage/actions/overview&#34;&gt;Gitea Actions&lt;/a&gt;. Which is similar and compatible to &lt;a href=&#34;https://github.com/features/actions&#34;&gt;GitHub Actions&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Before implementing the action it was a manual process which required using docker commands to login, build and push the image to the container registry.&lt;/p&gt;&#xA;&lt;h3 id=&#34;why-use-cicd&#34; id=why-use-cicd&gt;&#xA;  &#xA;    &lt;span class=&#34;me-2&#34;&gt;Why use CI/CD?&lt;/span&gt;&#xA;    &lt;a href=&#34;#why-use-cicd&#34; class=&#34;anchor text-muted&#34;&gt;&lt;i class=&#34;fas fa-hashtag&#34;&gt;&lt;/i&gt;&lt;/a&gt;&#xA;  &#xA;&lt;/h3&gt;&lt;p&gt;It takes the manual process steps away and does them for you, helping you to avoid missing any steps and avoiding errors. This also makes the interaction seamless and automated.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
