I don’t, because I switch it with something better if something like that happens.
I fuck numbers.
I don’t, because I switch it with something better if something like that happens.
They’ve not been used too much, I think. My laptop had very typical laptop usage: browsing, reading docs, coding, nothing storage intensive. On the server, the most intensive usage is for PhotoPrism and Jellyfin, and I don’t think that’s anything out of the usual.
I just have a couple of headless AlmaLinux boxes. Almost all of my apps are set up inside docker containers. If I have some time, I do plan to change the system to Debian stable/NixOS, given the recent RHEL drama. But otherwise, I think this is the way to go. Self hosting “solutions” tend to actually create more problems than they solve.
For tailscale/wireguard, you just need to open the port in your machine as if you’re using it locally. No need to forward port in your router. For all intents and purposes, you can treat all devices in your tailscale network as if they were local devices.
You don’t actually need to do reverse proxy while using tailscale. You can just use ports as if you’re on a local network.
The price is super low, but it’s been very reliable. Will highly recommend. You can see their current offers here.
If you want a free solution, wireguard and tailscale are your friends. It you’re willing to pay, get a cheap VPS (the one I use for this is from RackNerd for ~$12/yr). It’ll make the process very user friendly if you’re planning to share it with others.
Nowadays, I build them locally, and upload stable releases to registry. I have in the last used GitHub runners to do it, but building locally is just easier and faster for testing.
A great option that I personally use is FileShelter. It’s super light and seems to perform very well.
No, unfortunately.
I already have an external HDD. Maybe I can try the setup out with that.
Try out fileshelter. It’s super lightweight and works pretty reliably.