Thanks! Well I don’t believe it’s possible according to the filebrowser documentation…
Best I could do is to modify the root folder you see when opening the filebrowser app… Would that help you? For example, to see only the mount folder when starting the app (but then you wouldn’t be able to see the folders below)
Hello, i see you are asking for the homebridge addon. We’ve worked on that and it works like a charm, only issue we need to fix is the ingress. I have currently a thread to see what should be done to get this running. If ingress works, the HomeBridge addon is ready to install (Currently only works on access by direct link.).
@alexbelgium thanks for the filebrowser!!! Works very well, exactly what i needed.
Btw maybe you know how to fix it, since it looks like your addon uses ingress as well.
When we add ingress to an addon it resolved the correct url, except for static js files. The browser tries to get them from the home assistant root directory while the js files are running in the container.
So lets say for example i have a addon, and with ingress it loads /api/hassio_ingress/xxxxxxxxxxxx
But the addon/container serves some static files like js, when i open the addon it doesnt show anything and in the dev console i see that the browser tries to get the static files just from / instead of /api/hassio_ingress/xxxxxxxx
Hi, saw it! Great that you have developed this addon I’ll post in the other thread to see if I can help. There could be a solution if js files are not dynamically generated
That’s very strange, it works fine on my system. You’re using HA in docker, does it has the local build capability (this addon is not based on an image due to a bug in HA supervisor). Did it install correctly? Is that all you have in terms of log? What is your system arch? Thanks
Seeing this error, the most probable issue is within the local HA build script, as this file is added through the dockerfile…
Just saw your message. Did you find your solution? I encountered that on some addons - for one the solution I found was to use sed to create relative instead of absolute links, for the other I managed through it by setting the “root” directive in nginx, for the third one it seems a solution is to redirect specifically those files through the nginx.conf. Honestly, it’s always complex
Hi, those are the addon options that you can find in the “configuration” tab of the addon.
To mount a samba disk, just fill the networksdisk, cifspassword and cifsusername tabs. If you can’t see them in the config, you need to click on something like “show unused configuration options”.
In the addon log everything will be described : if the mount was correctly done, and where it is put. It can then be accessed by browsing to /mnt/SHARENAME. Due to the way docker works, this mount is only accessible from within the addon.