Hugo build caching
Is there a way to get build caching in Hugo sites? (cc @Dario , who seems to be the resident build cache maven)
DYes, I can impelement that 
Since I need to do it for docusaurus I might as well just do it for Hugo too
Since I need to do it for docusaurus I might as well just do it for Hugo too
Dbut I have zero Hugo knowledge I'd like to get someone from the Hugo team ideally confirm what directories need to be cached
Dare you by any chance a Hugo maintainer and/or can you connect me with one? 
TOh fantastic! I am not a maintainer but I can reach out to one to let them know you're interested in working on this.
Tthe cacheDir is configurable. I think that's all you'd need to support: https://gohugo.io/getting-started/configuration/#configure-cachedir
TThank you very much for looking into this!
JBy default, we create a "hugo_cache" directory in the user cache directory as determined by https://pkg.go.dev/os#UserCacheDir. For example, by default, on Linux my cache directory is /home/jmooring/.cache/hugo_cache. Although users can override the location of the cache directory, that's not something you need to worry about... it would be a self inflicted wound in this context.
JBy default, this directory contains cached modules and remote data. Users can configure a site to cache images in this location as well. This is a big win for sites that perform image processing. See https://gohugo.io/getting-started/configuration/#configure-file-caches.
JGitHub
The world’s fastest framework for building websites. - gohugoio/hugo
DI'm sorry I completely missed the replies is thread! 
(I feel like discord's notifications aren't always the most helpful! )
(I feel like discord's notifications aren't always the most helpful! )Dour build cache implementation is unfortunately a bit limited and it doesn't really implements any integration with possible framework customization, so it always only checks the default directory (/directories)
fortunately it seems like you're ok with that
fortunately it seems like you're ok with that
Dhttps://github.com/gohugoio/hugo/blob/7f3061723e3df064515fc57c183b06ed16f26b75/helpers/path.go#L374
regarding the netlify=true... I need to check I am not 100% sure if that applies to the v2 build image
regarding the netlify=true... I need to check I am not 100% sure if that applies to the v2 build image
GitHub
The world’s fastest framework for building websites. - gohugoio/hugo
DI'll have to check about the dir location... as I said it's just static/hardcoded on our end, so I am not 100% sure if
if it's not this could require a bit of refactoring on our end (with some potential pushbacks).
Or maybe you'd be willing to add an additional ad-hoc
UserCacheDir will always be the same for every single build...if it's not this could require a bit of refactoring on our end (with some potential pushbacks).
Or maybe you'd be willing to add an additional ad-hoc
ifGitHub
The world’s fastest framework for building websites. - gohugoio/hugo
Dsorry before I forget, thanks for connecting us! 
0Would that cover resized images as well? (I'm not committing
resources/_gen to the repo)DI did start look into it but there's a non trivial issue with enabling build caching with Hugo
Dthe fact that hugo is not node/npm based and all our build caching code is npm-based, so to support hugo we'd have to add a separate build cache implementation from scratch for it 
Dnot impossible but it'd take some effort for sure (and I don't really have lots of time at the moment, I can make a note of this and get back to it as soon as I can if it can help , or I can ping the team which own that infrastructure but I can't imagine this getting prioritized unfortunately )
, or I can ping the team which own that infrastructure but I can't imagine this getting prioritized unfortunately )TAh ok, understood! Thanks for looking into it anyway.
TI was hoping there'd be at least some appetite to make this happen, since y'all appear to be using Hugo and Pages for the your own developer docs: https://blog.cloudflare.com/new-dev-docs/
The Cloudflare Blog
In this blog post, we’ll cover the history of Cloudflare’s developer docs, why we made this recent transition, and why we continue to dogfood Cloudflare’s products as we develop applications internally.
