<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>docker on nidomiro</title>
    <link>https://nidomiro.de/tags/docker/</link>
    <description>Recent content in docker on nidomiro</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Jul 2020 12:00:00 +0000</lastBuildDate><atom:link href="https://nidomiro.de/tags/docker/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Handling server configurations</title>
      <link>https://nidomiro.de/article/server-config-from-git/</link>
      <pubDate>Wed, 15 Jul 2020 12:00:00 +0000</pubDate>
      
      <guid>https://nidomiro.de/article/server-config-from-git/</guid>
      <description>1. IntroDuring my work as a programmer I often encountered that configuration and infrastructure files only lived on the servers they belog to. If they had a copy in git, the states would always divert over time. One reason for this diverting is that you actively have to put the changed files in git, after you finished your work. It’s simply a thing you can forget.
What do I mean by &amp;#34;infrastructure files&amp;#34;?</description>
    </item>
    
  </channel>
</rss>
