Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Request: Better feedback in messaging / nothing generated in blank directory #717

kevinSuttle opened this Issue · 9 comments

3 participants


Running jekyll in a blank directory: Nothing is actually generated, yet the message says it was.

☰  mkdir jekyll-test
☰  cd jekyll-test 
☰  jekyll
WARNING: Could not read configuration. Using defaults (and options).
    No such file or directory - /Users/kevinsuttle/Desktop/jekyll-test/_config.yml
Building site: /Users/kevinsuttle/Desktop/jekyll-test -> /Users/kevinsuttle/Desktop/jekyll-test/_site
Successfully generated site: /Users/kevinsuttle/Desktop/jekyll-test -> /Users/kevinsuttle/Desktop/jekyll-test/_site
☰  ls
./  ../

Also, WARNING: Could not read configuration. Using defaults (and options). isn't really helpful in that, there is no config to read from. This relates to another issue of generating nothing but the site, when first running the jekyll command. Would it be better to generate a config file since it's needed anyway, and let the user know that in the process?


I foresee someone running jekyll by accident in other directories and getting _config.yml files all over the place. I could get behind a jekyll --init which wrote out a basic scaffold, but nothing automatic like this (especially if you're always using the defaults).

I would support a RuntimeError being thrown if Jekyll cannot find one's _layouts directory.


Agreed. One thing I'm seeing in the source files is that this kind of stuff should be prevented anyway (in theory at least).

And this scenario is missing in the feature spec also.


I think the tests fail because @path isn't null because there is no config file.

That's why we always get the 2nd stderr output, because it's not referencing @path.

It also doesn't help that the same warning is present for both no, and bad config files.


Doh. I wish I would have know you were working on this @parkr :p #726


Technically the message is true, it generated an empty site :)

And I'm against throwing exceptions over a missing _layouts directory, they're not actually required.


@tombell makes two good points. The only feasible way of doing this, which is probably not desirable, is to add a --helpful flag which throws errors and bugs the hell out of you until you fix things.


I don't think we're nearly that restricted. It's just a simple check. Don't generate the site, and tell me that I need at least an index.html file to generate a static site. Everything else is optional. No index.html, no site.

See my comments [1] [2] above and it doesn't look like this would take much.


We're doing #791.

@parkr parkr closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.