I have all my javascript (and other) web packages managed by bower. I then set up symbolic links (in linux) from the various js files I will use within those packages to a js directory within the static folder. The idea being is if I do a bower update then hugo will use in the latest js files when it builds. I am trying to avoid putting the entire bower_components (packages) folder within the static folder because that just puts a lot of unsued files into the website itself.
Can anyone suggest an alternative workable workflow so one simple bower update command and hugo uses the latest js files?
Guess I donât understand symbolic links well enough to understand why hugo would complain about this. I use them all the time to âfoolâ other programs. So is it possible that Hugo can support symbolic links in a future release? Is this really because it is an OS specific issue? I mean one would have to build for example a linux specific version?
For any reading who may be using bower I found this. It does what I need (i.e. puts only the required files of a package where I want them i.e. /static).
filepath.Walk, the Go function doing the heavy lifting, doesnât follow symbolic links, hence the error. But I believe that the âroot folderâ as a symbolic link should work, and that is what you see â and the error message is wrong. (could you create an issue at GitHub?)
So /content_src as a symbolic link seems to be fine, but /content/blog or whatever would fail. Not sure.
Note that this only supports symbolic links for the top-level directory of these different content paths â so /static can be a symbolic link, but not /static/js âŚ