Host your own Mastodon Instance with Docker (Part 3)

My Mastodon instance is now running without any issues for around to months. But still, there are some things that I noticed during that time that I want to address. My biggest concern is that the machine Mastodon is running on will run out of disk space. That’s why in this post I’m going to describe how I moved the static file storage of my Mastodon instance to a S3 compatible object storage provider. If your interested in the whole process of setting up your own Mastodon instance, make sure to check out Part 1 and Part 2 of the setup too.

Host your own Mastodon Instance with Docker

After the recent events on Twitter, the open source microblogging platform Mastodon seems to become more popular every day. The cool thing about Mastodon is, that you can run your own Mastodon instance. By doing so, you have full control over your data, and you can still interact with all the other users on any other Mastodon instance. In this blog post I’m setting up my own Mastodon instance with Docker.

Auto-generate SSL Certificates for Azure Container Instances

If you want to spin up a container on Azure and need to access it over HTTPS, you are probably better of running it inside an Azure App Service instead of using Azure Container Instances, as App Services support auto-generated SSL certificates out of the box. But if for some reason you want to achieve the same with Azure Container Instances, I’m going to show you how to do it in this post by using the sidecar pattern with the reverse proxy Caddy.

Passwortloser SSH Zugriff

In meinem Heimnetzwerk betreibe ich diverse virtuelle Maschinen, auf denen Services laufen die ich tagtäglich benutze oder die zum Ausprobieren neuer Tools dienen. Auf diese verbinde ich mich in der Regel via SSH. Damit ich mir nicht für jede virtuelle Maschine ein Passwort merken muss, habe ich jeweils SSH Keys für den passwortlosen Zugriff eingerichtet.