

I use https://sftpgo.com/ at home for backing up and accessing files. It’s a private unshared network and it works well.
I use https://sftpgo.com/ at home for backing up and accessing files. It’s a private unshared network and it works well.
Spot on. You can’t self host without reading app and system logs.
I’m using https://sftpgo.com/, which uses WebDAV. It’s as basic as can be but I like it because it’s so basic. I can mount drives in windows and Linux and it has a basic webui for file management. The only problem for me is mobile apps. I’m trying out OwlFiles on Android and iOS; the free version includes WebDAV support, which works well.
Don’t make anything accessible via the internet if you’re new and starting out. The last thing you want is to accidentally leave a port open, leave an admin page with a default guessable password, or a piece of vulnerable software running and have someone gain access to your local network.
Start locally and learn the basics following the excellent advice of others here, and slowly build your knowledge until you understand the various moving and connecting pieces.
Haha it’s easy to overthink things sometimes. I’m guilty of that. I’m using SFTPGo at home to serve files from a small server.
Would this work? https://rclone.org/
Also hosted on… GitHub! 😀
It would be 2 or 3 people max.
Thanks. I’m just curious how much bandwidth would be consumed by the self hosted server if all video traffic is routed through it. If the video traffic is p2p then the self hosted server would be cheaper to maintain.
The self hosted part would be for discovery.
I used a NetCup VPS for a while but it would repeatedly have terrible performance, presumably because whoever I was sharing the server with was hammering the machine.