<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devops on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/categories/devops/</link>
    <description>Recent content in Devops on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 16 Mar 2020 17:43:01 +0100</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/categories/devops/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Backup Docker volumes with Ansible and restic</title>
      <link>https://janikvonrotz.ch/2020/03/16/backup-docker-volumes-with-ansible-and-restic/</link>
      <pubDate>Mon, 16 Mar 2020 17:43:01 +0100</pubDate>
      <guid>https://janikvonrotz.ch/2020/03/16/backup-docker-volumes-with-ansible-and-restic/</guid>
      <description>&lt;p&gt;In a new assignment I&amp;rsquo;m in charge of the infrastructure for a new startup. I was given a blank canvas and decided to use Ansible and Docker from the start. Therefore I&amp;rsquo;ve setup an Ansible project containing various roles and deployment scenarios. Have a look here for details: &lt;a href=&#34;https://github.com/Mint-System/Ansible-Playbooks&#34;&gt;https://github.com/Mint-System/Ansible-Playbooks&lt;/a&gt;. To put it simply, this project deploys open source web application as Docker containers on a target system. Currently, I am adding new features and polishing existing ones. An important role that is still missing is the backup. Having a robust and reliable backup and recovery system is key. While developing the backup system I had a few key points in mind:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
