I have a single Raspberry Pi 3b as a local file/media server running Jellyfin. I’m also running BOINC and seeding torrents of various Linux distributions. External HDD for storage, plus a thumb drive for the local media and another for the torrents so it only has to spin up when someone’s actually using it.

It’s not super-fast by any means, but it’s fast enough to listen to music over my LAN, which is the main thing I need it to do quickly. Though eventually I plan on setting up a better NAS on something with faster I/O.

If I was only using it for file sync, maybe. Though as it happens, the Linux desktop file sync client works fine on here, and I can work on files locally.

But that doesn’t help for things like, say, account settings, or tasks, or getting the right caldav URL to be able to plug it into a local client.

I’m using it for multiple services, not just one, and while some have apps available, not all do, and some features aren’t supported in the corresponding app.

I’m using Nextcloud for a lot more than just file sharing. Calendar, contacts, tasks, RSS reader sync, etc.

Same. Thunderbird now has native support for CalDAV and I use DAVx5 to sync it with my Android devices.

I’ve been using it for a while now. Currently on the “main” instance, cross-posting reviews to my website.

I used names of fictional robots, androids and self-aware computers (though I avoided HAL for obvious reasons) for a long time. These days my wife and I usually go with an indirect reference to the function or hardware - Ex. a device named Anathema, or a Raspberry Pi server named Marie (as in Marie Callendar, a former local pie/restaurant chain). I had an expendable frankenputer for tinkering that I called RedShirt.

Currently trying to come up with a name other than Chris for the PineTab 2.

Edit to add: Places I’ve worked have used Roman emperors, drink brands, Simpsons characters, and of course basics like “IIS1” “MAIL4” “QA-3” and so on. Some would add numbers to the names sequentially, others would use the last octet of the IP address.

At least until the NUCs run out, now that Intel’s discontinuing them

I tried setting up both for a local music server last year, and found Plex’s cloud requirements and constant upselling were more of a pain than it was worth. Jellyfin was the one I kept.

Similar experience here, esp. with the comments.

I think the tutorial posts are a great idea! Looking forward to the first one.

Yep. DigitalOcean specifically recommends SendGrid as an alternative: https://docs.digitalocean.com/support/why-is-smtp-blocked/

I like Alpine Linux for my VPS servers, but that’s because it’s very lightweight, not because of ease of use.

For user friendliness I’ve heard really good things about Yunohost, which runs on Debian and lets you manage a lot of different software, Nextcloud included

Same here. I tried both on a Raspberry Pi, and JellyFin was easier to set up and seemed to work better, at least within the LAN. I uninstalled Plex as soon as JellyFin was ready to go.

KeePass, mainly.

It’s not the static assets, it’s the database queries

I just commented on this in another thread: https://lemmy.world/comment/76011

TL;DR: The server-to-client interactions on Lemmy are a lot heavier than the server-to-server interactions, so even if you’re just using your own server to interact with communities on other servers, it should still take load off of the servers you would have been using directly.

One of the devs mentioned that the biggest draw on server resources is the direct web interaction, and loading pages, not the behind-the-scenes federation, where the database queries are simpler and the actions can be queued up and retried as needed. (I think apps would have the same issue since the server’s going to be doing the same kind of massive database queries to build your feed.)

If your comment takes a few minutes to get from your home server to another one when the site’s overloaded, it’s not a huge deal, but if your comment takes a few minutes to get from your browser to your server, the site’s basically down.

So moving yourself to a new server takes over the entire real-time load you would have been using, and the additional background load of sending threads to/from your server is a lot smaller.

On my own hardware: At home I have a Raspberry Pi 4 running JellyFin as a local media server, also experimenting with PiHole. One of these days I’d like to pull my NextCloud server in-house.

VPS: Nextcloud (including calendar, notes, contacts & RSS/Atom), GoToSocial, WordPress, Gemini, and personal website with a mix of home-grown parts and sections managed through Eleventy.

I’ve also experimented with self-hosting Calckey , Snac2 and Mastodon, but Mastodon’s too heavy for a single user and Snac2 is lighter than I want to go with for now. I may try Calckey again at some point, though.

Eventually I’d like to set up Wallabag and migrate from Pocket.