Skip to content
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

Jekyll serve --watch not recognizing and updating changes #2926

Closed
javirivera opened this issue Sep 15, 2014 · 23 comments
Closed

Jekyll serve --watch not recognizing and updating changes #2926

javirivera opened this issue Sep 15, 2014 · 23 comments

Comments

@javirivera
Copy link

@javirivera javirivera commented Sep 15, 2014

I recently set up my github pages for my new website and installed bundler gem through the terminal and the git-hub pages gem. Since then the jekyll serve --watch has not been updating when I make a change to my code.

Thanks in advence for any help.

@parkr
Copy link
Member

@parkr parkr commented Sep 15, 2014

Are you on Windows? Try --force_polling when you run jekyll serve --watch. What version of Jekyll and Listen are you using?

@parkr parkr added the support label Sep 15, 2014
@javirivera
Copy link
Author

@javirivera javirivera commented Sep 15, 2014

I'm in OSX . Using jekyll 2.4.0 . And from a listen -v I could read that I have Listen 2.7.9 . How do I --force_poll?

@kleinfreund
Copy link
Contributor

@kleinfreund kleinfreund commented Sep 15, 2014

jekyll serve --force_polling

You don't need --watch, because watching is the default for serve since 2.4.0.

@javirivera
Copy link
Author

@javirivera javirivera commented Sep 15, 2014

Ah, alright. It Regenerates with --force_polling. So from now on I should run the jekyll serve with that instead of --watch?

Thanks for your prompt answers!

@parkr
Copy link
Member

@parkr parkr commented Sep 15, 2014

So from now on I should run the jekyll serve with that instead of --watch?

Only if you're using Jekyll 2.4 or later.

@parkr
Copy link
Member

@parkr parkr commented Sep 15, 2014

If you're on Mac OS X, it should all work.

@kleinfreund
Copy link
Contributor

@kleinfreund kleinfreund commented Sep 15, 2014

So from now on I should run the jekyll serve with that instead of --watch?

What is --force_polling for? Is this just some way to fix issues like this?

@parkr
Copy link
Member

@parkr parkr commented Sep 15, 2014

What is --force_polling for?

Force polling forces liquid to use the polling architecture rather than inotify. It's more CPU intensive than the latter.

@alfredxing
Copy link
Member

@alfredxing alfredxing commented Sep 15, 2014

Have you tried not using the github-pages gem? Try it with Jekyll 2.4.0 or HEAD and not through bundle.

@javirivera
Copy link
Author

@javirivera javirivera commented Sep 15, 2014

@alfredxing I have uninstalled the github-pages gem. Tried it with just jekyll serve --watch; with and without bundle, and it just doesnt regen.

I'm not sure I might've messed up something while I installed the bundler gems or set up my repo on github.
On a pleasant note: --force_polling has been working well for now, Thanks again.

@XhmikosR
Copy link
Contributor

@XhmikosR XhmikosR commented Oct 8, 2014

@parkr: is there an issue to track the force-polling workaround for Windows? I'm hitting this issue and force-polling fixes it; it happens when the output directory already exists before calling jekyll serve.

@parkr
Copy link
Member

@parkr parkr commented Nov 29, 2014

Check your exclude config variable as well.

@parkr parkr closed this Nov 29, 2014
@robotdana
Copy link

@robotdana robotdana commented Feb 15, 2015

For future people coming across this.

this issue for me was related (I suspect) to this: thibaudgg/rb-fsevent#10

The case of a directory in the "Auto-regeneration: enabled for ..." line was different than it was in the finder.

Renaming the incorrect dir, then renaming back, fixed it. (other possible solutions are listed here: http://feedback.livereload.com/knowledgebase/articles/86239)

@LukeMcGurdy
Copy link

@LukeMcGurdy LukeMcGurdy commented Jul 20, 2016

I was having the same issue (git-hub pages gem on Win10) but jekyll --incremental seemed to do the trick

@alexshyba
Copy link

@alexshyba alexshyba commented Nov 14, 2016

This article helped me with similar issue on Win10 with Jekyll 3.3.0. See "May not work" part: https://labs.sverrirs.com/jekyll//5-wdm-gem.html

@iddan
Copy link

@iddan iddan commented Mar 24, 2017

Updates do not work for me at all.
macOS 10.12.3
ruby 2.4.1
jekyll 3.4.3
using the github-pages gem and bundler

@wraybowling
Copy link

@wraybowling wraybowling commented May 17, 2017

Auto-regeneration isn't working for me with

  • macOS 10.12.3
  • ruby 2.3.3
  • jekyll 3.4.3
    not using the github-pages gem, and it doesn't seem to matter if I execute jekyll with bundler or not.
@ashmaroli
Copy link
Member

@ashmaroli ashmaroli commented May 17, 2017

@wraybowling jekyll-admin v0.4.1 has the auto-regeneration disabled internally. Disable the plugin if you're using that particular version..

@wraybowling
Copy link

@wraybowling wraybowling commented May 17, 2017

@ashmaroli WOW. Gosh I hope you didn't spend too long figuring that out, but that did the trick. Thank you!

@ashmaroli
Copy link
Member

@ashmaroli ashmaroli commented May 17, 2017

I hope you didn't spend too long figuring that out

😃 I had encountered a similar issue on StackOverflow. So my first guess was on the plugin.. 😉

@rsmithlal
Copy link

@rsmithlal rsmithlal commented Sep 7, 2018

the --force_polling option worked great for me using Docker on Windows

@mikekok
Copy link

@mikekok mikekok commented Dec 10, 2018

I'm facing the same problem on Elementary OS (it's Ubuntu based).
Jekyll doesn't automatically update changes, I have to manually reload the page.

I've already tried the following, but nothing seems to work:

  • Used --watch
  • Used --force_polling
  • Reinstalled the plugin through the _plugins folder
  • Reinstalled the plugin using gem install
  • Reinstalled the plugin using bundle install
  • Checked if jekyll-admin is installed
  • Generated a blank project
@ashmaroli
Copy link
Member

@ashmaroli ashmaroli commented Dec 10, 2018

@mikekok jekyll-admin no longer has that bug.. So that's not the issue.
You may need to "serve" your site with --livereload to have Jekyll refresh pages automatically.
If problems persist, please open a "new issue"

@jekyll jekyll locked as resolved and limited conversation to collaborators Dec 10, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
14 participants
You can’t perform that action at this time.