<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Redis – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/redis/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-GB</language><lastBuildDate>Sat, 21 Nov 2026 18:00:00 +0100</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/redis/index.xml" rel="self" type="application/rss+xml"/><item><title>AlmaLinux 10 on Trial: My Nextcloud Playbook, Nine Stumbling Blocks, and an AI That Works While I Am Out</title><link>https://www.apt-upgrade.me/2026/11/21/almalinux-10-test-nextcloud-playbook-claude-works-while-i-sleep/</link><pubDate>Sat, 21 Nov 2026 18:00:00 +0100</pubDate><guid>https://www.apt-upgrade.me/2026/11/21/almalinux-10-test-nextcloud-playbook-claude-works-while-i-sleep/</guid><description>&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; My Nextcloud servers run on AlmaLinux 9, and that will stay so for quite a while. Still, I wanted to know what my Ansible playbook needs for AlmaLinux 10. So I had a test server freshly installed with AlmaLinux 10.3 and handed the work to Claude. For part of the day I was out and followed the progress through the mails of the playbook runs. The result: nine stumbling blocks, nearly all of them in the hardening, not in Nextcloud. The two most interesting ones: kernel modules that moved to another package, and SELinux paths where &lt;code&gt;/run&lt;/code&gt; and &lt;code&gt;/var/run&lt;/code&gt; swapped roles. The code is in the branch &lt;a href="https://github.com/aptupgrademe/nextcloud_k3s/tree/el10-support"&gt;&lt;code&gt;el10-support&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>The Ansible Tour, Part 4: Nextcloud – Collabora, Push, Host Database and occ, Role by Role</title><link>https://www.apt-upgrade.me/2026/10/19/ansible-tour-part-4-nextcloud/</link><pubDate>Mon, 19 Oct 2026 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/19/ansible-tour-part-4-nextcloud/</guid><description>&lt;p&gt;&lt;em&gt;Part 4 of the &lt;a href="https://www.apt-upgrade.me/2026/10/14/ansible-tour-part-1-framework/"&gt;Ansible Tour&lt;/a&gt;. After the blog in &lt;a href="https://www.apt-upgrade.me/2026/10/16/ansible-tour-part-3-blog/"&gt;part 3&lt;/a&gt;, here comes the second application: &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt;. The series describes release &lt;a href="https://github.com/aptupgrademe/www_k3s/tree/v3.3.0"&gt;v3.3.0&lt;/a&gt;, with later changes added as updates. What matches the blog is only mentioned briefly; the focus is on what is different.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; Part 4 of the &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt; tour shows the second application: Nextcloud with &lt;a href="https://www.collaboraonline.com/"&gt;Collabora&lt;/a&gt; and push, for two groups of very different size, from the same code. Database and Redis run on the host here, Nextcloud, Collabora and the push service as Kubernetes objects, and settings are read, compared and only set when needed – plus a careful update playbook.&lt;/p&gt;</description></item><item><title>The Ansible Tour, Part 3: The Blog – WordPress, MariaDB and Redis on K3s, Role by Role</title><link>https://www.apt-upgrade.me/2026/10/16/ansible-tour-part-3-blog/</link><pubDate>Fri, 16 Oct 2026 20:00:00 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/10/16/ansible-tour-part-3-blog/</guid><description>&lt;p&gt;&lt;em&gt;Part 3 of the &lt;a href="https://www.apt-upgrade.me/2026/10/14/ansible-tour-part-1-framework/"&gt;Ansible Tour&lt;/a&gt;. &lt;a href="https://www.apt-upgrade.me/2026/10/15/ansible-tour-part-2-platform/"&gt;Part 2&lt;/a&gt; built the platform; this part puts the blog on it. The series describes release &lt;a href="https://github.com/aptupgrademe/www_k3s/tree/v3.3.0"&gt;v3.3.0&lt;/a&gt;, with later changes added as updates.&lt;/em&gt;&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; Part 3 of the &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt; tour puts the blog on the platform: four roles take &lt;a href="https://wordpress.org/"&gt;WordPress&lt;/a&gt; from an empty Kubernetes cluster to a running, configured and monitored website. The post shows the path of a request from the ingress via the page cache to PHP, &lt;a href="https://redis.io/"&gt;Redis&lt;/a&gt; and MariaDB, configuration from the outside, anonymous visitor statistics, the final check and the routine update.&lt;/p&gt;</description></item><item><title>How to Summon an Observability Beast: Installing Icinga 2 + IcingaDB + Web + Director on Debian</title><link>https://www.apt-upgrade.me/2025/12/09/how-to-summon-an-observability-beast-installing-icinga-2-icingadb-web-director-on-debian/</link><pubDate>Tue, 09 Dec 2025 20:00:00 +0100</pubDate><guid>https://www.apt-upgrade.me/2025/12/09/how-to-summon-an-observability-beast-installing-icinga-2-icingadb-web-director-on-debian/</guid><description>&lt;p&gt;&lt;em&gt;A nerdy homelab story featuring Redis, too many databases, and not enough sleep.&lt;/em&gt;&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;p&gt;&lt;strong&gt;In short:&lt;/strong&gt; Congratulations, traveller: anyone who wants to monitor their homelab like a responsible adult ends up with the full Icinga stack sooner or later. This post shows step by step how to put together Icinga 2, Redis, the database, IcingaDB, Icinga Web 2, the API and the Director on &lt;a href="https://www.debian.org/"&gt;Debian&lt;/a&gt; – with a pinch of sarcasm and too little sleep.&lt;/p&gt;</description></item></channel></rss>