<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on dev.endevour</title><link>https://devendevour.iankulin.com/tags/automation/</link><description>Recent content in Automation on dev.endevour</description><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Wed, 26 Jul 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://devendevour.iankulin.com/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>First Ansible Playbook</title><link>https://devendevour.iankulin.com/first-ansible-playbook/</link><pubDate>Wed, 26 Jul 2023 00:00:00 +0000</pubDate><guid>https://devendevour.iankulin.com/first-ansible-playbook/</guid><description>&lt;p&gt;&lt;img src="https://devendevour.iankulin.com/images/biomage_biomechanical_cyborg_computer_hacker_keyboard_protrudin_3d895c1b-0776-4f6e-b1a6-733b5622ea5d.jpg" alt="" class="img-responsive"&gt; &lt;/p&gt;
&lt;p&gt;In the &lt;a href="https://devendevour.iankulin.com/getting-started-with-ansible/"&gt;previous post&lt;/a&gt; , we looked at getting up and running with Ansible, including using the ad-hoc mode to send commands to our servers. We had a inventory file called hosts that had groups of server IP addresses and a simple &lt;code&gt;ansible.cfg&lt;/code&gt; file that pointed to our inventory file.&lt;/p&gt;
&lt;h3 id="playbooks"&gt;Playbooks&lt;/h3&gt; &lt;p&gt;Ansible playbooks are used to collect together a description of the state we want in a server. When the playbook is executed, Ansible figures out what things need need changed, and changes them. If you&amp;rsquo;re used to the procedural nature of a bash script, where things proceed from one step to the next, and there might be decision branches, this requires an adjustment in your thinking. This is similar to the adjustment I had getting my head around &lt;a href="https://betterprogramming.pub/swiftui-understanding-declarative-programming-aaf05b2383bd" target="_blank" rel="noopener"&gt;SwiftUI&lt;/a&gt; , and moving from JS to &lt;a href="https://levelup.gitconnected.com/why-react-is-declarative-a300d1e930b7?gi=3d11485226b4" target="_blank" rel="noopener"&gt;React&lt;/a&gt; .&lt;/p&gt;</description></item><item><title>Getting Started with Ansible</title><link>https://devendevour.iankulin.com/getting-started-with-ansible/</link><pubDate>Wed, 19 Jul 2023 00:00:00 +0000</pubDate><guid>https://devendevour.iankulin.com/getting-started-with-ansible/</guid><description>&lt;p&gt;&lt;img src="https://devendevour.iankulin.com/images/cyberpunk_24_k_hyper_realistic_a_thousand_details_hyper_detaile_841f4769-e869-497f-a804-c9fade21e150.jpg" alt="" class="img-responsive"&gt; &lt;/p&gt;
&lt;p&gt;Ansible is a system for executing commands on remote systems. It allows a declarative approach - so if you run a playbook (the system configuration files are called playbooks) that says a system has a Docker container running Jellyfin, Ansible will check if that&amp;rsquo;s true, and if not, make it so. Ansible is best used when you have a large number of systems to maintain, but even with a small number, it serves to document systems as well as to automate their creation.&lt;/p&gt;</description></item></channel></rss>