<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>All Posts - Ciro Lucio Tecce</title>
        <link>http://localhost:1313/en/posts/</link>
        <description>All Posts | Ciro Lucio Tecce</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 04 Aug 2026 00:00:00 &#43;0000</lastBuildDate><atom:link href="http://localhost:1313/en/posts/" rel="self" type="application/rss+xml" /><item>
    <title>Local Inference on an Asrock BC250 Cluster</title>
    <link>http://localhost:1313/en/posts/bc250-cluster-inferenza-locale/</link>
    <pubDate>Tue, 04 Aug 2026 00:00:00 &#43;0000</pubDate>
    <author>Ciro Lucio Tecce</author>
    <guid>http://localhost:1313/en/posts/bc250-cluster-inferenza-locale/</guid>
    <description><![CDATA[<h2 id="intro">Intro</h2>
<p>I&rsquo;ve always been a tech enthusiast, and a few years ago I fell into the homelabbing rabbit hole. With all the AI hype around, developing an interest in local inference felt like the next natural step.</p>
<p>But even beyond the technical challenges and fascination this space brings, I strongly believe that the future of AI is local. This is both for practical reasons regarding the sustainability of the AI ecosystem as a whole—which currently consumes resources completely out of proportion to the actual returns companies get based on pricing—and for the democratization of access to these tools, which cannot and should not remain exclusively in the hands of big external providers.</p>]]></description>
</item>
<item>
    <title>Monitoring llama.cpp with Prometheus and Grafana...</title>
    <link>http://localhost:1313/en/posts/monitoring-llm-homelab/</link>
    <pubDate>Wed, 03 Jun 2026 00:00:00 &#43;0000</pubDate>
    <author>Ciro Lucio Tecce</author>
    <guid>http://localhost:1313/en/posts/monitoring-llm-homelab/</guid>
    <description><![CDATA[<h2 id="introduction--experiment-small-dream-big">Introduction — Experiment small, dream big</h2>
<p>For the past few months, one of the mini PCs in my homelab has been getting a bit of a rough ride, or rather, it&rsquo;s been pushed a little beyond what its original specs were meant for. I&rsquo;m asking it to do things it was never designed for: load LLMs, process prompts, generate text, and analyze images. This is discrete GPU territory, but it doesn&rsquo;t know that and keeps going anyway.</p>]]></description>
</item>
<item>
    <title>From SSH to git push: how I automated deployments on my homelab</title>
    <link>http://localhost:1313/en/posts/homelab-deploy-template/</link>
    <pubDate>Tue, 02 Jun 2026 00:00:00 &#43;0000</pubDate>
    <author>Ciro Lucio Tecce</author>
    <guid>http://localhost:1313/en/posts/homelab-deploy-template/</guid>
    <description><![CDATA[<h2 id="introduction---why-having-a-home-server-is-a-good-idea-and-how-to-manage-it">Introduction - Why having a home server is a good idea and how to manage it</h2>
<p>A couple of years ago I fell down the homelab rabbit hole. Like any self-respecting nerd, I couldn&rsquo;t resist the temptation of building my own little server. I&rsquo;ve always been fascinated by compact, quiet setups — not necessarily the most powerful, but the ones best suited to the job. After reading dozens of posts on <a href="https://www.reddit.com/r/homelab/" target="_blank" rel="noopener noreffer ">r/homelab</a> and watching pretty much every video of the <a href="https://www.servethehome.com/introducing-project-tinyminimicro-home-lab-revolution/" target="_blank" rel="noopener noreffer ">TinyMiniMicro</a> series, I finally took the plunge.</p>]]></description>
</item>
</channel>
</rss>
