<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Gitlab on 412Linux</title>
    <link>https://412Linux.io/categories/gitlab/</link>
    <description>Recent content in Gitlab on 412Linux</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 07 Dec 2023 09:31:27 +0100</lastBuildDate>
    <atom:link href="https://412Linux.io/categories/gitlab/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Gitlab double upgrade</title>
      <link>https://412Linux.io/code/gitlab-double-upgrade/</link>
      <pubDate>Thu, 07 Dec 2023 09:31:27 +0100</pubDate>
      <guid>https://412Linux.io/code/gitlab-double-upgrade/</guid>
      <description>Due to life circumstances, I had neglected my home Gitlab instance. I logged in the other day to perform some &amp;ldquo;quick&amp;rdquo; maintenance. Unfortunately, I found that I was more behind than expected. So much so, that I would need to perform a double upgrade of Gitlab going from 16.1 to 16.3 then ultimately to 16.6. After running a gitlab reconfigure, I found the Let&amp;rsquo;s Encrypt certs required an update. After making the required DNS and firewall changes, I was able to complete the necessary cert updates.</description>
    </item>
  </channel>
</rss>
