Closed trailfog closed 1 year ago
I've gave up on this sinking ship and moved to unmanic. It works great, download artists/albums/songs/playlist straight from deemix and unmanic transcodes from flac to MP3 in the same folder. No faffing around it just works.
@youegraillot can we get this merged, pretty please :D
Hi, If I install the latest lidarr-on-steroids does it include the deemix bug patch? Thank you
Hey, sorry for not being responsive on this image anymore I don't have much time to maintain this project on a regular basis :( I'll merge !
@trailfog PR broke the build from github action I tried to fix it for a bit but could not figure out why it builds locally but not on github action
@youegraillot I'll have a look at it. It seems to me, that the arm version of the build is failing. The amd version builds just fine in the pipeline.
Btw, you can use something like act to run & debug your GitHub actions locally ;)
@youegraillot I have fixed the issue on the arm64 build.
I'm not going to open another pull request for this, you can copy & paste the change I made here: https://github.com/trailfog/lidarr-on-steroids/commit/fb7682006f9f590d56589f2cf289a70da5e7b111
For some reason, the alpine image requires some additional dependencies when run on an arm processor. I hope this will fix the issue, it does locally for me at least.
Build on RaspberryPi fails with exit code 1 on "run yarn dist-server"
`#7 109.2 asset app.js 1.66 MiB [emitted] [minimized] (name: main) 1 related asset
process "/bin/sh -c yarn dist-server" did not complete successfully: exit code: 1`
@noworthwhile build is successful on github action with arm64 please use the dockerhub image or open a new ticket with more specific info on your hardware closing
This is a simple and superficial bug patch for deemix, as it does not seem to be getting any updates any more.
The issue is described in #63, where when fetching the
newRelease
endpoint from the deemix-gui server, the entire server will crash due to some missing data not being sent to deezer.To patch this issue, the
bockiii/deemix-docker
image has been removed and deemix gets built directly from source in this Dockerfile.Once the deemix-gui repo has patched the bug, the
sed
command can safely be removed.