Post · bonfire.cafe

@stefano@mastodon.bsd.cafe · 2 months ago

Thanks to SeaweedFS, I've set up two replicas of the BSD Cafe's media. One is on a backup server (for disaster recovery purposes only, also containing the hourly zfs-autobackup backups), and the other is on a Raspberry Pi 4 running FreeBSD, which is one of my home backup servers - just one meter away from my desk.
I've also configured Nginx in a jail, so when I'm at home, the BSD Cafe's media is served directly from the local replica.
The performance is lightning fast.

#BSDCafe #SeaweedFS #S3 #Mastodon #SelfHosting #Homelab #FreeBSD #RunBSD

Robert George 𓇳𓃀𓁹𓏏𓇥𓆓𓀀

@rrgeorge@raphus.social replied · 6 days ago

@span stefano I was just reading about Seaweedfs and was thinking it could work well for mastodon, and then I found your posts about it!
Would you be willing to share your configuration details?

Anita Lewis

@ajlewis2@social.vivaldi.net replied · 2 months ago

@stefano

Very interesting. I've been wondering for some time if I could use a server.

Nux

@Nux@fosstodon.org replied · 2 months ago

@stefano Question, why the necessity for "object storage"? why not just "static file hosting"?

Stefano Marinelli

@stefano@mastodon.bsd.cafe replied · 2 months ago

@Nux the Mastodon media files are many - in a few days, you can go over the 200 GB.
This would require a lot of space. More, you can only have one Mastodon instance as the media files are stored locally.
With S3, I can have the media file in a different server (with large, spinning drives). This can be efficiently served by my own self hosted CDN and I can have two different Mastodon installations for the BSD Cafe (one is a backup one), as media will always be at "media.bsd.cafe".
In one word, scalability.