<nanoc-gh>
[nanoc] ddfreyne deleted ruby-2-2 at dae0c95: http://git.io/vk4fM
<travis-ci>
nanoc/nanoc/master ab7b6c4 Denis Defreyne: The build was broken.
<ddfreyne>
I have no clue why this build broke.
pkunc has joined #nanoc
pkunc1 has joined #nanoc
pkunc has quit [Ping timeout: 255 seconds]
<guardian>
ddfreyne: I may have features for the sass filter, would you accept them in a 3.8.1 (because migrating to 4.0 is a huge effort I can't make right now)
<guardian>
like I'm calling nanoc('@config[:url]') from within a .scss :)
alerante has joined #nanoc
alerante has quit []
kAworu has joined #nanoc
tom[] has quit [Changing host]
tom[] has joined #nanoc
tom[] has quit [Changing host]
tom[] has joined #nanoc
tom[] has quit [Quit: Quit]
tom[] has joined #nanoc
jugglinmike has joined #nanoc
<kAworu>
what's the recommanded way to have variables (like say the website's title)
<kAworu>
should I create a Ruby module into the lib/ directory and use it form erb ? Or is there a nanoc way to do it ?
matthieu_m has joined #nanoc
matthieu_m has quit [Ping timeout: 245 seconds]
<ddfreyne>
guardian: No, it'll have to go in nanoc 4
<ddfreyne>
guardian: Upgrading to nanoc 4 is pretty easy actually (if you don't use the advanced features)
<ddfreyne>
kAworu: The recomended way is to set them in the nanoc configuration, e.g. "site_title: Foo" and then access it using @config[:site_title]
<kAworu>
ddfreyne: thanks, I'm checking the nano.ws source code to try to get a grip.