louquillio has quit [Remote host closed the connection]
louquillio has joined #nanoc
Creationism has joined #nanoc
VitamineD has quit [Read error: Operation timed out]
_rgn has quit [*.net *.split]
ldk has quit [*.net *.split]
jaspervdj has quit [*.net *.split]
Evolution has quit [*.net *.split]
jaspervdj has joined #nanoc
ldk has joined #nanoc
guardian` has joined #nanoc
gkarekinian_ has joined #nanoc
guardian has quit [Ping timeout: 264 seconds]
gkarekinian has quit [Ping timeout: 264 seconds]
gkarekinian_ is now known as gkarekinian
yogsototh has joined #nanoc
_rgn has joined #nanoc
<jachymko>
tantalum, i have a /static directory (next to /content), and a static data source with /static prefix registered in nanoc.yaml
<jachymko>
then you don't need to alloww_periods_in_identifiers
<jachymko>
and then i have an empty compilation rule for /static/* and a routing rule that replaces /static with /assets, which is where my other (compiled) assets end up
<jachymko>
oh, he's not here anymore. oops:)
Rym has quit [Quit: Rym]
yogsototh1 has joined #nanoc
yogsototh has quit [Ping timeout: 246 seconds]
VitamineD has joined #nanoc
pavelkunc has joined #nanoc
jugglinmike has joined #nanoc
Creationism is now known as Evolution
tantalum has joined #nanoc
<tantalum>
Hi,
<tantalum>
I'm building a Nanoc site with a lot of images... I'm compiling the site and the process has been running for 22 minutes and has eaten up 1GB of memory
<tantalum>
is this normal?
<jachymko>
no, that's not normal
<jachymko>
what do you do with the images?
<tantalum>
They are design and content images
<tantalum>
it would be great if there was a way for nanoc to "skip over" them but also include them in the output.
<jachymko>
use a static data source
<jachymko>
[10:18:21] <jachymko> tantalum, i have a /static directory (next to /content), and a static data source with /static prefix registered in nanoc.yaml
<jachymko>
[10:18:53] <jachymko> then you don't need to alloww_periods_in_identifiers
<jachymko>
[10:21:09] <jachymko> oh, he's not here anymore. oops:)
<jachymko>
[10:20:39] <jachymko> and then i have an empty compilation rule for /static/* and a routing rule that replaces /static with /assets, which is where my other (compiled) assets end up
<jachymko>
but even then, the problem is somewhere else
<jachymko>
unless you filter the images, nanoc shouldn't be doing anything with them
<jachymko>
also, what's "a lot"? hundreds? thousands? tens of thousands?
<tantalum>
4000 images
<tantalum>
jachymko: I'd like to try it your way
<tantalum>
so let me see if I have this right
<tantalum>
you have a /static directory next to your /content and /layouts
<tantalum>
and you register it as a static data source in nanoc.yaml
<tantalum>
jachymko: Can you show me a copy of your nanoc.yaml file?
<creidieki>
Hi, I'm following the tutorial, and when I actually copy the webpage to a server the css doesn't work, because it's set to an absolute path.
<creidieki>
And on the server I'm in the /~username/ directory
<creidieki>
The tutorial mentions this problem, but doesn't seem to discuss what to do about it
<tantalum>
creidieki: You either need to use the :relativize_paths filter
<creidieki>
Is there a good way to tell nanoc to use a relative path for the css file, or to tell it which directory I'm going to be putting the webpage in?
<tantalum>
or fix the paths in your css
<creidieki>
tantalum: I saw posts saying to use :relativize_paths, but I don't know where to put it in the Rules file. I added it to the beginning of the rules for '/' and for '/stylesheet/', but that didn't change anything
<creidieki>
Okay, got it.
<tantalum>
creidieki: You need to put it in you /stylesheet/ compilation rules and set :type => :css
<jachymko>
no, you need to relativize the paths in you *html*
<jachymko>
the paths in the css are already relative to the location of the css file
<creidieki>
tantalum: Yeah, it turned out that filters happen in order, or some such, and it needed to be *after* the layout command.
<tantalum>
creidieki: yes
<creidieki>
Cool beans.
<creidieki>
In a perfect world, putting things under a non-root url would be in the "deployment" part of the "guides" section of the manual, but I know it's a volunteer project.
<creidieki>
Thanks. As usual, phrasing the problem to someone else made the solution obvious :-)
creidieki has left #nanoc [#nanoc]
bobthecow has joined #nanoc
bobthecow has quit [Changing host]
bobthecow has joined #nanoc
yogsototh1 has quit [Remote host closed the connection]
bobthecow has quit [Remote host closed the connection]
bobthecow has joined #nanoc
bobthecow has joined #nanoc
<Evolution>
ddfreyne: ping if you're around...
<bobthecow>
ping even if he's not?
<Evolution>
:-P
<ddfreyne>
pong
<ddfreyne>
Evolution: pong
<Evolution>
ddfreyne: so, I'm considering migrating from external bootstrap css links to using the sass-bootstrap bits.
<Evolution>
ddfreyne: the only things I can find about sass/compass integration bits seem to come from you
<Evolution>
wanted to know if there was any bit of doco you had or something I could read up on for a 'best practice' for pulling bootstrap into compass for nanoc
<bobthecow>
or live on the edge and use nanoc 4.x!
<bobthecow>
;)
<Evolution>
yeah, I'm going to go with 'no' for now thanks.
<Evolution>
:-P
<ddfreyne>
haha
<ddfreyne>
I would recommend not doing that for now
terinjokes has quit [Ping timeout: 245 seconds]
terinjokes has joined #nanoc
<Evolution>
okay. I'm screwing this up now. I have a /styles/ directory with subfolders. if I drop a null compile rule for the directory/* it works for things in that dir, but not in subdirs.
<Evolution>
is still tries to process them.
<Evolution>
do I have to do a */*/* then? to exclude that dir and all subdirs or is there something simpler I can do?
<bobthecow>
Evolution: in nanoc 3.x or 4.x?
<Evolution>
3.x
<bobthecow>
then /styles/* should apply to everything in styles.