<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Alek&#x27;s Blog - systemd</title>
    <subtitle>My Blog to share my knowledge</subtitle>
    <link rel="self" type="application/atom+xml" href="https://blog.none.at/tags/systemd/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://blog.none.at"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-05-12T00:00:00+00:00</updated>
    <id>https://blog.none.at/tags/systemd/atom.xml</id>
    <entry xml:lang="en">
        <title>NFS to Object Store Sync with rclone and systemd</title>
        <published>2026-05-12T00:00:00+00:00</published>
        <updated>2026-05-12T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              aleks
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.none.at/blog/2026/2026-05-12-nfs-sync-via-rclone/"/>
        <id>https://blog.none.at/blog/2026/2026-05-12-nfs-sync-via-rclone/</id>
        
        <summary type="html">&lt;p&gt;I needed to sync and back up an NFS share to cloud storage for example to Azure Blob Storage — reliably, with a hard “no version must ever be lost” SLA, and for a file tree that could grow to 1M+ files. This post documents the architecture decisions, the core sync script, the lab setup for testing without real NFS or Azure access, and the packaging for RPM, DEB, Nix and Alpine. The sync engine is &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;rclone.org&quot;&gt;rclone&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;The result is &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git001&#x2F;nfs-sync-via-rclone&quot;&gt;nfs-sync-via-rclone&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;</summary>
        
    </entry>
    <entry xml:lang="en">
        <title>haproxy-spoe-rs: Deployment</title>
        <published>2026-04-12T00:00:00+00:00</published>
        <updated>2026-04-12T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              aleks
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://blog.none.at/blog/2026/2026-04-12-haproxy-spoa-rs-deployment/"/>
        <id>https://blog.none.at/blog/2026/2026-04-12-haproxy-spoa-rs-deployment/</id>
        
        <summary type="html">&lt;p&gt;This post covers deploying the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https:&#x2F;&#x2F;github.com&#x2F;git001&#x2F;haproxy-spoe-rs&quot;&gt;haproxy-spoe-rs&lt;&#x2F;a&gt;
SPOA agent in production. It is a companion to the
&lt;a href=&quot;&#x2F;blog&#x2F;2026&#x2F;2026-04-12-haproxy-spoa-rs&#x2F;&quot;&gt;architecture post&lt;&#x2F;a&gt; which explains the library design.&lt;&#x2F;p&gt;
&lt;p&gt;The agent and HAProxy run as &lt;strong&gt;separate services&lt;&#x2F;strong&gt; — HAProxy connects to the agent over TCP.
This keeps their lifecycles independent and allows scaling each side separately.&lt;&#x2F;p&gt;</summary>
        
    </entry>
</feed>
