Don’t do it it’s shit in it’s current form . Turned it on and at first face unlock would kick in faster . then bizzarly it would activate simultaneously with either finger print or face and results in a loop where it would unlock then get kicked back to the lock screen and tell me that it was unlocked by the watch but it wasn’t unlocked . Got annoying enough that I had to hold the watch hand out away from the phone when I tried to unlock, eventually just said screw it and turned it off.

Pixel watch 2 and 8 pro.

Only had it work properly maybe a handful of times

https://www.smarthomebeginner.com/traefik-docker-compose-guide-2024/

Updated version of the guide

If that’s the case then a reformat into something that will support it is simple enough

I don’t know there are any limits to hardlinks other than that the source and destination needs to be on the same drive.This might help

If you get a reverse proxy setup all you need is port 80 and 443 and configure it it’ll expose the services that you want to be exposed through the subdomain Personally I’ve got Traefik service sitting on my media server and anything I want to expose goes through it .it has the details for the connection to cloudflare and so long as I direct it properly both on the container side and Traefik it’ll run as expected. The idea is if you go to say jellyfin.example.com cloudflare will direct that at at your reverse proxy(nginx in this case) which then redirects to the right machine/container because you entered from “jellyfin” .

The VPN gluten it is another container that will have the login details to your provider .

I’m still working my way through the self hosted rabbit hole myself, however I used a combination of Google and this sitehttps://www.smarthomebeginner.com/traefik-docker-compose-guide-2022/ The entire site not just the specific article linked . As well as https://trash-guides.info/