-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NasMounts config.json missing 'Path' variable #104
Comments
yep it's a known problem. Name is used as path... you can edit config.json to correct it, waiting for a fix. |
Yep, I accept suggestion on how the input fields should be named, and how many of them ... |
1 - There is still a problem mounting nfs share : name is used as path. |
For me we should have :
did i miss something ? i can work on this this wek-end i think.. (mostly with NFS i don't know if i can mount a cifs share to test) |
With the last built (from today 12/01/16) I think that network drive configuration is not clear. With cifs files, it's rather easy even if the name of the share and the path should be separate. With nfs same thing but path is much more complicated.
|
Mpasteur I read your comment after I post... |
no problem. If you have some time to test my PR i would be glad to have some feedbacks... |
I'll try tonight. But I see a lot of activities ! |
@mpasteur |
You need to update both the UI and the Backend, plus you need to delete /data/configuration and reboot |
Hello, |
i think im running the latest build and i dont see an option in the ui for path, how do i update both the backend and the ui. |
... and it just magically fixed itself. weird? |
@ecto1a2003 you'll find some useful information here : https://gitter.im/volumio/Volumio2 |
the 'Name' is used as a path leading to mounts that are multiple folders deep. for example 'e/music' is the path to the share but the mount folder is created with the same path
The text was updated successfully, but these errors were encountered: