tofuwabohu

Sounds interesting, thanks!

I'm not really up to date on homelabbing hardware, but I'm surprised to see how much the whole thing is centered around raspis given how expensive they are for their relatively low capacities. Possibility of offgriding your homelab is an interesting project but not what I'd center this "revolution" around given most homelabs stay, well, home.

DIY 10" racks for second hand mini PCs would interest me way more but looking at the YouTuber's big lab racks affordability doesn't seem to be much of a factor.

How is there more or less benefit to federation with this content?

Yeah, I feel like exposing ports 80 and 443 towards an up to date nginx/whatever is referred to as a super dangerous thing in this community and also the selfhosted subreddit. Recommending cloudflare is almost the default, which I find a bit sad given many people selfhost to escape the reliance on big monopolist companies.

One can add different layers of security of course, but having nginx with monitoring in it's own VM without keys to jump to another VM is enough of risk mitigation for me.

I think the best thing of reddit is them having so many actually active niche subreddits. Many people saying Lemmy doesn't need to grow don't seem to care much about that which surprises me a bit.

Op mentioned pixelfed for several people though, is it possible to reverse proxy through tailscale from a VPS or similar? It's probably not suitable to have a service for several people behind a vpn

Yes! Mostly having a plan on how to make your service reachable in the internet while keeping the rest of your local stuff shutdown.

Many people recommend cloudflare, but I don't think it's necessary. If you get a public IP from your ISP, it's relatively easy with dyndns. Personally, I have a virtual machine running nginx as a reverse proxy and configured the router to forward port 80 and 443 to that machine.

You got quite good answers already, here and in the other thread.

My suggestion is to not start with pixelfed but something else (simple stuff like dokuwiki, you can use it to document your stuff while you're at it) to get an understanding of the whole process (running the service itself, making it available to the internet after hardening your infrastructure a bit etc).

Also, if you're not settled for how to do it exactly, give Docker a try. There's a reason it's popular among selfhosters!

Mio Mio gehört zu Berentzen?

Thanks! I don't know much about shielding, do you have a hint what I'm looking for?

I could also ask the manufacturer if I can just use an extension cable to put the controller away. That would probably be the easiest solution!

Most important: replace the raspi SD card with an SSD

General hardware: see if I find a better solution than my current Proxmox box (repurposed desktop which consumes 60w idling but is capped to 16GB Ram)

Incoming traffic: currently having a VM that runs nothing but nginx and certbot. Considering switching to another reverse proxy and, more important, get proper monitoring of the logs (e.g. IP detection, 403, etc)

Maybe add some iam like authentik

Finding a solution for selfhosting podcasts client with sync on Android and Linux.. gpodder never really seemed to work, considering audiobookshelf.

Probably setting up calibre web and gethomepage

Keeping what I have and maybe optimize a bit:

• Prometheus stack
• plenty exporters
• Nextcloud
• paperless
• home assistant, mosquitto
• pihole
• vaultwarden
• selfoss

On VPS:

• Mastodon
• Bookwyrm
• some WordPress (want to move this to my homeserver as well)

This should be possible, in nginx you would just have near identical entries that deliver the same content. The service itself sometimes takes a domain to build internal links etc, and those usually only take one.