inland swallow
Hi, after having to build all of my NAS new and reordering my stuff, i noticed that Music Assistant now supports "Audiobookshelf", which is a self-hosted Audiobook Provider (https://github.com/advplyr/audiobookshelf).
Because the features sounded promising, i started looking if there is an addon for Home Assistant. Unfortunately, there are no real existing addons for this, but i found a github account used to making an addon from an older version (2.9); so i forked it (https://github.com/kuchenundkakao/hass-audiobookshelf) and started to adapt the addon to use the newer 2.24 Version of Audiobookshelf and got it to run on my home assistant (Success!).
But now i am stuck and my docker-/home-assistant-fu isn't good enough to overcome it. Maybe somebody here knows better how to do the dockerings and configurations?
- How can this be configured so that my Music Assistant instance can connect to the Audiobookshelf instance without using the "external" port (http://homeassistant.local:13378/) ? I thought there was some kind of "internal" communication between docker images like localhost or something?
- How do i have to configure everything so that the database is saved on the home assistant? Right now i'm scared that once i update the audiobookshelf the database will get deleted
- (this is probably more for the audiobookshelf community, but better ask than be sorry 😉 ) Can i somehow get Audiobookshelf to respond correctly to ingress and external calls? in the index.js (that gets started when the addon starts) there is an environmental variable that defines the path for the javascripts and stuff. once it works external, it won't find js files in the ingress window...
However, if somebody has an idea how any of this can be managed (and if) i would be thankful for answers.
Regards, Kuchen
copper shoal