Closed JoergZ2 closed 2 years ago
yes, the local backend project is meant to run offline, it allows you to run without backend! it is supposed to run on same device
It removes the need for a backend, it doesnt provide a full backend alternative
So far its the only way to make a vanilla mycroft-core run fully offline with no pairing etc (native option exists in ovos-core)
I thought the readme was pretty clear about this, if it isnt maybe you can send a PR clarifying the readme?
while not directly replacing the mycroft selene functionality, you also have https://github.com/OpenVoiceOS/OVOS-Dashboard
its a sister project by @AIIX providing a web interface to manage your mycroft device, it doesnt have the full selene functionality, but it also has things selene doesn't
Thanks for the explanations! The dashboard I had already noticed and seen that it is an addition to the backend. And of course it makes more sense if it runs on the same device as Mycroft itself.
Hi, I've installed OVOS-local-backend as described in the README.md and make a new mycroft.conf for using local backend. OVOS-local-backend runs at a Ubuntu Desktop in a virtual Python environment. Picroft is logged in at the backend. There are a lot of lines showing the IP of Picroft. But when I call the address and port by a browser I get this:
I expected to see something similar to home.mycroft.ai.Am I missunderstandig the local backend project?