08-29-2023, 05:35 PM
Okay, I needed to review how this functionality is designed - sorry for the confusing instructions. The way it works is that you need to create an entry both on the server device, and on the client device. The name is the unique identifier, and the path is the path on the device. So you would do something like:
Server
Name: Noten
Path: /storage/emulated/0/documents/Noten
Client
Name: Noten
Path: /storage/0000-0000/Noten
While the sync is underway, the server will consult the mapping so that if it encounters the path "/storage/emulated/0/documents/Noten", it will find the name "Noten" assigned to that, so then it looks up "Noten" in the map from the client to see how it wants that path mapped to its storage. It will find "/storage/0000-000/Noten", so it will use that value for the files it needs to send to the client.
The reason it's set up this way is so that you can browse for the folder you want to use on each device using the file browser versus trying to type in the full path manually. Let me know if you run into problems using the feature now that I've explained it properly.
Mike
Server
Name: Noten
Path: /storage/emulated/0/documents/Noten
Client
Name: Noten
Path: /storage/0000-0000/Noten
While the sync is underway, the server will consult the mapping so that if it encounters the path "/storage/emulated/0/documents/Noten", it will find the name "Noten" assigned to that, so then it looks up "Noten" in the map from the client to see how it wants that path mapped to its storage. It will find "/storage/0000-000/Noten", so it will use that value for the files it needs to send to the client.
The reason it's set up this way is so that you can browse for the folder you want to use on each device using the file browser versus trying to type in the full path manually. Let me know if you run into problems using the feature now that I've explained it properly.
Mike