Because if you use relative bind mounts you can move a whole docker compose set of contaibera to a new host with docker compose stop then rsync it over then docker compose up -d.

Portability and backup are dead simple.

Thise are just different flavors. I need a pixel 8 pro xl equivalent device that runs linux natively. All thw postmarket phones are ancientx

Get rid of iscsi. Instead, use truenas scale for nas and use a zvol on truenas to run a vm of proxmox backup server. Run proxmox on the other box with local vms and just backup the vms to proxmox backup server at a rate you are comfortable with (i.e. once a night). Map nfs shares from truenas to any docker containers directly that you are running on your vms. map cifs shares to any windows vms, map nfs shares directly to any linux things. This is way more resilient, gets local nvme speeds for the vms and still keepa the bulk of your files on the nas, while also not abusing your 1gbit ethernet for vm stuff, just for file transfer (the vm stuff happens at multi GB speeds on the local nvme on the proxmox server).

In firefox on android i just flip the switch to request desktop site amd its mostly fine...

50 watts is maybe halfof one of my 10 gig switches...

Its decent except google amdoid aosp policy changes are screwing it over

just fyi, direct streaming isn't really direct streaming as you may think of it if you have specified samba shares on your nas instead of something on the vm running jellyfin. it will still pull from the nas into jellyfin and then http stream from jellyfin, whihc is super annoying.

I started on planka but ended on vikunja, it was just a lot nicer and more flexible for my needs.

That's the dude who was butt hurt about something this dude did: https://github.com/iamadamdev/bypass-paywalls-chrome

and so forked it and arguably does a better job, lol.

Thats not the feature i would port to paperless.paperless needs an o counter lol.

Jellyfin media player config setti gs tell ut to pass those through

I used to host anonaddy, I don't have the docker compose or configs anymore but I don't remember it being that bad. I stopped a couple years ago because simplelogin became included with my vpn subscription (and then I found fastmail, which has a similar feature built in so I ended up canceling simplelogin and that vpn and going to fastmail and mullvad). I basically just edite their example compose/env files and ran it behind my existing nginxproxymanager setup (that is gone now too, ended up moving to traefik but that's a story for another time). compose example here: https://github.com/anonaddy/docker/tree/master/examples/compose

It's really easy with headscale so I assume it must be really easy with tailscale too. How I did it was I created tiny tailscale vm to advertise the route to the ips I wanted access to on my internal lan. Then I shared the nfs share with the ip of that subnet router. now everything on my headscale network looks like it's coming from the subnet router and it works no problem (Just remember you have it setup this way in case you ever expand your userbase, as this is inherently insecure if there is anything connected to your tailscale that you don't want to have full access to your nfs shares)

Put them all on the same tailscale/netbird metwork and use restic to encrypted backup from each one to the others. Each hpuse gwts their files from there own box and has encrypted backups to pull from if their unit fails

Just came here to say this, it workson a 10 dollar a year racknerd vps for me no problem. Matrix chugs on my much bigger vps, although it is sharing that with a bunch of other things, overall it should have mich more resources.

Not being able to do graphene properly will hit everythibg if they screw up aosp i think

shouldn't be. If you gets ome sound out of jellyfin then the systems tuff should be working.

I did similar https://github.com/zombiehoffa/hyprjellynix

Edit I tried your way and it works better but is slightly more annoying to setup than running a nixos update (but only slightly more and making the nixos config file was a pain in the arse).

This is what I did too, after self hosting and self hosting anonaddy for a while. I really like how it integrates into bitwarden to give me most of what I liked about anonaddy as an included thing. I also did it ofr the same reason. Too many Eh holes out there that just want to bang on the mail server all day.

I ended up on purelymail.com for my machine sending email (it's dirt cheap I think I will be under their minmimum and it will cost something like 10 dollars a year for unlimited unique email addresses for my services)..

Pretty sure that title is firmly held by mcafe, even now.