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

'source' directory #75

solars opened this Issue Aug 7, 2009 · 4 comments


None yet
5 participants

solars commented Aug 7, 2009


Wouldn't it make sense to set site.source to the absolute path of the dir where the jekyll command is run (if no config['site'] is specified).

I had some templates where it complained about non existing ./_includes - not sure when exactly though - until I specified the source dir in my config.


This comment has been minimized.


qrush commented Aug 8, 2009

Hmm, this probably makes sense. If you could whip up a patch or a good way to test this I'd be up for it.


This comment has been minimized.


christianhellsten commented Oct 26, 2009

This is easy to fix. I had problems using includes from within includes (in the _includes directory).

I fixed this issue by changing line 38 in from:
'source' => '.',
'source' => Dir.pwd,

This change breaks ./test/test_configuration.rb. To fix the test change line 6 in test_configuration.rb to:

 @path = File.join(Dir.pwd, '_config.yml')

I can create a patch if required.


This comment has been minimized.


mojombo commented Jun 22, 2010

If you're still up for making a patch and test for this, that would be awesome.


This comment has been minimized.


mojombo commented Jun 22, 2010

This is fixed in master.

@jekyll jekyll locked and limited conversation to collaborators Feb 27, 2017

pointblack pushed a commit to pointblack/jekyll that referenced this issue Feb 3, 2018

This issue was closed.

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