Backgound image not found

[hklausing]

Question: what should I do to load a local background image without touching the git repository?

• homepage version 1.12.3
• installation type: from source via git repository
• installation process: own Ansible role
• ...: location of git clone path

I installed homepage to an LXC container building from source, supported by Ansible. Now I want to load a background image, that is stored in .../config/images/background.jpg.
With this I tried to use a solution like image: ../../config/images/background.jpg which doesn't work. Lastly I found a workaround to set a link from ...config/images/ to .../public/images/. Than I could use image: images/background.jpg to load the image.
This disadvantage of this solution is, it will break Ansible execution.
I guess it would be helpful to add the line /public/images to .gitignore

Regards, Heiko

[shamoon]

../../config/images/background.jpg is not expected to work. Homepage only supports background images that are either:

• a full URL, or
• a path served from the app’s public directory, e.g. /images/background.jpg

So in a source install, the supported local option is to place the file under /public/images/ and reference it as background: /images/background.jpg

Allowing paths outside the public root would effectively be filesystem traversal, which we intentionally do not do.

[hklausing]

I did exactly that, I made the directory public/images and stored the background.jpg. The background image will be found and displayed, no problem.

If I check the status of the homepage repository, untracked files will be reported by git in public/images. Similar issue if Ansible checks the git repository status. I don't think this a satisfactory solution.

To avoid this git report, the path public/images should be ignored by adding the info to .gitignore. This change allows users to get a similar solution as for Docker.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.