<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Github on Puppeteers Oy</title>
		<link>https://www.puppeteers.net/tags/github/</link>
		<description>Recent content in Github on Puppeteers Oy</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Tue, 01 Dec 2020 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://www.puppeteers.net/tags/github/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Fattening the workflow, part 3: GitLab and similar</title>
				<link>https://www.puppeteers.net/blog/fattening-the-workflow-part-3-gitlab-and-similar/</link>
				<pubDate>Tue, 01 Dec 2020 00:00:00 +0000</pubDate>
				<guid>https://www.puppeteers.net/blog/fattening-the-workflow-part-3-gitlab-and-similar/</guid>
				<description>&lt;p&gt;In the previous posts of this series I discussed &lt;a href=&#34;https://www.puppeteers.net/blog/fattening-the-puppet-workflow-part-1-the-control-repository/&#34;&gt;the control repository&lt;/a&gt; and &lt;a href=&#34;https://www.puppeteers.net/blog/fattening-the-workflow-part-2-r10k/&#34;&gt;r10k&lt;/a&gt;. The last component in fattening the workflow is Git provider such as GitLab, GitHub or Bitbucket. Nowadays all of them are reasonable choices for storing private Git modules, which Puppet control repositories and site-specific modules tend to be. One of the biggest advantages of GitLab over its competition is that it is open source and can be installed locally.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
