this post was submitted on 18 Jan 2026
32 points (94.4% liked)

Selfhosted

54845 readers
344 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Basically, I want to make one for some multiplayer games out there (along with Stoat communities, or something similar - what do y'all recommend? Bonus if it has voice chat).

What would I need, and how can I set this up safely without having my own network hacked beyond comprehension? I could do it off site from home too if that's better.

I have a Raspberry Pi 4gb, but also an old DDR3 16gb desktop with a PCI network card available if that's recommended.

you are viewing a single comment's thread
view the rest of the comments
[–] potatoguy@lemmy.eco.br 5 points 4 days ago* (last edited 4 days ago) (1 children)

I tried one time to make my own personal instance https://potato-guy.space/, that ended because I forgot my ssh keys when i distrohopped, but I could make some suggestions.

  • Get anti-bot protection, like cloudflare (or something more privacy friendly) AND something like anubis or a nginx plugin.
  • Don't make it on your network if you don't know what you're doing, put it on a rented VM on the "cloud", the chance of someone breaking into your network because you misconfigured something, if you don't know about network security, is above zero and horizontal hopping in a network is feasible.
  • A raspberry pi is enough, just use some optimzed settings and use the picture server settings to use postgresql too, just create a new database on postgresql and hook that on, it will be more cpu and ram friendly.
  • If you really want it on your network, double check and triple check every router configuration, put it on a virtual network, inside a VM, outside your own network so horizontal attacks don't happen.
  • Edit: Also, use btrfs with compression enabled for the postgresql database, it will make the database faster as the read and write ops will be 2x (with lzo, almost no cpu usage) to 3x (with zstd, but with more cpu usage) faster.

This is the docker-compose config for lemmy: https://github.com/LemmyNet/lemmy/tree/main/docker

This is the tutorial for it: https://join-lemmy.org/docs/administration/install_docker.html

Some drama happened in the past on those docker configs, check all and put your domain where needed.

[–] moonpiedumplings@programming.dev 1 points 4 days ago* (last edited 4 days ago) (1 children)

Do you have a source or benchmarks for the last bullet point?

I am skeptical that optimizations like that wouldn't already be implemented by postgres.

Edit: Btrfs has the worst performance for databases according to this benchmark.

https://www.dimoulis.net/posts/benchmark-of-postgresql-with-ext4-xfs-btrfs-zfs/

[–] potatoguy@lemmy.eco.br 1 points 4 days ago* (last edited 4 days ago)

Postgresql, or any database, don't compress its database files.

As the checks are done in the database files, at the disks, but cached in memory, when it does some expensive check or put any data into disk, if the data is compressed, then it will be faster.

I only have old data, but this could be of help, compression help disk reads and writes, even facebook uses btrfs for disk compression. Everyone should compress their databases in 2026, it makes it take less space and faster.

Edit: specifically, on the postgresql database, there isn't the default configuration without compression, but you can take some guesses from the other benchmarks, and these are old benchmarks, things changed since 2017, 9 years ago.

Edit 2: These are more noticeable on the data being capped by the ssd/hdd or sata connection, as it's a raspberry pi, it will surely be capped by the data transmission, sending and receiving less data will make the reads/writes faster.

Edit 3: This is another benchmark too, not postgresql, but on limited bandwidth to the disk