07:41 <skroon> ddfreyne: sorry for the late reply, but acting upon the "Route your nanoc items so it ends up in output/root output/blog output/support output/shared and then set up 4 hosts for that (mydomain.dev, blog.mydomain.dev, etc)

07:41 <skroon> "

07:43 <skroon> all of those 3 directories that you mentioned: output/root output/blog output/support will have their own full self contained html web pages right? meaning that output/root I can pickup and put on a webserver's root, output/blog I can pickup and put on a webservers' root, etc?

08:12 <ddfreyne> skroon: yes

08:27 <skroon> cool :-) and all CSS will then be refered to this output/shared right?

08:30 <ddfreyne> skroon: Yeah. You'll need to do some rewriting of the URLs though. I'd do that in a filter based on the relativize_paths one. Rewrite /shared/style/blah.css to http://shared.mydomain.tld/style/blah.css etc.

12:04 <skroon> ddfreyne: cool thanks, but durign development, you would thus not rewrite to this http://sahred.mydomain.tld/* ?

12:04 <skroon> or you would, and use sometinglike /etc/hosts to overwrite it? (or that anilformac)

12:31 <ddfreyne> skroon: I would, and use anvilformac or /etc/hosts

12:37 <ddfreyne> I think /etc/hosts is easier

12:38 <ddfreyne> Hmmm... would still need to have both .dev and .com domains. This is not super simple

12:38 <ddfreyne> You'd needto be able to compile for dev and for prod

19:27 <musicmatze> guardian: Building your library (PackedArray) taskes very long. Is this normal? around one minute on my device!

19:30 <musicmatze> guardian: Can you explain to me (maybe in a /query) why there are this much macros in your library? Makes code really bad readable for me. I'll be away from now, but I'm online via a bouncer, so you can query me!