habitualTartare

Official Recommendations for low power: Intel 12th gen or above N series platforms Apple M Series Mac mini Rockchip RK3588 / RK3588S SBC (Advanced Users Only)

Note 10th gen and older integrated graphics are losing support in Linux due to Intel dropping SDK support or something. Don’t buy a nuc or small PC with Intel 10 or older but if you have one it’s fine for now.

Another option would be an old laptop with dedicated graphics (e.g. e waste/recyclers). then you can get away with older than 10gen Intel since you’d be using the external graphics. Just research how to limit battery charging in the bios since it’s always going to be plugged in.

Top Motivation: Cost

The several hundred dollars a year and hours spend is definitely worth saving that $14-30/month in subscriptions right? right?

yunohost + ebay or old office desktop (or literally any computer you can get your hands on for cheap). There’s a lot of people with very strong opinions but you really don’t need much.

As other commenters have said yes you can run these depending on the Pi. Do note however if you need transcoding, A Pi is not recommended by jellyfin:

jellyfin.org/docs/general/…/hardware-selection#po…

Most Single Board Computers (SBC): Most SBCs (including the Raspberry Pi, especially the Raspberry Pi 5) are too slow to provide an acceptable Jellyfin experience as they often lack proper support for hardware acceleration. If you really want to run Jellyfin on an SBC, you may wish to consider models based on the following platforms: Rockchip RK3588 / RK3588S, Intel Core, Intel 12th gen N series

if you want to lock your phone to one app when you hand it to them you can use app pinning in settings. otherwise look into creating a user profile and see what you can do to lock that down.

what type of phone/OS are your phone and computer?

there’s some hands-on controls too that may be useful but it starts with just giving them their own profile or login that’s ideally with as few permissions as possible. For android, there’s profiles which you may be able to lock down a bit more than your own profile. Apple had family mode settings that you may be able to turn on and off when they have the device. For a computer, same approach. Standard user account with whatever you installed using an admin account and lock down content via DNS like cloudflare for families, adguard-dns.io/public-dns.html, a self hosted one or something like nextdns.io.

Worth a read if you haven’t: en.wikipedia.org/…/Wikipedia:Signs_of_AI_writing

but hasnep covered it well. also emoji use, overly wordy and that graph/tree is a common style of llms.

looking at the install script it looks like casaOS is installed directly on the laptop. you can check by running

systemctl status casaos

in a terminal. if that’s not found try docker ps -a to list all docker containers including any not currently running.

I’ve never used Netbird or casaOS. I run debian and docker containers. I would recommend looking at wg-easy as a VPN. it also uses wireguard but for me it just works. you open 1 port on UDP and route it to wireguard, it’s a secure way to access your network and is quite hard to detect from the outside.

I’ve heard good things about caddy.

“data at rest/LUKS” is something you should consider if your personally worried about someone physically trying to get information off your computer/server. if the server is running or an attacker gets into your system remotely, it doesn’t matter. as a beginner, I would determine if the data your saving is worth the extra headache of encrypted media, especially if something goes wrong/an update breaks something or your configs/setup messes something up. if you do, keep a copy of your decryption keys on a NEW USB drive (flash drives go bad) or printed out in addition to saved on your workstation/laptop/password manager.

Personally for new systems I recommend Proxmox hypervisor instead of running directly on the laptop. having your debian OS/casa or whatever you use virtualized gives you the ability to take snapshots in time of your OS, makes backups easier and can help when you expand later (backup and restore on the new computer running proxmox). mine is: proxmox on bare metal old office PC

• | debian > docker w/ portainer (I plan to replace portainer w/ komono)
• | TrueNAS > S3 bucket application (garage)

if Casa becomes limiting as you learn and grow, I would recommend docker compose stacks w/ a web gui like komono.

one final note, although AI can be very useful for troubleshooting and getting some code to fix a problem (albiet logic/problem solving isn’t their strength) it’s awful for retaining knowledge and learning in the same way that using a calculator or other tool before fully understanding how to do addition/multiplication manually. I would strongly recommend taking some time to learn the basics without ai if your goal is to understand how everything works. resources to start with are using and reading “man + command”, command help flags, online courses and websites: linuxbasecamp.com explainshell.com - copy paste a command with all arguments and it tells you what it does. …linuxfoundation.org/…/introduction-to-linux/

you could definitely run proxmox in a VPS but I was thinking more of debian in the cloud. Then exporting that computer from wherever you host it as a ova file then importing it into your local server: pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Automa…

and on the ram issue, I’m running on over 10 year old workstation hardware ddr3. it doesn’t take much to run.

NAS with zfs storage does typically want a lot of ram (e.g. truenas) but still for a small home environment it works fine with a lot less than 64gb.

I run proxmox bare metal (debian-based hypervisor) and virtualize debian which has all my docker containers.

with virtualization you can take a snapshot and backup everything that way. super simple to roll back if you mess something up. the added bonus is you could probably take a snapshot of your VPS and migrate it to a local vm.

Ubuntu is something I played with about a decade ago and I never felt like I was “missing” something for debian, especially on servers.