ddfreyne changed the topic of #nanoc to: 3.6.4 (may 29th) | web http://nanoc.ws/ | repo http://bit.ly/XE6e3G | issues http://bit.ly/VfXaSV | forum http://ho.io/n-discuss | irclog http://irclog.whitequark.org/nanoc
pavelkunc has quit [Quit: Leaving.]
louquillio has quit [Remote host closed the connection]
yogsototh has joined #nanoc
<ddfreyne> musicmatze: But you have nanoc as an inspiration. THat counts, no? ;)
<guardian> ddfreyne: I'll try to make up time to properly open my site sources, then you'll get to clone it and eventually reproduce the show-data |less thing
yogsototh1 has joined #nanoc
yogsototh has quit [Ping timeout: 264 seconds]
<musicmatze> ddfreyne: yeah! :-P
skroon has joined #nanoc
louquillio has joined #nanoc
<skroon> good morning all
pavelkunc has joined #nanoc
pavelkunc has quit [Ping timeout: 256 seconds]
pavelkunc has joined #nanoc
pavelkunc has quit [Client Quit]
pavelkunc has joined #nanoc
<ddfreyne> guardian: that would be cool
cDlm has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
pavelkunc has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
pavelkunc has joined #nanoc
skroon has quit [Quit: leaving]
Rym has joined #nanoc
_rgn has joined #nanoc
<_rgn> hey. a quick question. ./content is the right place to put html/css/js/images, right? and then i should probably add proper routes to Rules or something
<guardian> well it depends
<guardian> some people put their fonts and images in static/fonts and static/images
<guardian> but I like to have everything go through nanoc's pipeline
<guardian> with the static datasource, files are just copied over to output folder
<guardian> but as I said, I like to have everything go through nanoc's pipeline. So that I can e.g. compress images
<_rgn> is a static/ a special dir mentioned somewhere, because i can't find it in the skeleton
<guardian> look for static datasource in the dco
<guardian> doc
<_rgn> have to say this route & identifier scheme is a bit confusing
<_rgn> so uh... Found 2 content files for content/css/jquery; expected 0 or 1
<_rgn> oh wow "Unfortunately, you can't have two files in the same directory with the same name before the last extension. For nanoc 4.0 it'll be rewritten to change that."
<stbuehler> actually you can if you write your own datasource :)
jugglinmike has joined #nanoc
<_rgn> i'm getting there slowly but surely, a lot of trial and error
<ddfreyne> in case you hadn't found it yet
<ddfreyne> And that *has* already changed in nanoc 4.0, but that version is not quite ready for production yet ;)
<_rgn> well assuming i have my scripts under content/js (not a static data source) what's the best way to deal with dots in filenames?
<ddfreyne> _rgn: what are the filenames that you're dealing with? somelibrary.js + somelibrary.pluginname.js?
<_rgn> exactly
<ddfreyne> _rgn: You can set allow_periods_in_identifiers: true in the nanoc configuration. This way, only the final extension will be stripped
<_rgn> i noticed that option, does it have side effects?
<ddfreyne> So you'll get identifiers /somelibrary/ and /somelibrary.plugin/
<ddfreyne> So you'll get identifiers /somelibrary/ and /somelibrary.pluginname/
<ddfreyne> _rgn: Mmmm, not really apart from that
<ddfreyne> Or you can use nanoc 4.0 which handles that quite differently, but prepare for other pains ;)
<_rgn> btw i noticed this issue: https://github.com/nanoc/nanoc/issues/328 - why doesn't autoprune option work with guard?
pavelkunc has quit [Quit: Leaving.]
<ddfreyne> _rgn: Ohh, I misinterpreted that issue. I'm reopening that now
<_rgn> i find myself doing nanoc prune --yes && nanoc because it's very useful to have output reflect the state of Rules to learn how it work exactly
<ddfreyne> _rgn: Yeah that is definitely a bug, because guard-nanoc should honor that
pavelkunc has joined #nanoc
Rym has quit [Quit: Rym]
Rym has joined #nanoc
<ddfreyne> _rgn: It is also useful to enable the :stale check so you don't deploy any stale files
<_rgn> is there a builtin way to have multiple environments? to render assets in the markup different depending on if they're minified etc.
<ddfreyne> _rgn: There isn't
<_rgn> i used Stasis previously, and you couldn't use ENV variables within Rakefile
<_rgn> for some reason
<_rgn> so Stasis had this way of compiling your project programmatically (Stasis.new.render)
<ddfreyne> _rgn: You can set env variables and let nanoc change compilation on that, but if you want to do that, you have to set @config[:env] = ENV['NANOC_ENV'] in the preprocess block, and use @config[:env]
<ddfreyne> That way, nanoc will correctly track chagnes to the @config[:env] variable
<_rgn> oh what's the preprocess block?
<ddfreyne> _rgn: you can compile nanoc sites programatically too (not sure what it is in 3.x anymore, but in 4.0 it will be site = Nanoc::SiteLoader.new.load ; Nanoc::Compiler.new(site).run
<ddfreyne> _rgn: the preprocess block is executed before compiling. See http://nanoc.ws/docs/troubleshooting/#error-can-t-modify-frozen-x or http://nanoc.ws/docs/guides/paginating-articles/ for an example
<musicmatze> &window list
<musicmatze> sry!
<ddfreyne> musicmatze: That's a weird keyboard layout right there
<darix> ddfreyne: normal german layout
<darix> &/ are right next to each other
<musicmatze> :D
<musicmatze> yeah... unfortunately, when I plugin an external usb keyboard, it switches to another layout and / becomes & -.-'
<ddfreyne> I really should look into some open nanoc issues. :(
<ddfreyne> If somebody wants to help me out... :)
pavelkunc has quit [Quit: Leaving.]
pavelkunc has joined #nanoc
cDlm has quit [Ping timeout: 245 seconds]
cDlm has joined #nanoc
<_rgn> hm yeah can't pass an ENV variable to sh "nanoc compile" with rake, but i can wrap the compilation to a bash script where i set the ENV variable
Rym has quit [Ping timeout: 260 seconds]
Rym has joined #nanoc
louquillio has quit [Remote host closed the connection]
Rym has quit [Ping timeout: 245 seconds]
Rym has joined #nanoc
<antognolli> ;q
<antognolli> oops
yogsototh1 has quit [Ping timeout: 240 seconds]
yogsototh has joined #nanoc
tbm has quit [Ping timeout: 248 seconds]
<bobthecow> _rgn: don't use sh "nanoc compile" in rake, use the programmatic compile call.
<_rgn> makes sense, wasn't able to find such api
<bobthecow> then you can pass env variables through rake.
louquillio has joined #nanoc
pavelkunc has quit [Quit: Leaving.]
<ddfreyne> Yeah, sh "nanoc" is discouraged
yogsototh has quit [Remote host closed the connection]
jugglinmike has quit [Quit: Leaving.]
<_rgn> bobthecow: i guess you can access @config through the site object
<_rgn> didn't try yet
<_rgn> then i don't need env variables
Rym has quit [Ping timeout: 256 seconds]