At some point, every home server enthusiast hits the same wall. The files are on one machine. You need them on another. So you copy them over. Then you edit something. Now you have two versions. Which one is current? You copy it back. You forget to copy it back. You copy the wrong direction.

There is a better way, and it has existed since 1984.

NFS — Network File System — is one of those Unix technologies that has quietly outlasted everything built to replace it. The concept is almost offensively simple: a folder on one machine appears as a folder on another. Not synced, not replicated, not copied. The same folder. When you write a file on your laptop, it lands on your server. When you read it on your desktop, it comes from the same place. There is no version conflict because there is only one version, in one location, accessible from everywhere on your network.

This becomes genuinely useful the moment you have more than one computer and more than one user. Your NAS stores the files. Your server, your laptop, your desktop — they all see the same filesystem, with the same permissions, without any of them needing local copies. You stop thinking about where things are and start thinking about the things themselves.

It is also the foundation for more interesting setups. Virtual machines sharing storage with their host. Media servers that read from a central pool. Backup scripts that run on one machine and write to another as if it were local disk. Once NFS is mounted, everything that works with files works across your network without modification.

The setup takes about fifteen minutes and most of it is a one-time configuration. After that it just works — quietly, reliably, the way good infrastructure should.

Full walkthrough on the forum: NFS Share Remote Mount