<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ansible on widerin</title><link>http://widerin.net/tags/ansible/</link><description>Recent content in Ansible on widerin</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2020 12:30:34 +0200</lastBuildDate><atom:link href="http://widerin.net/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><item><title>Maintaining manual gitlab installation with ansible</title><link>http://widerin.net/posts/2016/maintaining-manual-gitlab-installation-with-ansible/</link><pubDate>Sun, 03 Jan 2016 00:00:00 +0000</pubDate><guid>http://widerin.net/posts/2016/maintaining-manual-gitlab-installation-with-ansible/</guid><description>&lt;p&gt;A long time ago we started using &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt;. It was a greate step forward and definitly the right decision to switch from SVN to a distributed version control system. If you want to try &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt; you should definitly install it using &lt;a href="https://about.gitlab.com/downloads/"&gt;GitLab Omnibus distribution&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="manual-installation"&gt;Manual installation&lt;/h2&gt;
&lt;p&gt;But this long time ago there was no omnibus installation available so we installed &lt;a href="http://about.gitlab.com"&gt;GitLab&lt;/a&gt; with a manual &lt;code&gt;git&lt;/code&gt; checkout. Their monthly release cycle brought some upgrade effort every month - there was an upgrade tool available which was &lt;a href="https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/update/upgrader.md#gitlab-upgrader-deprecated"&gt;marked as discontinued&lt;/a&gt; - so i started to write some anisble scripts to handle the upgrade process.&lt;/p&gt;</description></item></channel></rss>