<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>InstallingMastodon &amp;mdash; @dirkhaun XXL</title>
    <link>https://blog.tinycities.net/dirkhaun/tag:InstallingMastodon</link>
    <description>When 500 characters are not enough ...</description>
    <pubDate>Mon, 27 Apr 2026 20:20:15 +0000</pubDate>
    <item>
      <title>Moving to Mastodon</title>
      <link>https://blog.tinycities.net/dirkhaun/moving-to-mastodon</link>
      <description>&lt;![CDATA[So when it became obvious that #Twitter was going down the drain, I started looking for alternatives and quickly settled on #Mastodon. After a brief stint as @dirkhaun@troet.cafe I began to wonder how easy (or not) it would be to run my own instance.&#xA;&#xA;!--more--&#xA;&#xA;It has been a while since I administered a webserver. That was back in the Apache 1.3 days, long before Docker and all this new-fangled stuff (which I still don’t understand to this day) came along. So I got myself the smallest vServer I could find and gave the instructions a try. What can I say - it worked (almost) without a flaw.&#xA;&#xA;Now, those instructions are not for the faint of heart. But if you know where to look (and what to do) when, at the end of the day, nginx reports a permission issue trying to serve a CSS file, then you can do it.&#xA;&#xA;Setting up a Mastodon instance is one thing. Running an instance is another, which we’ll explore in another post …&#xA;&#xA;#MastodonAdventures #InstallingMastodon]]&gt;</description>
      <content:encoded><![CDATA[<p>So when it became obvious that <a href="/dirkhaun/tag:Twitter" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Twitter</span></a> was going down the drain, I started looking for alternatives and quickly settled on <a href="/dirkhaun/tag:Mastodon" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Mastodon</span></a>. After a brief stint as <a href="https://blog.tinycities.net/@/dirkhaun@troet.cafe" class="u-url mention" rel="nofollow">@<span>dirkhaun@troet.cafe</span></a> I began to wonder how easy (or not) it would be to run my own instance.</p>



<p>It has been a while since I administered a webserver. That was back in the Apache 1.3 days, long before Docker and all this new-fangled stuff (which I still don’t understand to this day) came along. So I got myself the smallest vServer I could find and gave the <a href="https://docs.joinmastodon.org/admin/install/" title="Installing Mastodon from source" rel="nofollow">instructions</a> a try. What can I say – it worked (almost) without a flaw.</p>

<p>Now, those instructions are not for the faint of heart. But if you know where to look (and what to do) when, at the end of the day, nginx reports a permission issue trying to serve a CSS file, then you can do it.</p>

<p>Setting up a Mastodon instance is one thing. Running an instance is another, which we’ll explore in another post …</p>

<p><a href="/dirkhaun/tag:MastodonAdventures" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">MastodonAdventures</span></a> <a href="/dirkhaun/tag:InstallingMastodon" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">InstallingMastodon</span></a></p>
]]></content:encoded>
      <guid>https://blog.tinycities.net/dirkhaun/moving-to-mastodon</guid>
      <pubDate>Sat, 10 Dec 2022 15:20:28 +0000</pubDate>
    </item>
  </channel>
</rss>