<guardian>
you have '/command-line/bash/', '/command-line/cp' <-- those are the identifiers for two of your items
<FernandoBasso>
I really don't know what an item is. Is it something like /foo/bar/ or /foo/bar/something.md ?
<FernandoBasso>
Ah!
<guardian>
that's why I said, read a bit more about nanoc concepts :)
<FernandoBasso>
Sure. You are right.
<FernandoBasso>
But then I could do /command-line/* ?
<guardian>
then have a look at this routing rule that I apply to all items for a project of mine: http://pastebin.com/ekAtKAPR
<guardian>
yeah you could do that
<FernandoBasso>
All right. Thanks. I'll get busy re-reading the docs.
<guardian>
hmm that being said, lines 9-10 in the sample I pasted look dodgy :)
<FernandoBasso>
I wonder how I could inspect what a command is doing. Like if (true) puts item[:blah] or something...
<ddfreyne>
Hi
<ddfreyne>
FernandoBasso: You can use the show-rules
<FernandoBasso>
All right. I just saw that :filename is the path and the name of the file itself.
<FernandoBasso>
I added a puts item[:filename] inside the routing rules. I was afraid it would cause the compilation to fail.
jugglinmike has joined #nanoc
jugglinmike has quit [Quit: Leaving.]
jugglinmike has joined #nanoc
prxq has joined #nanoc
cDlm has quit [Ping timeout: 245 seconds]
wrl has joined #nanoc
<wrl>
hey, i'm having some trouble with the `static` data source
<wrl>
i'm generating stuff out of my `assets` directory, items_root = '/assets/'
<wrl>
i've got an empty compile rule and a passthrough route rule
<wrl>
but there are two things amiss: first, i can't get my route rule to actually do anything (if i drop a `raise RuntimeError` in there, it doesn't get raised)
<wrl>
i really wouldn't care about that, except that my images are getting copied into output with duplicated extensions