More > JRiver Media Center 25 for Linux
JRiver MC25 Docker Image with WebUI as VNC
max096:
Did change something in the openbox config. Now the JRriver Window should always stay in the background.
Before if you opened some option window and then clicked on the jriver window. That brought the main JRiver window in front of the options window. And then you could not do anything until you restarted the container (since you cannot interact with jriver when the option window is open and you cannot interact with the option window when the jriver window is in front of it).
shortie:
Excellent, thank you! Good choice for the base image, too. Im especially pleased that you provided a compose as well as a Dockerfile, rolled it all up into gitlab and have it set up for ci.
max096:
Glad you like it. :)
Another thing that I wanted to try at some point is use http://eradman.com/entrproject/ to force an auto import as soon as a file changes within your music directory. Wherever it is. Youīre gonna configure that "somehow" (or do nothing and it will just not do anything). I donīt know specifics yet, since I didnīt even start doing that. But etr being a linux native utility for executing something on file changes will absolutely instantly react to anything that changes, while jriver seems to do that on a set schedule (so sometimes it may take a while) and then I usually go to the UI and hit "Run Auto Import Now". How about not needing to do that anymore?
bob:
--- Quote from: max096 on June 16, 2019, 12:13:59 pm ---Glad you like it. :)
Another thing that I wanted to try at some point is use http://eradman.com/entrproject/ to force an auto import as soon as a file changes within your music directory. Wherever it is. Youīre gonna configure that "somehow" (or do nothing and it will just not do anything). I donīt know specifics yet, since I didnīt even start doing that. But etr being a linux native utility for executing something on file changes will absolutely instantly react to anything that changes, while jriver seems to do that on a set schedule (so sometimes it may take a while) and then I usually go to the UI and hit "Run Auto Import Now". How about not needing to do that anymore?
--- End quote ---
MC uses inotify to update automatically when files are on a local filesystem.
inotify doesn't work for cifs so the fallback is to the timed auto-checking on cifs mounted filesystems. There may be other filesystems that don't work for inotify either.
Note that the auto-import can be triggered from JRemote (iOS, not sure about android).
Also since it's a MCWS command you could make a curl string to the localhost:52199 MC library server to do the same as well.
max096:
--- Quote ---MC uses inotify to update automatically when files are on a local filesystem.
inotify doesn't work for cifs so the fallback is to the timed auto-checking on cifs mounted filesystems. There may be other filesystems that don't work for inotify either.
Note that the auto-import can be triggered from JRemote (iOS, not sure about android).
Also since it's a MCWS command you could make a curl string to the localhost:52199 MC library server to do the same as well.
--- End quote ---
I don't use CIFS mount (on my main jriver instance anyways), since the mdadm raid6 formatted with etx4 is local to the system running the container. But I did volume mount it into the docker container. All I can say is that it does not work instantly for me now (and never did, since I was using docker) and it most likely will be consistently the same with any filesystem and mount option you use, since at the end of the day you are always gonna have to use docker volume mounts to map your music, or you don't have your music inside the container.
As I said I didn't even really start doing that. That's something that will appear in the dev-tags, whenever I find time to do so. But if it works out perfectly, I'll probably be putting that into the stable and latest tags to as an option to use.
I wasn't really planning on using curl, because it might be needing logins (and seems unnecessarily to do an http request) and there appear to be MC core commands available for triggering autoimport from the CLI.
Another option would be to forgo auto-import entirely and use the import methods instead. But that would also mean I'd have to do the delete and all those "fixing broken links" things when files change. Just run auto import seems a h3ll of a lot simpler. Although, you'd have 2 auto import triggers running at the same time then. Witch isn't perfect either. And ditching auto import would mean, you would not even have to configure JRiver at all to import your music. You just tell it /data (for example) is where my music is in the docker run command. Mount 10 directories under /data/music1 /data/music2 and it just kinda would go ahead and do that, without auto import ever being a thing. So that sounds nice, but I probably won't do that, because delegating the work to JRiver's autoimport seems just that much easier to do without introducing potential bugs.
---
OR... you update JRiver to work well with docker volume mounts and I don't try anything... ^^
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version