Asset UPnP { Help Index > Linux / ARM (Raspberry PI) Specifics }
Installing Asset
Installation is done through the Linux terminal command-line. For headless devices, install a ssh client, such as Putty on Windows then connect to the device to access command-shell.
Determine which version of Asset is compatible with your system, type into the shell:
Possible outputs:
i686 : need x86 32-bit
x86_64 : need x86 64-bit (x64)
armv7, aarch64 : need ARM (Raspberry Pi)
Create and enter a folder in which Asset will be downloaded and extracted:
mkdir ~/Asset-Install
cd ~/Asset-Install
You will want to download the registered or trial version to a USB stick and mount it (out of scope of this help, given the number of different OS, a google search is your friend here) on the device and copy the install file to ~/Asset-Install:
cp /media/username/* ~/Asset-Install
Where /media/username/ is the mounted location, it might be in /mnt/
To extract the install type:
tar xzf ~/Asset-Install/*.tgz
cd Asset-*
./INSTALL.sh
Further details will be shown on screen. When finished, Asset will be running and configured to automatically start on system startup.
When done, the Asset-Install folder is no longer needed and can be deleted:
Upgrading Asset
Follow the exact instructions above, the newer install when ./INSTALL.sh is run, will upgrade the existing.
Configuring Asset
To access Asset configuration, type the following URL into your web browser:
Replacing x.x.x.x with the IP address of the Linux/ARM machine. Typing
ifconfig on the device ssh, can reveal the IP address.
Uninstalling Asset
Use the included UNINSTALL.sh script. If you've deleted the Asset-Install folder, you can follow the install procedure above with any version of Asset including the trial, and run UNINSTALL.sh instead of INSTALL.sh
Configuration Files
Asset's profile data, by default stored in ~/.dBpoweramp
The data can grow pretty huge as it stores a cache of all your album covers. If your home folder is space-restricted, which happens on some embedded systems or NAS boxes, you can have have it stored in another location.
Prior to running Asset, set an environment var _APPDATA_OVERRIDE pointing it to a folder where you want your Asset data stored. For example: export _APPDATA_OVERRIDE=/path/to/asset/data
If asset starts on the crontab then, edit it:
And the line which starts Asset change to @reboot _APPDATA_OVERRIDE=/path/to/asset/data /usr/bin/asset/Asset-RXXXX-Linux-x64-registered/bin/AssetUPnP
Where /usr/bin/asset/Asset-RXXXX-Linux-x64-registered/bin/AssetUPnP would be left, and could be different on your Linux.