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

Closed
javirivera opened this Issue Sep 15, 2014 · 20 comments

Comments

Projects
None yet
@javirivera

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

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Sep 15, 2014

Member

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

Member

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

This comment has been minimized.

Show comment
Hide comment
@javirivera

javirivera 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?

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

This comment has been minimized.

Show comment
Hide comment
@kleinfreund

kleinfreund Sep 15, 2014

Contributor

jekyll serve --force_polling

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

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@javirivera

javirivera 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!

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

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Sep 15, 2014

Member

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.

Member

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

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Sep 15, 2014

Member

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

Member

parkr commented Sep 15, 2014

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

@kleinfreund

This comment has been minimized.

Show comment
Hide comment
@kleinfreund

kleinfreund Sep 15, 2014

Contributor

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?

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Sep 15, 2014

Member

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.

Member

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

This comment has been minimized.

Show comment
Hide comment
@alfredxing

alfredxing Sep 15, 2014

Member

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

Member

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

This comment has been minimized.

Show comment
Hide comment
@javirivera

javirivera 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.

@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

This comment has been minimized.

Show comment
Hide comment
@XhmikosR

XhmikosR Oct 8, 2014

Contributor

@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.

Contributor

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

This comment has been minimized.

Show comment
Hide comment
@parkr

parkr Nov 29, 2014

Member

Check your exclude config variable as well.

Member

parkr commented Nov 29, 2014

Check your exclude config variable as well.

@parkr parkr closed this Nov 29, 2014

@makeaweli makeaweli referenced this issue in Refresh-Hilo/Refresh-Hilo.github.io Feb 11, 2015

Merged

Vagrant Jekyll Watch Fix #3

@robotdana

This comment has been minimized.

Show comment
Hide comment
@robotdana

robotdana 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)

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)

@mdotasia mdotasia referenced this issue in UNStats/website-theme Apr 15, 2015

Closed

Use force polling for Jekyll watch on Vagrant #76

@orbeckst orbeckst referenced this issue in MDAnalysis/MDAnalysis.github.io Mar 17, 2016

Closed

local jekyll build does not auto-watch #22

@lcreid lcreid referenced this issue in lcreid/rails-5-jade May 7, 2016

Closed

Jekyll `--incremental` doesn't work. #2

@LukeMcGurdy

This comment has been minimized.

Show comment
Hide comment
@LukeMcGurdy

LukeMcGurdy Jul 20, 2016

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

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

@alexshyba

This comment has been minimized.

Show comment
Hide comment
@alexshyba

alexshyba 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

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

This comment has been minimized.

Show comment
Hide comment
@iddan

iddan 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

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

This comment has been minimized.

Show comment
Hide comment
@wraybowling

wraybowling 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.

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

This comment has been minimized.

Show comment
Hide comment
@ashmaroli

ashmaroli May 17, 2017

Member

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

Member

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

This comment has been minimized.

Show comment
Hide comment
@wraybowling

wraybowling 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 WOW. Gosh I hope you didn't spend too long figuring that out, but that did the trick. Thank you!

@ashmaroli

This comment has been minimized.

Show comment
Hide comment
@ashmaroli

ashmaroli May 17, 2017

Member

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.. 😉

Member

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.. 😉

@prasbg prasbg referenced this issue in PyryM/truss Dec 1, 2017

Open

Documentation via Jekyll #42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment