You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While customizing the favicon in settings, locally stored .ico files in the /app/public/images folder will not apply. However, when referencing the same .ico file from the web source, it applies just fine. First, I thought it could be permissions or storage location. However, background images sourced from the same /app/public/images folder with the exact same permissions apply just fine. I have also browsed locally in the container to confirm that the file is present within the folder specified to check for mounting issues within docker.
I can apply this same exact .ico file fine in many other applications I have, but I thought I would try another file to see if it's somehow "non standard". I first used the url from the documentation here. Using the URL works. When downloading that same source .ico locally, with correct permissions, it will not apply.
I believe I have found the solution, and it relates to closed issue #534 (as I was also experiencing that). I had my image folder directly mounted into the parent (app/public). After reading the solution to that, I changed my mount point to be /app/public/images and just supplying the files within, and now the favicon.ico seems to be applying correctly.
Please confirm on your side, but I believe this can be closed.
Ah yea I meant to circle back on this. I could swear I didn’t do that when I setup a test install for this but anyway, I’m sure if it’s solved for you that’s all it was. Thanks
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.
Description
While customizing the favicon in settings, locally stored .ico files in the /app/public/images folder will not apply. However, when referencing the same .ico file from the web source, it applies just fine. First, I thought it could be permissions or storage location. However, background images sourced from the same /app/public/images folder with the exact same permissions apply just fine. I have also browsed locally in the container to confirm that the file is present within the folder specified to check for mounting issues within docker.
I can apply this same exact .ico file fine in many other applications I have, but I thought I would try another file to see if it's somehow "non standard". I first used the url from the documentation here. Using the URL works. When downloading that same source .ico locally, with correct permissions, it will not apply.
For reference. the ico file I am trying to use is located here: https://iconarchive.com/download/i103430/paomedia/small-n-flat/house.ico
Here is a screenshot from when it works when a url is provided in settings.yaml, essentially proving that the file can work
Steps to reproduce
then
homepage version
v0.5.3
Installation method
Docker
Configuration
Container Logs
No response
Browser Logs
No response
Other
Until issue #534 is resolved, none of this matters anyway. Any customization of the settings.yaml leads to i18n key names being used for labels.
The text was updated successfully, but these errors were encountered: