Community Apps

Locate your drives and assign them to a graphical tray map to get full overview of installed hard drives in your system.

Locate your drives and assign them to a graphical tray map to get full overview of installed hard drives in your system. NB! This is the developer edition of the plugin, use with CAUTION and OWN RISK!

Mopidy is an extensible music server written in Python. Mopidy plays music from local disk, Spotify, SoundCloud, Google Play Music, and more. You edit the playlist from any phone, tablet, or computer using a range of MPD and web clients. This is Mopidy for unraid with support for snapcast and icecast It is based on whhoesj/mopidy with additin of TuneIn and Youtube and Iris Web Interface. set up the docker set up the network to br0 with an ip set up volume mount to /mnt/user/appdata/mopidy/mopidy.conf >> /mopidy.conf set up volume mount for tmp/snapfifo if you use snapcast /mnt/user/appdata/mopidy/tmp/ >> /tmp set up volume mount for your local media generate the mopidy.conf file Doc here https://docs.mopidy.com/en/latest/config/ example here https://github.com/wernight/docker-mopidy/blob/master/README.md authentication for soundcloud and spotify https://www.mopidy.com/authenticate/ use my docker icecast or snapcast for music streaming: for audio you need a special config for snapcast you have to generate the audio output in a pipe file /tmp/snapfifo this is mounted in both docker container output = audioresample ! audio/x-raw,rate=48000,channels=2,format=S16LE ! audioconvert ! wavenc ! filesink location=/tmp/snapfifo icecast output = lamemp3enc ! shout2send async=false mount=mopidy ip=X.X.X.X port=8000 password=XXXXX

Mopidy is an extensible music server written in Python. Mopidy plays music from local disk, Spotify, SoundCloud, Google Play Music, and more. You edit the playlist from any phone, tablet, or computer using a range of MPD and web clients. This is Mopidy3 for unraid with support for snapcast and icecast. set up the docker set up the network to br0 with an ip set up volume mount to /mnt/user/appdata/mopidy/ >> /config/ set up volume mount for tmp/snapfifo if you use snapcast /mnt/user/appdata/mopidy/tmp/ >> /tmp set up volume mount for your local media generate the mopidy.conf file Doc here https://docs.mopidy.com/en/latest/config/ example here https://github.com/maschhoff/docker/blob/master/mopidy/mopidy.conf authentication for soundcloud and spotify https://www.mopidy.com/authenticate/ *authenticate spotify https://developer.spotify.com/documentation/web-api/quick-start/ use my docker icecast or snapcast for music streaming: for audio you need a special config for snapcast you have to generate the audio output in a pipe file /tmp/snapfifo this is mounted in both docker container output = audioresample ! audio/x-raw,rate=48000,channels=2,format=S16LE ! audioconvert ! wavenc ! filesink location=/tmp/snapfifo icecast output = lamemp3enc ! shout2send async=false mount=mopidy ip=X.X.X.X port=8000 password=XXXXX

This container will install a fully updated Windows 98SE virtual machine (VM) into the VMs tab of your server. The container variables that you select will apply to the VM, and for most users, the default settings are sufficient and do not require modification. However, if you need to change the locations within the container, here is a brief explanation of what each location does. The "VM Share on Server" setting should be configured to reflect the location of your VM share. By default, the VM share on Unraid is located at /mnt/user/domains. The "Name to call VM" setting is straightforward. It allows you to choose a custom name for your vm. The default name is "Windows 98" but you have the option to change it to any desired name. Windows 98 type WIN98-KernelEX This allows Win98 to run some Win2000 and XP software WIN98-Normal Normal vanilla install After configuring the container variables as described above, the container will take care of the rest. It will create an XML file for the Win 98 virtual machine based on your selections and install the VM directly onto the server. Once the container has been run, you can go to the VMs tab and locate the installed VM. It is important to note that the container does not need to be kept running after installation. It is simply a tool for installation purposes and does not have a web user interface (UI). To monitor the container's progress, you can view the container log. ** This container cant translate the location of an unassigned disk across to the vm template. So all locations choosen must be on the array or pool device.