<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>configuration on nidomiro</title>
    <link>https://nidomiro.de/tags/configuration/</link>
    <description>Recent content in configuration on nidomiro</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 21 Aug 2020 12:00:00 +0000</lastBuildDate><atom:link href="https://nidomiro.de/tags/configuration/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>More secure deployments via ssh</title>
      <link>https://nidomiro.de/code/more-secure-deployments-via-ssh/</link>
      <pubDate>Fri, 21 Aug 2020 12:00:00 +0000</pubDate>
      
      <guid>https://nidomiro.de/code/more-secure-deployments-via-ssh/</guid>
      <description>If we deploy an application automatically we have to grant the CI (Continuous Integration) access to the server. Common practice is to do that via a GitLab Runner or a ssh account on the server.
Personally I would not recommend to use a GitLab Runner for deployments, because you have to maintain it. Another potential issue is, that you normally register runners for your whole GitLab instance or groups. That results in a scenario in which everyone can use that runner and accidentally (or not) destroy, for example, your production server.</description>
    </item>
    
    <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>
