{"id":2894,"date":"2022-11-10T10:33:00","date_gmt":"2022-11-10T08:33:00","guid":{"rendered":"https:\/\/www.bnamed.blog\/en\/?p=2894"},"modified":"2022-11-10T12:19:42","modified_gmt":"2022-11-10T10:19:42","slug":"how-we-set-up-our-own-mastodon-server","status":"publish","type":"post","link":"https:\/\/www.bnamed.blog\/en\/2022\/11\/how-we-set-up-our-own-mastodon-server\/","title":{"rendered":"How we set-up our own Mastodon server"},"content":{"rendered":"\n
\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

As we reported earlier<\/a>, the takeover by Elon Musk of Twitter clearly was the straw that broke the camel’s back and eventually caused an exodus of twitter-users towards Mastodon. <\/p>\n\n\n\n

Mastodon is very much different from how Twitter works. Contrary to having one centralized system to control everything, Mastodon works via many independent nodes that magically interconnect to each other (just like the internet itself). Everybody can run and control their own Mastodon server.<\/p>\n\n\n\n

This means that, just like having an e-mail address under your own domain name, you can also have a mastodon account under your own domain name. <\/p>\n\n\n\n

Clearly: this is what we wanted and we wouldn’t settle for less! <\/strong><\/p>\n\n\n\n

First step: register our own address. We selected a .social domain name<\/a> because this points out that it’s a social media account. And… hey: there’s a promo ongoing for the .social extension<\/a>. But any domain name extension can be used. You can even create a sub-domain under your existing domain name and use that. <\/p>\n\n\n\n

We then started looking for an existing provider that would allow us to connect our own domain name to their services. <\/p>\n\n\n\n

Apparently it’s currently not possible to share a Mastodon server. The current version of the server software available, assumes you’ll have one domain name per server.<\/p>\n\n\n\n

So no “shared hosting”. A dedicated instance is required if you want to use your own domain. This is an existing business model already offered by a couple of providers<\/a>. Because we were looking for a solution at the peak of the exodus, some of the providers however were closed for new subscriptions. The remaining providers were, according to our feeling, either too expensive or didn’t offer the control we hoped to have. <\/p>\n\n\n\n

This made us eager to get our hands dirty and actually run our own instance. Joinmastodon.org has a nice overview of what is needed for this<\/a>. But quickly we noticed almost every singly software used by Mastodon turned out to be a competing solution compared to what we were comfortable to work with. Maybe we didn’t want our hands to get this dirty after all.<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

Eventually we came about the possibility of installing Mastodon through Cloudron<\/a>. So let’s dig in!<\/p>\n\n\n\n

We rented a cheap Ubuntu 20.04 machine. Not the Linux distribution we’re used to work with, but we’re reasonably comfortable with it and eventually Cloudron will manage this for us.
Installing Cloudron is just three lines of code
<\/p>\n\n\n\n

wget https:\/\/cloudron.io\/cloudron-setup
chmod +x .\/cloudron-setup
.\/cloudron-setup<\/p>\n\n\n\n

The installation will take some time. Once you have Cloudron on your server, Mastodon is just one click (and some more patience) away. <\/p>\n\n\n\n

We’re now all ready and set with our own branded Mastodon account. So let’s meet at https:\/\/bnamed.social\/@bnamed<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"

As we reported earlier, the takeover by Elon Musk of Twitter clearly was the straw that broke the camel’s back and eventually caused an exodus of twitter-users towards Mastodon. Mastodon is very much different from how Twitter works. Contrary to having one centralized system to control everything, Mastodon works via many independent nodes that magically […]<\/p>\n","protected":false},"author":1,"featured_media":2912,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[5],"tags":[],"_links":{"self":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/2894"}],"collection":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/comments?post=2894"}],"version-history":[{"count":6,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/2894\/revisions"}],"predecessor-version":[{"id":2918,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/2894\/revisions\/2918"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/media\/2912"}],"wp:attachment":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/media?parent=2894"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/categories?post=2894"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/tags?post=2894"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}