<ddfreyne>
_rgn: The advantage of using the pruner is that site compilation time will go down, because not everything needs to be recompiled
<ddfreyne>
_rgn: The prune needs to go after the compile
<ddfreyne>
_rgn: and you can load the pruner config too, instead of passing {}
<_rgn>
it assumes the last argument is a hash i guess. so i'll pass site.config[:prune] instead of :exclude => site.config[:prune][:exclude]
yogsototh has quit [Ping timeout: 245 seconds]
pavelkunc has joined #nanoc
<ddfreyne>
_rgn: That works unless you have no prune section in the config
<ddfreyne>
Maybe I'll reserve next weekend for some nanoc work. It's needed :)
<skroon>
ddfreyne: In the frontmatter I would like to add a list of language alternatives for i18n + SEO
<skroon>
if I can call it "front matter" since jykell, middleman, etc call it that way :)
<skroon>
cci
<_rgn>
pretty happy that i did the switch from stasis to nanoc
<_rgn>
the setup was way easier with stasis but the compilation was slow and directory structure was a bit weird
<ddfreyne>
_rgn: One of the goals of nanoc 4.0 is to simplify things. there are a few weird idiomatic things that nanoc does and I'm getting rid of those
<_rgn>
for what it's worth coming from rails and co. the route keyword thing was pretty confusing
<_rgn>
route '/stylesheet/' do '/style.css' end huh???
<_rgn>
i get it now but the '/stylesheet/' syntax raised some eyebrows
<ddfreyne>
_rgn: that is already gone in nanoc 4.0. It's something like compile '/style.css' do ; filter :rainpress ; write '/stylesheet.css' ; end
<_rgn>
seems more intuitive
<ddfreyne>
The identifiers (two slashes) have advantages but I don't think it weighs up to the confusion
<_rgn>
yep, '/style.css' is an abstraction i'm already aware of, a path to a file
<ddfreyne>
Upgrading to nanoc 4.0 should be relatively easy though.
cDlm has quit [Quit: cDlm]
yogsototh has joined #nanoc
jugglinmike has joined #nanoc
skroon has quit [Ping timeout: 245 seconds]
bghost has joined #nanoc
bghost has quit [Quit: leaving]
bghost has joined #nanoc
<musicmatze>
Yeah, finally setup nanoc in a VM (Mint linux) and now I'm able to use my new notebook, only. So I can use my old to play around with linux kernels and so on :-P
<musicmatze>
And, of course, I could setup a testing environment for my static site compiler and later compare it against others like nanoc or jekyll ...
Rym has quit [Ping timeout: 260 seconds]
Rym has joined #nanoc
Rym has quit [Ping timeout: 260 seconds]
<guardian>
ddfreyne: would you recommend using nanoc 4 already?