Closed wiebereu closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
That is the expected webui for beets.
Yes but what can i do with an empty webui? You can't click on anything on this page How can i start with a scan of my library if there is nothing to see in the webui?
Beets is primarily a CLI tool, I would suggest reading the documentation.
Beets is primarily a CLI tool, I would suggest reading the documentation.
I don't want to be rude but i can say the same to you cause the version i installed says it worked with a webui. So i have read the documentation.
Here is the link about Beets. https://beets.io/
Why do i need a webui if i have to do everything from the command line? It doesn't make sense
The web plugin is a very basic alternative interface to beets that supplements the CLI. It can’t do much right now, and the interface is a little clunky, but you can use it to query and browse your music and—in browsers that support HTML5 Audio—you can even play music.
We also state here: https://github.com/linuxserver/docker-beets#application-setup how to use the container.
As Spad has linked the webui plugin, it's just used for querying the beets database and basic playback.
The web plugin is a very basic alternative interface to beets that supplements the CLI. It can’t do much right now, and the interface is a little clunky, but you can use it to query and browse your music and—in browsers that support HTML5 Audio—you can even play music.
Thank you for enlighten me. I had a different picture of Beets. Now that i understand that the Webui is just some kind of window dressing i will remove the container from my Docker platform.
Is there an existing issue for this?
Current Behavior
Is the second time that i installed the Beets container but after installation i see no information on the webpage. The only thing i see is Beets in the left upper corner of the screen but no further infomation.
Take a look and you will see. The logs tells me nothing Beets-log.txt
Expected Behavior
A GUI which i use.
Steps To Reproduce
No steps at the moment
Environment
CPU architecture
x86-64
Docker creation
Container logs