<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Update on Docka</title><link>https://docka.org/tags/update/</link><description>Recent content in Update on Docka</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 08 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://docka.org/tags/update/index.xml" rel="self" type="application/rss+xml"/><item><title>So it begins</title><link>https://docka.org/posts/2026-07-so-it-begins/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://docka.org/posts/2026-07-so-it-begins/</guid><description>&lt;p&gt;This is the first of, hopefully, many updates.
In this series of posts, I hope to explain what&amp;rsquo;s happened over the last month of work at Docka.
Since this project is still in its early stages, these posts will probably be long but boring for now, since most of it is general architecture stuff.&lt;/p&gt;
&lt;h2 id="no-central-server-only-hosts"&gt;No central server, only hosts&lt;/h2&gt;
&lt;p&gt;Puppet and Salt both use a central server to distribute tasks or state to the nodes.
This has some undeniable advantages.
It opens up a whole lot of options, like centralized reporting and ensuring all nodes apply the same state, but, as usual, this comes at a cost.
One downside is that this acts as a single point of failure.
While the server is down, at most, the nodes can apply their old state, and reports can&amp;rsquo;t be collected during this time.&lt;/p&gt;</description></item></channel></rss>