<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hugo / WebDev on Mexicali IT</title><link>https://mxlit.com/technologies/hugo-/-webdev/</link><description>Recent content in Hugo / WebDev on Mexicali IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 Mar 2026 16:30:00 -0800</lastBuildDate><atom:link href="https://mxlit.com/technologies/hugo-/-webdev/index.xml" rel="self" type="application/rss+xml"/><item><title>Leaving SaaS: Creating Your Own Telemetry Microservice with FastAPI and Docker</title><link>https://mxlit.com/kb-00047/</link><pubDate>Thu, 05 Mar 2026 16:30:00 -0800</pubDate><guid>https://mxlit.com/kb-00047/</guid><description>&lt;p&gt;Static site generators (SSGs) like Hugo are unbeatable in speed and security. By compiling everything into pure HTML files, we eliminate attack vectors and database dependencies. However, a classic problem arises: How do we add basic interactivity, such as a &amp;ldquo;Likes&amp;rdquo; counter, without ruining the static nature of the site?&lt;/p&gt;
&lt;p&gt;Initially, the easy answer is to integrate a third-party service (SaaS). It&amp;rsquo;s fast and it works. But as infrastructure engineers, relying on an external API presents us with two fundamental problems: the loss of sovereignty over our data and the inevitable paywalls that arise when traffic increases. The ultimate solution isn&amp;rsquo;t to look for a heavyweight open-source clone, but to build our own minimalist microservice.&lt;/p&gt;</description></item><item><title>HUGO: Implementing Serverless Telemetry in Hugo with Lyket (Applause Button)</title><link>https://mxlit.com/kb-00046/</link><pubDate>Thu, 05 Mar 2026 13:00:00 -0800</pubDate><guid>https://mxlit.com/kb-00046/</guid><description>&lt;p&gt;Implementing Serverless Telemetry in Hugo with Lyket&lt;/p&gt;
&lt;p&gt;Migrating to a static site generator (SSG) like Hugo offers massive advantages in security and speed by not relying on databases to serve content. However, this presents a challenge when we want to integrate basic interactivity, such as a &amp;ldquo;Like&amp;rdquo; or &amp;ldquo;Applause&amp;rdquo; counter in our Knowledge Base.&lt;/p&gt;
&lt;p&gt;Instead of setting up additional containers or databases just to record clicks, the most elegant solution is to use a decoupled serverless approach. This is where &lt;strong&gt;Lyket&lt;/strong&gt; comes in, an external API that handles transactional telemetry while our frontend remains 100% static.&lt;/p&gt;</description></item></channel></rss>