-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web GUI #6
Comments
Also, the Spotify support link in the readme directs to the wrong GitHub page now :) |
Snapweb, interesting, didn't even know that existed. Could be a useful addition. Personally, I don't need it, but I am open for PRs! The link is fixed, thanks! |
Yeah I think it's supposed to be shipped with Snapcast but I'm guessing the docker install does something differently which means it doesn't automatically get bundled. |
Okay so it looks like Snapweb was only introduced in v0.21 and the version this uses is the default Debian one, which is (I believe) 0.15.0-1 https://packages.debian.org/buster/snapserver. Maybe it's worth adapting this to use the latest one from the Github repo? |
Hmm maybe not |
As far as I know Snapweb was introduced in 0.21.0: https://github.com/badaix/snapcast/releases/tag/v0.21.0 Is there a reason you are still on 0.19.x? |
Sorry I'm not sure where 0.19.x is coming from, in the makefile it appears the version is: |
Yes, I should've tagged 0.20 already. And yes, we can update 0.21. The problem is that arm builds are currently broken, which is actually an upstream issue at docker. I hope they fix it soon (or maybe they already fixed it even.) |
0.19 is the version packaged for debian bullseye.
This problem seems to have been around since last summer. Since I don't care about the arm build wouldn't it be possible to release the arm builds with a different version? E.g. use debian bullseye package for arm build (and tag it 0.19) and use the .deb file for the other build? |
Does this come with the web GUI (Snapweb)? I can't seem to be able to access it at :1780?
The resource '/' was not found.
The text was updated successfully, but these errors were encountered: