<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Ubuntu Tips</title><link>https://ubuntips.com/posts/</link><description>Recent content in Posts on Ubuntu Tips</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://ubuntips.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>XenForo on Valkey: do you need php-redis?</title><link>https://ubuntips.com/posts/xenforo-valkey-php-redis-vs-sv-rediscache/</link><pubDate>Sat, 21 Nov 2026 14:45:00 +0800</pubDate><guid>https://ubuntips.com/posts/xenforo-valkey-php-redis-vs-sv-rediscache/</guid><description>&lt;p&gt;XenForo can store its cache in Redis or Valkey in two ways. The core provider needs the &lt;code&gt;php-redis&lt;/code&gt; extension. The popular SV RedisCache add-on ships its own pure-PHP client (Credis) and works with no extension at all. I wanted to know whether &lt;code&gt;php-redis&lt;/code&gt; is worth making a hard requirement for every XenForo server, so I measured it.&lt;/p&gt;&#10;&lt;p&gt;Short answer: no. On the forum, thread and mixed pages the two clients are within about 2% of each other, with the database on the same box or on a simulated remote server. The only larger gaps came from single noisy rounds, and they favoured the pure-PHP client. What matters is that the cache is on, and that the SV add-ons are installed.&lt;/p&gt;</description></item><item><title>Introducing Ubuntu Tips</title><link>https://ubuntips.com/posts/introducing-ubuntu-tips/</link><pubDate>Sat, 21 Nov 2026 09:00:00 +0800</pubDate><guid>https://ubuntips.com/posts/introducing-ubuntu-tips/</guid><description>&lt;p&gt;Most of the notes on this site started as comments in a shell script.&lt;/p&gt;&#10;&lt;p&gt;Provisioning an Ubuntu host is not hard, but it is full of decisions that are easy to get subtly wrong: the PHP-FPM process manager that looks fine at idle and collapses under load, the MariaDB buffer pool sized for a machine you no longer run, the sysctl values that only matter at 10,000 requests per second. Once you have worked them out, you write them down somewhere.&lt;/p&gt;</description></item><item><title>Why this blog is a static site</title><link>https://ubuntips.com/posts/why-this-blog-is-a-static-site/</link><pubDate>Fri, 20 Nov 2026 18:30:00 +0800</pubDate><guid>https://ubuntips.com/posts/why-this-blog-is-a-static-site/</guid><description>&lt;p&gt;A blog about hardening servers should not itself be the softest target in the stack. That ruled out the obvious choice.&lt;/p&gt;&#10;&lt;h2 id="the-requirements" class="heading-anchor"&gt;The requirements&lt;a class="anchor" href="#the-requirements" aria-label="Link to section: The requirements"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;The site needed to do five things:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;publish Markdown posts with syntax highlighting and tables,&lt;/li&gt;&#10;&lt;li&gt;load fast on a phone over a mediocre connection,&lt;/li&gt;&#10;&lt;li&gt;have nothing that needs a security patch on a Tuesday night,&lt;/li&gt;&#10;&lt;li&gt;cost approximately nothing to run,&lt;/li&gt;&#10;&lt;li&gt;keep every post in git, so a local agent or a shell script can edit it as easily as a person.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;That last point matters more than it sounds. If the source of truth is a database, every change has to go through an API, an admin session or a migration. If it is a directory of text files, an editor, a script and a coding agent all work the same way.&lt;/p&gt;</description></item><item><title>One idempotent script for the whole Ubuntu web stack</title><link>https://ubuntips.com/posts/one-idempotent-script/</link><pubDate>Wed, 18 Nov 2026 10:15:00 +0800</pubDate><guid>https://ubuntips.com/posts/one-idempotent-script/</guid><description>&lt;p&gt;The setup script behind most of these notes has one rule: every run must be safe to repeat. That constraint shapes the whole design, and it is the part most provisioning scripts get wrong.&lt;/p&gt;&#10;&lt;p&gt;This post is the long version of the script&amp;rsquo;s README: what it installs, what each flag does, what it refuses to touch, and how to verify a host afterwards. The source is at &lt;a href="https://github.com/droplinxuser/ubuntu-setup-script"&gt;droplinxuser/ubuntu-setup-script&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="why-idempotence-is-the-hard-part" class="heading-anchor"&gt;Why idempotence is the hard part&lt;a class="anchor" href="#why-idempotence-is-the-hard-part" aria-label="Link to section: Why idempotence is the hard part"&gt;#&lt;/a&gt;&lt;/h2&gt;&#10;&lt;p&gt;A script that only has to work once can do almost anything: append to a file, create a user, restart a service, assume the default config is still there. The second run is where the trouble starts. Appending twice duplicates a directive. Creating a user that already exists may reset its groups. Restarting a service in the middle of a config write can leave it running on half a file.&lt;/p&gt;</description></item></channel></rss>