Topics

• Overview
  • What is RPMS? And what is it not?
  • System Requirements
  • Installation
• Tech
  • Troubleshooting
  • Folder Mapping
  • Update RPMS
  • Development
  • Useful Commands
• Functions
  • Transcoder
  • Flac Health
  • Backup | Disaster Recovery

Web

Home-page

You can see here some specifics of the used hard- and software, like the Pi-model, Operating System-version, uptime, etc. A note about Power Supply: if it states Provided current is not sufficient, you need a bigger power supply; best used are the official power supplies for the specific Raspberry Pi-model.

It also contains info about updates of the RPMS-software: you can update your system by clicking on the Update-button, whenever a new version of RPMS is released.

See for details Update RPMS

Resources-page

This page show info about memory (or swap) and CPU usage & temperature. It also shows the connection-status of the disks, as well as the statistics of each disk. Obviously, when an indicator is coloured red, it means trouble!

Music-page

On this page you can see information about your (LMS) music-system such as connected players and statistics about your collection. If a player supports configuration by a web-page, a link is shown so you can jump right to it.

The collection is exported (automatically), in 3 different text-files which are placed in the root of your music-folder: collection-by-folder.txt, collection-by-tag.txt and collection-by-genre.txt; each gives you a different view of your collection. These can be used when sharing music, to give an quick overview of your collection. Forcing an export can be done from here. You can also view them directly from the interface through the links: Collection by Folder | By Tag | By Genre.

This page also contains info about Flac Health: the locally stored (flac-)files can contain errors which can prevent playing or transcoding. These errors can be detected and repaired. A nightly scan for flac-health is fired automatically, but you can also force a scan; the result of the scan is shown on this page.

See for details Flac Health

Transcoder-page

On this page, you can see the status and control-options for the RPMS-transcoder.

Within RPMS, there is a transcoder built in, for transcoding your lossless music files (flac) into lossy ones (ogg or mp3). B/c transcoded files occupy less space, you can easily transfer them to your phone of laptop for listening to your complete music-collection when you are not at home or even offline.

See for details Transcoder

Backup-page

Backups are very important, your local music-collection deserves it. On this page you can see the status and progress of the builtin backup of RPMS; these nightly backups perform automatically.

The preferred configuration for RPMS is to have two identical disks attached, one for data and one for backup. Once RPMS recognizes the backup-disk, it automagically creates a mirror of the data-disk to the backup-disk. This is called a server-based backup. When disaster strikes, when the data-disk crashes, the backup-disk can be swapped for the data-disk, providing minimal data-loss.

Besides the server-based backup, you can of course do a regular (remote) backup, on an external harddisk; RPMS provides multiple tools and protocols in doing so. It is best to have multiple backups, b/c general wisdom says one backup is no backup!

See for details Backup

System-page

On this page, you can see some technical stuff. You can control the server itself (halt or reboot). You can see the status of docker-containers (for LMS & SyncThing) as well as controlling them (kill, update, start); note that these containers are automatically updated at night, providing you with always the latest-and-greatest versions of LMS and SyncThing!

You can also see the status of the ports which are provided by RPMS. Of course, you can always see the port-status from your client:

watch nmap rpms