<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>migration &amp;mdash; Doctacosa</title>
    <link>https://blog.interordi.com/tag:migration</link>
    <description>🪶 I&#39;m a real blog! Maybe? 🤔  Thoughts by Stéphane, often in English, parfois en français!</description>
    <pubDate>Wed, 15 Apr 2026 06:05:02 +0000</pubDate>
    <item>
      <title>Misskey instance, all fixed and pretty again!</title>
      <link>https://blog.interordi.com/misskey-instance-all-fixed-and-pretty-again</link>
      <description>&lt;![CDATA[A few years ago, I had been meaning to run my own Fediverse instance and Misskey quickly caught my eye thanks to it&#39;s design that appealed to me: it worked very closely to how I&#39;d have designed it myself. Since I had a YunoHost installation online on a VPS, and Misskey was an available software to install, it made sense to set it up that way. Things quickly fell into place, and off I went with a public launch.&#xA;&#xA;It&#39;s only some months later that I noticed something was going wrong: it wasn&#39;t getting updated. Applications hosted on YunoHost depend on volunteers to keep them up to date and Misskey had recently released a major update with large technical changes. The people in charge of its packaging tried a few different things but couldn&#39;t make it work within the YunoHost environment. And so it was left to drift out of date.&#xA;&#xA;If it even needs mentioning, hosting a social media platform with no software updates is a Bad Thing™. The users aren&#39;t getting the latest new features and bug fixes, while the competition keeps moving forward. More importantly, though, it also means no security fixes. For an interconnected online platform, that&#39;s a Very Bad Thing™. I wanted to keep it going, but I also didn&#39;t want to take charge of the update process myself. I have enough on my plate already.&#xA;&#xA;And so it was left to hang for entirely too long. Eventually, I decided to see what it would take for me to make a clean install, without relying on YunoHost at all. I created a virtual environment and followed the official tutorial to build a test installation. Surprisingly enough, that came together pretty well, and I soon had a fresh setup running the latest version. All I needed was a place to host it. A Black Friday sale later, I had a second VPS that cost me less than half the price of the original. I had my way out.&#xA;&#xA;Over the holidays, I configured the new VPS with the needed dependencies. I then shutdown the live Misskey install and backed up everything I could. It turns out the brain of the system all lives in a single Postgres database, which is simple enough to back up and restore somewhere else. So, after following the Misskey installation tutorial but before launching it for the first time, I restored the database copy. When the time came for the first launch, the magic happened on its own: Misskey detected the existing database, updated what was required for the changes of the past two years, then came alive on its own. And that was pretty much it: I now had a fully refreshed instance going, on its own server, running on the latest version available!&#xA;&#xA;From here, future updates will be simple enough to handle. I won&#39;t have the convenience of YunoHost to back me up, but Misskey&#39;s updates are designed to be simple to apply, so a few command line inputs and I&#39;ll be set. That&#39;s one less thorn in my side!&#xA;&#xA;Meanwhile, my existing YunoHost installation is still running smoothly for several other tasks and I love the convenience it brings. It just wasn&#39;t meant to be for this specific use case.&#xA;&#xA;#Fediverse #Misskey #Migration #VPS #Projects&#xA;&#xA;- Doctacosa]]&gt;</description>
      <content:encoded><![CDATA[<p>A few years ago, I had been meaning to run my own Fediverse instance and Misskey quickly caught my eye thanks to it&#39;s design that appealed to me: it worked very closely to how I&#39;d have designed it myself. Since I had a YunoHost installation online on a VPS, and Misskey was an available software to install, it made sense to set it up that way. Things quickly fell into place, and off I went with a public launch.</p>

<p>It&#39;s only some months later that I noticed something was going wrong: it wasn&#39;t getting updated. Applications hosted on YunoHost depend on volunteers to keep them up to date and Misskey had recently released a major update with large technical changes. The people in charge of its packaging tried a few different things but couldn&#39;t make it work within the YunoHost environment. And so it was left to drift out of date.</p>

<p>If it even needs mentioning, hosting a social media platform with no software updates is a Bad Thing™. The users aren&#39;t getting the latest new features and bug fixes, while the competition keeps moving forward. More importantly, though, it also means no security fixes. For an interconnected online platform, that&#39;s a Very Bad Thing™. I wanted to keep it going, but I also didn&#39;t want to take charge of the update process myself. I have enough on my plate already.</p>

<p>And so it was left to hang for entirely too long. Eventually, I decided to see what it would take for me to make a clean install, without relying on YunoHost at all. I created a virtual environment and <a href="https://misskey-hub.net/en/docs/for-admin/install/guides/manual/">followed the official tutorial</a> to build a test installation. Surprisingly enough, that came together pretty well, and I soon had a fresh setup running the latest version. All I needed was a place to host it. A Black Friday sale later, I had a second VPS that cost me less than half the price of the original. I had my way out.</p>

<p>Over the holidays, I configured the new VPS with the needed dependencies. I then shutdown the live Misskey install and backed up everything I could. It turns out the brain of the system all lives in a single Postgres database, which is simple enough to back up and restore somewhere else. So, after following the Misskey installation tutorial but before launching it for the first time, I restored the database copy. When the time came for the first launch, the magic happened on its own: Misskey detected the existing database, updated what was required for the changes of the past two years, then came alive on its own. And that was pretty much it: I now had a fully refreshed instance going, on its own server, running on the latest version available!</p>

<p>From here, future updates will be simple enough to handle. I won&#39;t have the convenience of YunoHost to back me up, but Misskey&#39;s updates are designed to be simple to apply, so a few command line inputs and I&#39;ll be set. That&#39;s one less thorn in my side!</p>

<p>Meanwhile, my existing YunoHost installation is still running smoothly for several other tasks and I love the convenience it brings. It just wasn&#39;t meant to be for this specific use case.</p>

<p><a href="https://blog.interordi.com/tag:Fediverse" class="hashtag"><span>#</span><span class="p-category">Fediverse</span></a> <a href="https://blog.interordi.com/tag:Misskey" class="hashtag"><span>#</span><span class="p-category">Misskey</span></a> <a href="https://blog.interordi.com/tag:Migration" class="hashtag"><span>#</span><span class="p-category">Migration</span></a> <a href="https://blog.interordi.com/tag:VPS" class="hashtag"><span>#</span><span class="p-category">VPS</span></a> <a href="https://blog.interordi.com/tag:Projects" class="hashtag"><span>#</span><span class="p-category">Projects</span></a></p>

<p><em>– Doctacosa</em></p>
]]></content:encoded>
      <guid>https://blog.interordi.com/misskey-instance-all-fixed-and-pretty-again</guid>
      <pubDate>Fri, 03 Jan 2025 20:54:37 +0000</pubDate>
    </item>
  </channel>
</rss>