Spyke

Replies

Comment on

ISP not offering port forwarding anymore

Having your ISP do your port forwarding seems alien to me as that's not the norm where I am. Since it seems like a standard thing where you are, you may run the risk of another ISP doing the same thing. Personally, if the price is right, I'd take the latency hit and get a VPS and route all inbound traffic through that via wireguard.

Comment on

Struggling to Get Started Hosting a Mix of Local and Publicly Exposed Containers

So, docker networking uses it's own internal DNS. Keep that in mind. You can create (and should) docker networks for your containers. My personal design is to have only nginx exposing port 443 and have it proxy for all the other containers inside those docker networks. I don't have to expose anything. I also find nginx proper to be much easier to deal with than using NPM or traefik or caddy.

linux

Comment on

Can't figure out NFS file sharing

I'm 100% sure that your problem is permissions. You need to make sure the permissions match. Personally, I created a group specifically for my NFS shares then when I export them they are mapped to the group. You don't have to do this, you can use your normal users, you just have to make sure the UID/GID numbers match. They can be named different as long as the numbers match up.

Comment on

Self-hosted podcast aggregator/streamer, NOT downloader

Reply in thread

Kind of. I'm thinking something along the lines of sonarr/radarr/etc but with the ability to play/stream the podcast instead of downloading it. I tend to use web interfaces of stuff like that at work and can't really use my phone. Maybe I'll have to look into a roll-your-own solution using some existing stuff. Was hoping I wouldn't have to.