<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Linux on Mexicali IT</title><link>https://mxlit.com/technologies/linux/</link><description>Recent content in Linux on Mexicali IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 08 Apr 2026 16:00:00 -0700</lastBuildDate><atom:link href="https://mxlit.com/technologies/linux/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero-Cost HA: VPS and On-Premise Failover via Cloudflare Tunnels</title><link>https://mxlit.com/kb-00090/</link><pubDate>Wed, 08 Apr 2026 16:00:00 -0700</pubDate><guid>https://mxlit.com/kb-00090/</guid><description>&lt;p&gt;&lt;strong&gt;The Problem: Eliminating Single Points of Failure in Hybrid Infrastructure&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;In infrastructure design, High Availability (HA) and mitigating single points of failure usually require complex and expensive architectures. When seeking resilience for personal services or documentation platforms, the goal is to ensure web traffic automatically switches if a physical node or cloud provider goes down.&lt;/p&gt;
&lt;p&gt;One approach to achieve this is maintaining a hybrid architecture: a commercial VPS as the primary node and an On-Premise server as backup. Through CI/CD (such as GitHub Actions), source code can be compiled and synchronized simultaneously to both nodes. Data and web containers are replicated, but the challenge lies in routing: how do we failover public traffic without paying for a dedicated Load Balancer?&lt;/p&gt;</description></item><item><title>Ubuntu 24.04 Desktop to Server: Complete In-Place Conversion Guide</title><link>https://mxlit.com/kb-00089/</link><pubDate>Tue, 07 Apr 2026 17:00:00 -0700</pubDate><guid>https://mxlit.com/kb-00089/</guid><description>&lt;p&gt;There are multiple scenarios in infrastructure administration where a machine initially configured with Ubuntu Desktop ends up assuming exclusive server roles. Whether you are repurposing hardware for your home lab or transforming a development environment into a production node, the graphical environment (GNOME) becomes an unnecessary waste of CPU and RAM.&lt;/p&gt;
&lt;p&gt;While the traditional solution would be to format and install the Ubuntu Server ISO, this is not always viable. If you already have complex configurations, automations, or running services, a clean setup means rework. In this article, we will address how to perform an &lt;em&gt;in-place&lt;/em&gt; conversion from Ubuntu 24.04 Desktop to a pure &lt;em&gt;headless&lt;/em&gt; environment, removing the graphical layer without compromising your current data or workloads.&lt;/p&gt;</description></item></channel></rss>