

Yeah, the system was on a single server at first and eventually expanded to either a docker swarm or Kubernetes cluster. So the single server acts as both a docker host and an NFS server.
I’ve had this happen multiple times, so I use this pattern by default. Mostly these are volumes with just config files and other small stuff that it’s OK if it’s duplicated in the docker cache. If it is something like large image caches or videos or other volumes that I know will end up very large then I probably would have started with storage off the server in the beginning. It saves a significant amount of time to not have to reconfigure everything as it expands if I just have a template that I use from the start.
Mine has those, but it was a different model that had the hardware required to do WiFi. Likely it’s not included and unless the device was designed to modify, it’s likely that the motherboard doesn’t have a way to add it easily and there won’t be much space to do your own WiFi card and soldering if the board does have the connections and support in the firmware/BIOS. Best bet would be a USB WiFi card.