INTERACT FORUM

More => Old Versions => JRiver Media Center 27 for Windows => Topic started by: TheShoe on April 17, 2021, 09:13:25 am

Title: Cross Platform Paths - was this ever done?
Post by: TheShoe on April 17, 2021, 09:13:25 am
Referring to a specific post in an old thread - Cross Platform Paths

https://yabb.jriver.com/interact/index.php/topic,121740.msg842166.html#msg842166

Currently my library server is Windows, supporting multiple windows clients (and JRemote)

I'd like to move the server to Linux, but know that paths to files will be different.  The clients are all on the same network, and generally Windows.  Would like them to be able to access the files directly - but the pathing will be a problem.  Hendrik had what I thought was the best solution - leave the library as-is, e.g. referencing paths using the convention of the OS it's deployed on, and then on each client implement mapping outside of the library.  Seems most flexible and also avoids messing with the integrity of the library.

Is it possible to do this?  The thread ended and I've not found if it was ever implemented.
Title: Re: Cross Platform Paths - was this ever done?
Post by: glynor on April 17, 2021, 06:18:21 pm
I brought up something similar recently on the Mac board:
https://yabb.jriver.com/interact/index.php/topic,129204.0.html

No, it has not been done to my knowledge (and if so, someone please set us right).
Title: Re: Cross Platform Paths - was this ever done?
Post by: BillT on April 18, 2021, 03:12:34 am
I'm not sure if it will serve the purpose of accessing files locally on the client, but I use the original Windows library on my Linux server but use the portable library option on the server to point the windows path to the file location on the Linux server. You have to set up Samba shares on the Linux machine and map them on the clients to replicate the original setup.

I did this because I couldn't get file rename to work on the Linux machine; it would do a few hundred files then crash and corrupt the database. It has another advantage in that the library can be edited directly on a windows machine, which you can't easily with Linux file paths.

Obviously this won't work with Macs.