20 lines
1.8 KiB
XML
20 lines
1.8 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
|
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
|
<channel>
|
|
<title>Gitea on Comprofix</title>
|
|
<link>http://localhost:1313/categories/gitea/</link>
|
|
<description>Recent content in Gitea 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/categories/gitea/index.xml" rel="self" type="application/rss+xml" />
|
|
<item>
|
|
<title>Continuous Integration & 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><p>Since the reset of the website, I have been working on getting it to auto build and deploy using <a href="https://docs.gitea.com/usage/actions/overview">Gitea Actions</a>. Which is similar and compatible to <a href="https://github.com/features/actions">GitHub Actions</a></p>
<p>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.</p>
<h3 id="why-use-cicd" id=why-use-cicd>
 
 <span class="me-2">Why use CI/CD?</span>
 <a href="#why-use-cicd" class="anchor text-muted"><i class="fas fa-hashtag"></i></a>
 
</h3><p>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.</p></description>
|
|
</item>
|
|
</channel>
|
|
</rss>
|