alerante has joined #nanoc
smkelly has quit [Ping timeout: 240 seconds]
smkelly has joined #nanoc
smkelly has quit [Excess Flood]
smkelly has joined #nanoc
FunkyPenguin has quit [Ping timeout: 245 seconds]
FunkyPenguin has joined #nanoc
jugglinmike has quit [Quit: Leaving.]
terinjokes has quit [Ping timeout: 265 seconds]
terinjokes has joined #nanoc
alerante has quit [Remote host closed the connection]
alerante has joined #nanoc
alerante has quit [Ping timeout: 265 seconds]
relix has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 252 seconds]
gregkare has joined #nanoc
alerante has joined #nanoc
alerante has quit [Ping timeout: 252 seconds]
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
alerante has joined #nanoc
alerante has quit [Ping timeout: 240 seconds]
gregkare has quit [Quit: bye]
gregkare has joined #nanoc
<
GitHub117>
nanoc-core/master 3fad61b Denis Defreyne: Move checksumming logic to a central location
achal has joined #nanoc
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 3fad61b Denis Defreyne: The build was broken.
relix has joined #nanoc
<
GitHub97>
nanoc-core/master 5ac1157 Denis Defreyne: Use UNIX time in binary content checksum calculation
<
GitHub109>
nanoc-core/master 820139d Denis Defreyne: Add mtime and file size tests
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 5ac1157 Denis Defreyne: The build is still failing.
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 820139d Denis Defreyne: The build is still failing.
alerante has joined #nanoc
<
GitHub91>
nanoc-core/master 3258656 Denis Defreyne: Use small binary content checksum
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 3258656 Denis Defreyne: The build is still failing.
<
GitHub99>
nanoc-core/master 1e167aa Denis Defreyne: Test content/attributes checksum
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 1e167aa Denis Defreyne: The build is still failing.
<
GitHub123>
nanoc-core/master 6dd42b1 Denis Defreyne: Prevent entire content object from being dumped
<
GitHub35>
nanoc-core/master ad1f1dc Denis Defreyne: Test with JRuby 1.7.11
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 6dd42b1 Denis Defreyne: The build was fixed.
<
GitHub59>
nanoc-core/master 77e098e Denis Defreyne: Test with JRuby 1.7.11
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master ad1f1dc Denis Defreyne: The build is still failing.
<
GitHub155>
nanoc-core/master 90d7cec Denis Defreyne: Use Rubinius 2.2.6 on Travis
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 77e098e Denis Defreyne: The build passed.
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 90d7cec Denis Defreyne: The build was fixed.
<
GitHub176>
nanoc-core/master 9820000 Denis Defreyne: Remove JRuby and Rubinius from allowed failures...
<
travis-ci>
[travis-ci] nanoc/nanoc-core/master 9820000 Denis Defreyne: The build passed.
jugglinmike has joined #nanoc
<
guardian>
ddfreyne: are there asciidoctor attributes you found useful to set along with nanoc-asciidoctor?
achal has quit [Quit: Connection closed for inactivity]
alerante has quit [Remote host closed the connection]
alerante has joined #nanoc
<
ddfreyne>
guardian: Hmmmm, nothing in particular I think
<
guardian>
yeah I deciphered it since I asked
<
guardian>
options are mostly to control the output when using "standalone asciidoc"
<
guardian>
but when you just want a fragment in the context of nanoc or alike, most attributes are meaningless
<
guardian>
what's your practice with NANOC_ENV? you make it a string with different options separated by space?
<
guardian>
like NANOC_ENV="development drafts" <- don't minify, include drafts
<
guardian>
NANOC_ENV="production" <-- default, minify
<
guardian>
or do you use different environment variables for different options?
alerante has quit [Ping timeout: 250 seconds]
<
ddfreyne>
guardian: I don't use NANOC_ENV myself, but I'd probably have development/production
<
ddfreyne>
The latter having minification, relativizing paths etc
<
guardian>
another example
<
guardian>
if need to have 2 modes for my doc generation
<
guardian>
mode 1 == output/foo.html <-- this is when zipping the doc and shipping alongside a product
<
guardian>
mode 2 == output/foo/index.html <-- this is when hosting it on our servers
<
guardian>
NANOC_ENV="development offline" <-- is it good practice?
<
guardian>
or maybe NANOC_TARGET="offline" NANOC_ENV="production" nanoc compile
antognolli has quit [Remote host closed the connection]
alerante has joined #nanoc
cDlm has joined #nanoc
alerante has quit [Remote host closed the connection]
achal has joined #nanoc
<
guardian>
so?! what about my questions about NANOC_ENV? :)
alerante has joined #nanoc
alerante has quit [Ping timeout: 252 seconds]
alerante has joined #nanoc
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
achal has quit [Quit: Connection closed for inactivity]