joshmock
09/21/2025, 5:49 PM/usr/share/wallpapers. So I put them in my repo with a files module and committed them using Git LFS to avoid directly committing large binaries.
However, when I run my build, Blue Build just writes the symbolic link for each large file into the wallpapers directory instead of the actual file.
I tried setting up LFS in my image using a script module , and have considered writing a custom module to handle LFS. But it seems that, because module seem to run within the context of a Containerfile, it does not recognize that it is even in a Git repo.
Do you have any suggestions for how to go about this? Or should I just put my wallpaper files in a bucket and download them at build time?Answer Overflow
09/21/2025, 5:49 PMgmpinder
09/21/2025, 6:01 PMxyny
09/21/2025, 7:40 PMlfs: true to be set for lfs files to be fetchedxyny
09/21/2025, 7:40 PMxyny
09/21/2025, 7:41 PMxyny
09/21/2025, 7:41 PMgmpinder
09/21/2025, 7:46 PMjoshmock
09/21/2025, 11:23 PMjoshmock
09/21/2025, 11:26 PMbluebuild source to see if it needed to happen there, but the GitHub action makes way more sense.