-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add troubleshooting for WSL and hugo server
#1799
Comments
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 9, 2024
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 9, 2024
Merged
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 11, 2024
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 13, 2024
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 13, 2024
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 15, 2024
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 15, 2024
jmooring
added a commit
to jmooring/hugo-docs
that referenced
this issue
Feb 17, 2024
bep
pushed a commit
that referenced
this issue
Feb 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I recently came across the same issue as describe in Hugo issue #9809. This issue is that when using Hugo from WSL, and your files are on Windows, Hugo cannot detect file changes the same way as if both parts are on the the same system (both on WSL or both on Windows)
The resolution for this was to use the
--poll
flag to better enable Hugo's watcher to catch changes.This was not obvious to me, and took me quite some time to find, as it's only mentioned in a github issue. I believe this should at least be mentioned in the troubleshooting docs, so as to make it easier to find this information.
I'd submit it as PR, but I don't feel that I know enough about the technical details, or correct verbiage to do so.
The text was updated successfully, but these errors were encountered: