manwichmakesameal
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.
Of course it’s Missouri………
links is pretty lightweight. All joking aside, I’d look at adding RAM to it if possible. That’s probably going to help the most.
Also, to add to this: you’re setup sounds almost identical to mine. I have a NAS with multiple TBs of storage and another machine with plenty of CPU and RAM. Using NFS for your docker share is going to be a pain. I “fixed” my pains by also using shares inside my docker-compose files. What I mean by that is specify your share in a volume section:
volumes:
media:
driver: local
driver_opts:
type: "nfs"
o: "addr=192.168.0.0,ro"
device: ":/mnt/zraid_default/media"
Then mount that volume when the container comes up:
services:
...
volumes:
- type: volume
source: media
target: /data
volume:
nocopy: true
This way, I don’t have to worry as much. I also use local directories for storing all my container info. e.g.: ./container-data:/path/in/container