Pi 4 should be plenty to run Jellyfin, homeassistant, pihole and octoprint. Docker setup is pretty straightforward, and I can vouch that HA & pihole containers work great on RPi, if you want to leave the Jellyfin setup as-is and put the others alongside.

If you’re looking for an excuse to expand, my vote is for an N100 type system. I got one with 4 ethernet ports, PCIe for a wifi card, couple of NVME slots, and a half dozen SATA ports for $100-150. That’s a huge step up in potential without much increase in power draw. With the right wifi card, you can even use it to replace your WAP/router.

Are you sure the ISP will delegate a /56? Mine supports prefix delegation, but will only give a /64, and it seems like subdividing that ¿into /72s? would be questionable.

Fetched it. Started it. Did a really nice job fetching my whole health record from insurance co & has a wide array of compatible providers. Decent presentation of repeated test results. It’s got a bunch of areas “not implemented yet,” but it’s a decent way to visualize the records. Probably even better if you have health records from multiple providers.

Safe deposit box is exactly the right size to hold a 3.5" HDD. Or several. I keep a backup Yubikey there too, because I love the physical token 2FA, but I’m pretty sure I’m going to lose it.

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.

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

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.

At the time, it was part of the whole poisonous structure of the 2017 tax bill, where everything would expire after Trump’s presumed 2nd term to sabotage his Democratic successor, confident that no one has long enough memory to realize where it came from.

You can only spin drives down if they’re idle. If you have a service that touches it - say, homeassistant logging data, tvheadend updating EPG - then they’re going to keep spinning.

I switched from an I3-530, nominal TDP 73W, to an N-100, nominal TDP 7W, and power from the wall didn’t change at all. Even the i3 ran around 0.1 CPU load, except when transcoding, and I’m left with the impression that most of the power goes into HDDs, RAM, maybe fans, and PS losses. My sense is that the best way to decrease homelab power use is to minimize the number of devices. Start with your seyrver at 60W, add a WAP at 10-15W, maybe a switch at 10-15W… Not because of the CPUs, necessarily, but because every CPU every CPU comes with systems to keep the CPU going, keep the power regulated, etc.

It’s from a Molly White doot. I don’t see it on her website https://www.citationneeded.news/ but she’s definitely been all over Trump’s crypto.

I’m not a huge docker expert, but I recently spun up a tandoor…dev, and their config instructions explicitly point out a couple of mounts that have to be volumes and can not be binds.

Docker’s own comments are https://docs.docker.com/engine/storage/volumes/ which my tl;dr is faster, can be shared by multiple containers, and can be a remote (NFS/CIFS) target.

I’d guess that maintainers use the volume structure to let docker handle the details of creating and maintaining the mount, rather than put it on the user, who may be spinning up their first-ever docker and may make all kind of naive mistakes.

The reason for his post was that a provider shut down his access on the accusation of CSAM, without (according to him) much if any investigation. Cloud providers have all manner of automated systems for reporting CSAM, copyright, and other potential abuses, and generally seem to take a guilty-until-proven-innocent approach. They may or may not even be responsive to defense or explanation. Colo isolates you from abuse of those systems.

My ISP seems to use just normal DHCP for assigning addresses and honors re-use requests. The only times my IP addresses have changed has been I’ve changed the MAC or UUID that connects. I’ve been off-line for a week, come back, and been given the same address. Both IPv4 and v6.

If one really wants their home systems to be publicly accessible, it’s easy enough to get a cheap vanity domain and point it at whatever address. rDNS won’t work, which would probably interfere with email, but most services don’t really need it. It’s a bit more complicated to detect when your IP changes and script a DNS update, but certainly do-able, if (like OP) one is hell bent on avoiding any off-site hardware.

Daniel Stenberg claims that the curl bug reporting system is effectively DDOSed by AI wrongly reporting various issues. Doesn’t seem like a good feature in a code auditor.

I, for one, would rather just see them use a couple of 2/0 AWG welding cables, bolted onto a 5mm copper plate on the board. If you need 200 amps, make it look like 200 amps.

The UPS needs some power to keep its batteries full. Could be that it’s triggering off some threshold to do a charge cycle instead of just running a constant trickle. I’ve noticed that my laptop and phone charge that way, for example.

…hanging from their cables…