If you want it to be an actual community service, then you want it to be something that outlives your residence, your tenure as event coordinator, and your interest in being the neighborhood IT guy. It’ll be much easier to transfer control of a VPS to your successor than to give them hardware that also hosts a bunch of your personal services.

You can start with a very small, nearly free VPS while you recruit users & scale up as (if) anyone bites. Probably even get the HOA to pay for it.

I got my Pi4 to be a media player - LibreElec or Kodi - for my old, not-smart TV. It plays my library of CDs&DVDs, frontend for OTA TV, and a variety of streaming services. Fanless, so it doesn’t distract from audio, low power, so I don’t mind leaving it on 24/7. You can configure it to listen to a USB IR receiver, but I control mine from phone via web. The actual media library/NAS and tvheaded run on an old desktop in another room.

My favorite thing is all the sensors you can hook up. Adafruit & Sparkfun have a wide array of sensors with breakout boards for simplicity and well documented python libraries. I started just logging temperature, humidity, then air quality, CO2 to my own database and web page, but eventually expanded to full HomeAssisstant system.

Pihole.

SATA is really convenient for larger storage, though. I keep my OS on nvmes, but I’ve got a couple of SATA drive and a hot swap bay for games, media, etc.

Tandoor: I ended up there because it has an API that I can access and cross-reference to my grocer (Kroger.com also has API) to get current pricing, calculate recipe costs, nutrient costs, or find what’s on special this week. It’s theoreticcally possible, but I haven’t sorted out how to integrate that directly into tandoor & its shopping lists.

A lot depends on how many users you expect and how much media you expect. For one or two users with that stack, transcoding media is really the only CPU load. If most of your media is already in your desired format, then that’s not a big deal.

My stack is pretty similar (no *arr, plus tvheadend, homeassistant and a kodi frontend) for two users and it sits near idle all day long. It runs on an N100 NAS system off Aliexpress with 16GB and will transcode 1080p to x264 at just about playback speed… System runs from a 100 GB nvme, with a couple half-full 4 TB WD Reds for data. 35-ish Watts, maybe an extra 5 when actively transcoding. Used to be ~150 USD,

If you want a lot of 4k content, then I’d definitely go with the GTX 1660.

Same. Eventually upgraded to a Pi 4, which doesn’t have any trouble with 1080p content. Pi 3’s onboard wifi was also problematic, and I had to run it over wired networking. Kept that for the Pi 4, so I don’t know if its wifi is any better.

The landscapers and cleaning staff are probably fine people.

Internet sarcasm is hard, and lemmy has a very general audience :) I’m always happy when someone gives me an excuse to do the math I was already curious about - it’s often not worth it, for just my own curiosity, but even a sarcastic or disingenuous prompt reminds me that there’s other casually curious people out there.

crypto - as in cryptography, not cryptocurrency - is just the library he’s using to generate the 128-bit random UUID. The snippet is interesting because he matched the original UUID in just over 5 hours. You’d expect to need more than 10^38 guesses to pick the same number again, which, even at 1 guess every microsecond, means something like 10^22 years.

I made a self-hosted forgejo repository of /etc. Commit messages aren’t always informative, and I’ve never actually gone back to the repository to figure something out, but it’s there, just in case. Me cosplaying a sysadmin.

[US] I have a z-wave network of Zooz Zen04 power-monitoring plugs and Minoston MP21 non-monitoring plugs. Automatically set themselves up by scanning the little QR code, Haven’t had any network drops or device failures in…3(?) years. One Zooz Zen15 high power, monitoring device occasionally (every few weeks) glitches and reports an spurious, instantaneous 5-20 kWh energy consumption

You don’t even need to learn HTML to do it. Any word processor will ‘save as HTML,’ but the markup should be straightforward enough for anyone considering selfhosting. CSS can be a real rabbit hole, but browser default styles aren’t awful.

I’ve used a retired desktop for my home server since 1999. It doesn’t have the fancy web-UI management of commercial NAS, but I’m comfortable with command line and config files.

At some point, I realized I could use its wifi card and hostapd to replace my WAP. That was a bit of an adventure initially finding a card that really supports AP mode and setting up hostapd, but has now allowed me to migrate from 802.11g to n to ac much cheaper than buying whole new devices,

Recently converted to an N100 with 4x ethernet ports, which let me unplug my little 5-port switch.

Managing this doesn’t feel like a second job: it’s stable and just works. Automatic updates, with kernel blacklisted; periodically log in, update kernel & reboot. It does give me the opportunity, when I get inspired, for a weekend project, like adding hostapd or a new service, either via docker or bare metal. I like that I have one device doing “NAS,” WAP, and router jobs.

Not the person you replied to, but a shoulder plane is kind of specialized tool. The blade goes all the way to the edge of the shoe, which lets you plane right up to square corners, such as a tenon, and the shoe is narrow, which lets you plane into grooves, such as dadoes, where general purpose planes won’t fit. The narrow shoe means you have to pay a lot more attention to keeping the plane square/flat to the surface, and the relatively short shoe means you have to pay a lot more attention to overall flatness of your work piece. If you need to true-up twisted & warped wood, a general-purpose bench plane will be a lot easier.

That drive averages 900 hours between power cycles? In Windows?

You need a lot of houseplants to make up for a human. Humans exhale something like 1 kg CO2/day where plants consume something like 0.2 kg/hr/100 m2. Figure natural light, maybe 6-8 hours of full sun in a day, and you’d need 60-80 m2 of leaf surface.

That kg/day of CO2 is enough to raise a 200 m2 home to 3000 ppm CO2. CO2 diffuses pretty well, but my 110 m2 house equilibrates around 1000ppm when it’s sealed against the summer heat.

This is one of my pet peeves with containerized services, like why would I want to run three or four instances of mariadb? I get it, from the perspective of the packagers, who want a ‘just works’ solution to distribute, but if I’m trying to run simple services on a 4 GB RPi or a 2 GB VPS, then replicating dbs makes a difference. It took a while, but I did, eventually, get those dockers configured to use a single db backend, but I feel like that completely negated the ‘easy to set up and maintain’ rationale for containers.

People will accept either intelligence or stupidity. They will pay for a flattering sycophant.

The services you’ve mentioned are all pretty low compute impact, just bandwidth, so I’d expect your MBP to be fine. Transcoding for jellyfin is the only real wildcard, and that depends on your media and client setups. I run pihole, homeassistant, immich, and kodi on a raspberry pi 4 with plenty of overhead for more services. NAS is nice if your library outgrows a single disk and your storage bandwidth gets choked by USB multiplexing.

My suggestion is to consider a cheap VPS and vanity domain for external access. Domains cheap as $5/year; fair VPSs cheap as $30/year. Use SSH to forward localhost ports on the VPS to container ports on the MBP, then nginx on thee VPS to reverse-proxy to those forwarded ports. You get unique names for every service, LetsEncrypt certificates, and an offsite location for critical backups. Make sure you are the one paying for VPS & DNS so they don’t get surprise-cancelled.

Second not using local.com If OP doesn’t want a real domain, use an unresolvable TLD, like “private” (so, pihole.private, audiobookshelf.private), but a real domain will just work better, will let them use real TLS certs, and prevent problems from apps bypassing system DNS. Even if it’s not as pretty or memorable as the hijacked domain name.