run-jekyll-on-windows icon indicating copy to clipboard operation
run-jekyll-on-windows copied to clipboard

Ruby config.yml Instructions

Open RamblingCookieMonster opened this issue 9 years ago • 6 comments

In case it helps - after the ruby dk.rb init step, it might be worth noting that the user should add the path to the Ruby installation to their config.yml (it is not performed automatically, at least on the systems I have tested this on).

Thanks for the handy instructions!

RamblingCookieMonster avatar Mar 25 '15 22:03 RamblingCookieMonster

To clarify, you checked the "Add Ruby executables to your PATH" box during setup, right? (Or kept it checked.)

Could this be affected by whether or not the installation is run with admin permissions?

juthilo avatar Mar 26 '15 21:03 juthilo

Yes, path includes the Ruby dir - the config.yml generated by ruby dk.rb init is just empty.

Should have searched before - It looks like it might be a known issue?

RamblingCookieMonster avatar Mar 26 '15 21:03 RamblingCookieMonster

Oops, I totally misread the issue as being about PATH missing Ruby after installation. Sorry!

I'm gonna check out your link and probably add a note about this to the guide soon. Seems like 64bit Windows can be a real deal breaker for Ruby these days in general...

juthilo avatar Mar 26 '15 21:03 juthilo

No worries!

Apart from that one bit, everything worked flawlessly on both Windows 10 and Windows 8.1.

RamblingCookieMonster avatar Mar 26 '15 22:03 RamblingCookieMonster

I followed the guide today on Windows 7 64-bit, had the same issue with having to manually set the dev kit path in config.yml after running dk.rb init. I was running the installer as an administrator at the time. A small note in the guide would be sufficient IMO, the error message from running dk.rb install is pretty clear but would be nice to point it out since it seems pretty well established. Great work on the guide, much easier then the last time I fought through it on my own.

dlongest avatar May 04 '15 22:05 dlongest

This is a 64-bit specific issue with the DevKit. #53 fixes this in bcf23f3 by documenting the workarounds.

clintstotesbery avatar Sep 27 '16 21:09 clintstotesbery