alerante has quit [Read error: Connection reset by peer]
alerante has joined #nanoc
prxq has joined #nanoc
zi has quit [Read error: Connection reset by peer]
zi has joined #nanoc
VitamineD has quit [Ping timeout: 240 seconds]
louquillio_ has quit [Ping timeout: 240 seconds]
VitamineD has joined #nanoc
louquillio_ has joined #nanoc
<guardian>
o/
<guardian>
o/
<guardian>
ddfreyne: any opinion on what we discussed with bobthecow about :steal_rep yesterday night?
<ddfreyne>
I'm not sure I fully understand
VitamineD_ has joined #nanoc
VitamineD has quit [Ping timeout: 260 seconds]
VitamineD_ has quit [Quit: Computer has gone to sleep.]
VitamineD_ has joined #nanoc
VitamineD__ has joined #nanoc
VitamineD_ has quit [Ping timeout: 240 seconds]
VitamineD___ has joined #nanoc
VitamineD__ has quit [Read error: Connection reset by peer]
VitamineD___ is now known as cDlm
jugglinmike has joined #nanoc
<guardian>
ddfreyne: the same nanoc site, I want to build it for 2 targets:
<guardian>
ddfreyne: - target www == items are routed like /foo/bar/index.html
<guardian>
- target offline: items are routed like /foo/bar.html
<guardian>
target offline is used for zipping the whole doc/site and shipping to customer.
<guardian>
target www is to serve on a webserver
<guardian>
so far I do: NANOC_TARGET=www nanoc compile
<guardian>
or NANOC_TARGET=offline nanoc compile
<guardian>
yesterday we discussed compiling once, routing twice
<guardian>
from what I understood from nanoc 4, I think I can write the same item to 2 destinations easily
<guardian>
but with nanoc 3.x, I believe I have to use reps: :www and :offline reps, and then make a :steal_content filter that steals the compiled content from a rep
<guardian>
e.g. rep :www would go through the whole filter pipeline
<guardian>
but rep :offline would go through a single filter: :steal_content(:rep => :www)
<guardian>
that's how I envision achieving this with nanoc 3.x but maybe you have a better idea
<guardian>
is it a clear explanation?
<ddfreyne>
guardian: Yup, that is not a bad idea actually
<ddfreyne>
guardian: You could also have two snapshots for the same rep
<ddfreyne>
and then route those
<guardian>
two snapshots for the same rep?
<guardian>
in my mind: 1 rep == 1 compile, 1 route/destination file == 1 rep
<guardian>
so if I want 2 routes, 1 need 2 reps
<guardian>
if I want both foo/bar.html and foo/bar/index.html, then I need 2 reps for item /foo/bar/
<guardian>
I don't understand how I can have 1 item /foo/bar/, 2 snapshots, 2 destination files
<ddfreyne>
guardian: route '/blah/', rep: :something, snapshot: :a do … end
<ddfreyne>
guardian: route '/blah/', rep: :something, snapshot: :b do … end
<ddfreyne>
guardian: compile '/blah/', rep: :something do … snapshot :a … snapshot :b … end
<ddfreyne>
that works
<bobthecow>
ddfreyne: oh, right. i forgot you could route a snapshot.
<bobthecow>
that would work even better.
cDlm has quit [Ping timeout: 252 seconds]
jugglinmike has quit [Ping timeout: 260 seconds]
alerante has quit [Remote host closed the connection]
jugglinmike has joined #nanoc
jugglinmike has quit [Client Quit]
jugglinmike has joined #nanoc
cDlm has joined #nanoc
alerante has joined #nanoc
cDlm has quit [Ping timeout: 240 seconds]
cDlm has joined #nanoc
cDlm has quit [Read error: Connection reset by peer]