Support for Docker installation

[simoncn]

(12-10-2015 18:01)squarefrog Wrote:  Precisely. So for example, I would map /mnt/user/Music to /music in the VM. This would grant me read/write access to the audio files. I would then setup a folder separate from the disk pool for MinimServer config files. For example, /mnt/cache/appdata/minim, which would map to /config in the VM. This could host MinimServers database, along with any user settings.

In this case, there should be no problem with mapping the Linux MinimServer installation folder (a mixture of code and data) as /minim in the VM. This would mean you can install extensions such as MinimStreamer to this folder and they will survive a VM reboot.

Quote:In this case, the tagging application would be part of the VM. You may list any packages as dependencies, so you may want MinimServer, a tagging library, ffmpeg etc. All packages have access to the aforementioned /music and /config folders.

As the mounts are external to the VM, they survive reboots.

I could add files to my music library, over afp, smb, nfs whatever, and they appear instantly in the VM. Consider the mapping like a symlink or a mount in linux.

I am surprised that the tagging application would be part of the MinimServer VM. There is no need for the tagging application to communicate with MinimServer apart from via writing and reading shared files. It would be necessary to have ffmpeg as part of the same VM because MinimStreamer and ffmpeg need to communicate with other when doing transcoding.