<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>wopi – apt-upgrade.me – Homelab, Linux &amp; DevSecOps</title><link>https://www.apt-upgrade.me/tag/wopi/</link><description>One nerd's homelab: Linux, Kubernetes, security, and the occasional disaster.</description><language>en-US</language><lastBuildDate>Mon, 19 Oct 2026 15:52:20 +0200</lastBuildDate><atom:link href="https://www.apt-upgrade.me/tag/wopi/index.xml" rel="self" type="application/rss+xml"/><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 15:52:20 +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: Nextcloud. 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;Nextcloud is a file cloud: files, calendars, contacts, team folders and – with Collabora – documents edited together in the browser. Two of the three servers run it, for groups of very different size, with the same code and different values in the inventory. The work is shared by &lt;code&gt;next_mariadb&lt;/code&gt; and &lt;code&gt;next_redis&lt;/code&gt; (database and cache on the host), &lt;code&gt;next_k3s_deploy&lt;/code&gt; (Nextcloud, Collabora and the push service as Kubernetes objects), &lt;code&gt;next_config&lt;/code&gt; (Nextcloud’s settings) and &lt;code&gt;nextcloud_verify&lt;/code&gt;, plus the update playbook.&lt;/p&gt;</description></item><item><title>Bare Metal to K3s: A Nextcloud Migration Battle Log</title><link>https://www.apt-upgrade.me/2026/09/21/bare-metal-to-k3s-a-nextcloud-migration-battle-log/</link><pubDate>Mon, 21 Sep 2026 21:50:44 +0200</pubDate><guid>https://www.apt-upgrade.me/2026/09/21/bare-metal-to-k3s-a-nextcloud-migration-battle-log/</guid><description>&lt;p&gt;Today I moved a production &lt;a href="https://nextcloud.com/"&gt;Nextcloud&lt;/a&gt; from a cozy &lt;strong&gt;native bare-metal install&lt;/strong&gt; to a shiny &lt;strong&gt;K3s/container&lt;/strong&gt; stack. On paper: pull a backup, restore it, flip DNS, done. In practice: a series of small landmines, each invisible until you step on it. Here&amp;rsquo;s the battle log. 🪖&lt;/p&gt;&#10;&lt;h2 id="step-1-shovel-the-data-"&gt;Step 1: shovel the data 🚚&lt;/h2&gt;&#10;&lt;p&gt;The heavy lifting was an &lt;code&gt;rsync&lt;/code&gt; of ~360 GB of user data plus a ~330 MB SQL dump from the backup box into the new node. Because I pre-synced earlier in the day, the final run only shipped the delta — the whole thing came down to a fast incremental copy. Lesson old as time: &lt;em&gt;pre-seed, then the cutover sync is tiny.&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>