Especially with music, if any of this is plain HTTP (or any other plaintext, non-encrypted protocol) and you live in a lawsuit happy jurisdiction you might end up with piracy letters in the mail.
Especially with music, if any of this is plain HTTP (or any other plaintext, non-encrypted protocol) and you live in a lawsuit happy jurisdiction you might end up with piracy letters in the mail.
I’m thinking of building my own and having it use Paperless’ API for invoices, receipts, etc.
I finally gave this a go a few days ago but wasn’t in love with the UI. I’d contribute but it’s written in .NET.
I’ll probably build something myself. One thing I’d like to do is have it integrate with other APIs (like Paperless).
I’d curl
from a machine on the same WiFi network as the phones just to confirm that HTTP is working. That way you’re not dependent on browsers that can be more finicky for debugging.
I’ve noticed that but I thought I just didn’t know how to persist it correctly and never bothered to find out how. If what you’re saying is accurate (which I don’t doubt) that sucks.
GL.iNet actually has a decent UI too. When I’m on the road I don’t necessarily love hitting the CLI (okay fine I secretly do); they keep the updates going for a long time too.
I didn’t have a great reason other than mind-blowing performance on my LAN, and with large files (which I have a lot of) performance is better too. Probably I’m not smart enough to answer this well, but I did just see this today: https://www.phoronix.com/review/linux-611-filesystems/2
I’m a huge fan of XFS for network mounts. I think everyone else here is right that the best filesystem will depend on the OS, and picking one to make it compatible with everything has serious tradeoffs.
Plain HTTP means anyone between you and the server can see those credentials and gain access.
It it using HTTP Basic Auth by chance? It would be so easy to put nginx (or some other reverse proxy with TLS) in front and just pass the authentication headers.