Lastmod from GitInfo shows correctly with hugo serve locally, but is overwritten on Cloudflare pages deploy

support
1

WIth hugo serve, the last modified dates of pages shows up right.

With cloudflare deploys, every single page on the site says it was last modified on the date of the most recent deploy.

This is a similar issue - discourse.gohugo dot io/t/page-lastmod-always-show-todays-date-in-deployed-site-not-the-last-mod-date/33576

Semi related but not my issue - github dot com/gohugoio/hugoDocs/issues/1624, gohugo dot io/getting-started/configuration/#configure-dates [had to remove urls, new users are limited to 2 per post]

As is this - discourse.gohugo dot io/t/incorrect-lastmod-git-date-when-deploying-using-github-pages/40900/2

Also related - github dot com/gohugoio/hugo/issues/9810#issuecomment-1107519804 from @jmooring

I believe the fix would be to be able to run this on cloudflare pages.

git config --global core.quotepath false

Things tried:

  • I updated hugo from 114.1 to 118.2 locally

  • I updated the hugo version requirement on cloudflare from 114.1 to 118.2

  • I ran “git config --global core.quotepath false” locally and then updated my site and deployed, no success

  • I changed the cloudflare build command from “hugo” to “git config core.quotepath false && hugo”, it runs the command in the build log and no error, but resulting deploy has same issue (and I’m visiting directly from the deployed url rather than site url, to prevent cache issues)

  • I changed the cloudflare build command from “hugo” to “git config --global core.quotepath false && hugo”, it runs the command in the build log and no error, but resulting deploy has same issue

  • I changed cloudflare build command from “hugo” to “git config --global user.email “email@gmail.com” && git config --global user.name “Name” && git config --global core.quotepath false && touch blank.md && git add . && git commit -m “add” && hugo”, no errors, but didn’t fix the issue

What would you suggest @jmooring ?

2

I suspect that Cloudflare performs a shallow clone.

Check out this article by @bwintx. For Cloudflare pages he recommends:

git fetch --unshallow && hugo --whatever --flags --you --need
3 Likes
3

That solved it - thank you @jmooring and @bwintx !

And note for anyone coming from google in the future, I changed the cloudflare pages build command from

hugo

to

git fetch --unshallow && hugo

Then I modified a file, committed, deployed, and the updated deploy worked as expected and fixed the issue

1 Like
4

I suspect that Cloudflare performs a shallow clone.

Yes, that’s correct. That recommended build command came from the Cloudflare Pages team’s suggestion on a Discord thread after a confirmation that CFP does a shallow clone.

1 Like
5

@bwintx just updated the Hugo documentation to include Git fetch depth details for various hosting providers (Cloudflare Pages, GitHub Pages, GitLab Pages, Netlify, etc.).

See https://gohugo.io/variables/git/#hosting-considerations.

Thanks Bryce.

3 Likes
6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.