
- #Plexamp nas install
- #Plexamp nas archive
- #Plexamp nas code
The app can be moved once you choose something to play. General Questions What platforms support Plexamp? We do not currently offer any official support for Plexamp and it’s offered “as-is”. Note: Plexamp is an experimental app offered as part of Plex Labs. It’s designed to allow quick and easy access to your music content for playback and even includes fun features such as visualizers for the music.
#Plexamp nas code
Connect to the Plexamp UI from a browser at Note: there is more work to do to manage Plexamp code updates, but our friend is working on it.Plexamp 1.x is a small, dedicated music player for Plex. Check that Plexamp container is working:ĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĠc48fe3c8837 /zonywhoop/plexamp-headless-docker:arm-461 "/usr/bin/entry.sh n…" 3 hours ago Up 29 minutes plexamp. Go back to the first terminal session and close the container by keying Ctrl + C. Note III: for a reason I ignore, I had to run the step above twice, first attempt failed Note II: this step is only required for the first time run Note I: The DEVICE Error message can be ignored Bedroom, Kitchen): ĭEVICE: Error loading cloud players from HTTP status 403 # docker exec -it plexamp node js/index.js
> follow the instructions and enter the claim token Run: docker exec -it plexamp node js/index.js.From another terminal session, ssh to HiFiBerry host.> at this stage Plexamp is waiting for the claim token input
Note: arm-461 is for Plexamp version 4.6.1 arm 32 bits Image: /zonywhoop/plexamp-headless-docker: arm-461
Create /data/docker/plexamp/docker-compose.yaml. > This is to match local owner ID with docker Plexamp ID (if I understood well) Change ownership: chown 1001:100 /data/docker/plexamp. Some may be incomplete or incorrect, please shout in such case! Whenever a new Plexamp version is available, downloading and extracting it in place of the running one are the only required steps.Ĭhristian Brückner, here are the notes I took. Terminal: To run Plexamp as a service, a few other steps have to be performed. Browser: Access Plexamp UI at to fine tune its configuration and play some music. Terminal: Enter the token, Plexamp should now be running, using the default sound card. Browser: get the claim token at (you'll need to sign in Plex if not done already). At this stage you have to provide a "claim token" used to claim your Plex Media Server associated to your Plex account #Plexamp nas archive
Terminal: Untar Plexamp archive in the root home directory. Terminal: Download Plexamp archive file in the root home directory. #Plexamp nas install
Terminal: Install required version of Node.Js (12 or 16 from Plexamp 4.6.0 (still in beta)).Terminal: Install Nove Version Manager (NVM).Terminal: Open/ssh a terminal session against HFBOS.Without going into much details for now, here are the steps I used to install it in HFBOS (prerequisite: HFBOS installed and tested, ssh enabled in HFBOS, Valid Plex account + Plex Pass (TBC), Web browser): Unfortunately I don't think a docker can easily do the job as each Plexamp instance is linked to a Plex account that is configured during the initial installation, unless there is a "docker" way to manage this scenario?Īlso, a docker layer may have an impact on the performance in RPI without enough memory/cpu.