+ [2014-02-02T20:48:44Z] kaffeebohne http://stackoverflow.com/questions/19835729/copying-generated-files-from-a-jekyll-plugin-to-a-site-resource-folder
+ [2014-02-02T20:51:09Z] kaffeebohne But it looks like i can write into the sites config before build time, which could be the key here
+ [2014-02-02T20:51:11Z] kaffeebohne https://github.com/jekyll/jekyll/blob/master/lib/jekyll/site.rb
+ [2014-02-02T20:51:33Z] kaffeebohne that doesn't work like that :/

message no. 17722

Posted by jclrb in #jekyll at 2014-02-02T04:16:51Z

Actually, I ran 'rails new xyz" and it ran fine until I got to a similar error. That's new. I just installed ruby 2.1.0 today and did the gem upgrade all (to upgrade gems for the new ruby version), so that might be it. I only installed jekyll after doing those things, but even so the update could have caused a problem. Let me poke around for a bit :)
+ [2014-02-03T23:08:47Z] pepper_chico hi, does jekyll/liquid provides a way to get current page's original source path?, for example, like, in the source /foo/bar.md, is the a way to get "/foo/bar.md"? for "/index.html", get "/index.html"?
+ [2014-02-03T23:09:16Z] pepper_chico without a special plugin, since it's to be deployed straight to github pages
+ [2014-02-03T23:10:14Z] pepper_chico page.url gives me things like "/foo/bar/"