config.yml not reloaded when running jekyll serve --watch

[aldoforce]

Running 1.5.1, OSX.

To reproduce:

• create a new site with "jekyll new test-site"
• start the server with "jekyll serve --watch"
• in another console edit the _config.yml, change the site's title
  (you will notice in the server console: Regenerating: 1 files at xxx xxx ...done.)
• refresh your browser

Result: no changes on the web page
Expected: if the site was regenerated (as console says), the edited configuration should apply (the new site's title should change)

Thx

[troyswanson]

Which version of Jekyll are you running?

[troyswanson]

Oh, whoops, you said 1.5.1. I believe this is a feature that is only on 2.0.0.

[parkr]

The configuration file can't be re-read when using watch, because it contains things like source and destination. It could only work if it were actually like running jekyll build multiple times – as it stands, it's just running Site#process when a file changes instead of building a new site object.

[doktorbro]

It is the intended behavior.

[mscharley]

That doesn't make it the right behaviour just the naive, easy behaviour.
On 12/05/2014 4:15 pm, "Anatol Broder" notifications@github.com wrote:

It is the intended behavior.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2302#issuecomment-42799078
.

[doktorbro]

That doesn't make it the right behaviour just the naive, easy behaviour.

Jekyll is a static site generator. The --watch option is limited by design.

[mscharley]

With more and more things being added to the configuration file (data,
collections) and the recent push to have pluginize all the things, I
believe that mentality is getting harder and harder to reasonably maintain.
Just because jekyll is a static site generator doesn't mean it has to be a
pain to use and develop with.
On 12/05/2014 6:30 pm, "Anatol Broder" notifications@github.com wrote:

That doesn't make it the right behaviour just the naive, easy behaviour.

Jekyll is a static site generator. The --watch option is limited by
design.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2302#issuecomment-42807236
.

[doktorbro]

With more and more things being added to the configuration file

My configuration file has only 2 entries:

markdown: kramdown
permalink: /blog/:year/:title/

It’s enough for a full-blown static website with posts, pages and assets. No plugins. It’s not a pain for me.

[mscharley]

It’s not a pain for me.

How nice for you. https://bitbucket.org/matthew-scharley/matt.scharley.me/src/d5531861bf9054537dd2fecacd873227ec1142c9/_config.yml?at=master

(And that isn't even the site with collections; that one's private though)

Have you considered you may be in the minority?

[mscharley]

I could also throw default front-matter at that. Make the default layout actually be a default layout and provide sensible defaults for my sitemap.xml. There's lots I could do, but having to remember to restart jekyll each time I tweak and test things is not user friendly.

[doktorbro]

Have you considered you may be in the minority?

This is a good question you can answer yourself first. The development time is much shorter than the usage time. If not, stop playing and start to create content.

[parkr]

It used to be mostly infeasible but I think we can make this happen. @mscharley If you have time for a PR, I'd be happy to review it. This isn't a huge priority for me at the moment so I probably won't get to it soon.

[nternetinspired]

Agree with previous majority sentiment. Really, how much time during a project build is spent toying with your global config? Observed behaviour is the expected result.

Set it and forget it.

[aldoforce]

hey guys, sorry for making so much noise with my ticket. That was not my intention. As I user I just wanted to report a strange behavior on my console about something that every time I edit (_config.yml) the jekyll serve --watch console says "Regenerating..." when that's not really happening. I think that the fix is to put somewhere on the documentation _CONFIG.YML doesn't auto regenerate and that will be enough. In fact I opened two consoles, one with jekyll serve --watch, and the other with jekyll build when I edit the config.

[parkr]

No I remember why we can't do this: if you change either source or destination, you're eff'd, so we said 👎 to this suggestion. Definitely use _data if you're using custom data. Otherwise, a quick ^C and restart should be 👌