2024-12-22, 05:50 PM
It's a simple string replacement. Remote path is where the server looks for files, local path is how the client should reach those same files.
Example:
Your library is mounted on your server at
The library is available over your network at
You have two options here.
- Option A: one to one replacement
- Remote Path:
- Local Path:
- Option B: Multi match replacement
- Remote Path:
- Local Path:
Option A works just fine and is effectively a 1:1 mapping of folder on the server vs how a client can see it.
Option B can simplify the mappings if you have multiple paths stored in a single location. ie: this would work for both
Example:
Your library is mounted on your server at
/mnt/media/Movies.The library is available over your network at
nfs:/export/MoviesYou have two options here.
- Option A: one to one replacement
- Remote Path:
/mnt/media/Movies- Local Path:
nfs:/export/Movies- Option B: Multi match replacement
- Remote Path:
/mnt/media- Local Path:
nfs:/exportOption A works just fine and is effectively a 1:1 mapping of folder on the server vs how a client can see it.
Option B can simplify the mappings if you have multiple paths stored in a single location. ie: this would work for both
/mnt/media/Movies and /mnt/media/Shows, assuming both of them are also available under the same relative NFS path.