Updated _config.yml settings not used when auto-regenerating site #730

Closed
matthodan opened this Issue Jan 3, 2013 · 12 comments

Comments

Projects
None yet
8 participants

Jekyll should use updated config settings when auto-regenerating a site. Currently, Jekyll creates a site using the settings defined in "_config.yml" or passed as arguments (e.g. --server, --auto, etc.) when (and only when) the jekyll command is run. If "_config.yml" is updated after running jekyll --auto, Jekyll will not use the updated settings when regenerating the site. One must re-run jekyll --auto anytime they update "_config.yml".

@tombell I see your point, though don't you think it would be preferable to use the latest settings available when auto-regenerating? If Jekyll is going to auto-regenerate the site when "_config.yml" is updated (which it does), one would expect any updates to be reflected in the regenerated site. Understanding that some settings are used only when setting up auto regeneration, it feels a little like we're ignoring any update that can be used because of a few updates that cannot be used.

Contributor

mojombo commented Jan 4, 2013

I think it would be nice for Jekyll to reflect changes in _config.yml when running with --auto. If a config setting changes that can't be reflected, we could issue a warning, though this circumstance is probably rare enough to not even warrant the extra code. In any case, I'd love to see a pull request with a proposed solution.

👍 This would be great – it regularly confuses me that the site regenerates but settings changes aren't reflected.

why-el commented Jan 26, 2013

I went for a small solution (#779) and I need feedback.

svnpenn commented Feb 19, 2013

👍

padi commented Jul 2, 2013

👍

Owner

parkr commented Aug 31, 2013

Instead of this, we're going to ask that folks use the _data directory which has been proposed in #1003. This will be auto-reloaded upon a change and will be available via site.<filename>. Yay!

parkr closed this Aug 31, 2013

svnpenn commented Aug 31, 2013

@parkr what? Can you give an example of this new system would be used with say
_config.yml?

Owner

parkr commented Aug 31, 2013

Check out the PR - it has all the details there :)

Owner

parkr commented Aug 31, 2013

Ok it doesn't describe it as well as I thought on top because we shifted gears. My comment here describes it a bit better.

Owner

parkr commented Aug 31, 2013

Essentially, all the stuff you put in _data/members.yml (for example) is available via site.members in your Liquid templates. Additionally, everything in the _data directory is re-read on every change if you're watching with -w.

svnpenn commented Aug 31, 2013

@parkr this issue, that is to say issue 730, is not about "data" or some site.members. It is explicitly about settings as in this stuff
jekyllrb.com/docs/configuration.

So I will ask again - what does some new auto refreshing data folder have to do with updating the settings found in _config.yml? Providing an example would be helpful as well.

jekyllbot locked and limited conversation to collaborators Feb 27, 2017

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