Logs for #nikola for 2017-01-13

07:44:35 <KwBot> [nikola] stefanos82 opened issue #2633: Nikola auto causes exception, but still runs(?) https://github.com/getnikola/nikola/issues/2633
08:32:44 <toapolytoxaos_> I have a strange behavior with disqus. it does not work on all posts
08:32:47 <toapolytoxaos_> is this behavior normal?
08:40:38 <toapolytoxaos_> never mind...it was a freaking typo -_-
08:55:06 <KwBot> [nikola] Kwpolska closed issue #2633: Nikola auto causes exception, but still runs(?) https://github.com/getnikola/nikola/issues/2633
09:10:03 <ToApolytoXaos> ChrisWarrick: can you help me understand the logic behind two nikola commands?
09:10:12 <ChrisWarrick> ToApolytoXaos: go ahead
09:11:11 <ToApolytoXaos> what does nikola mean "clean all task" from "nikola clean --clean-all" command?
09:12:50 <ChrisWarrick> ToApolytoXaos: The clean command is provided by doit. The distinction between "default" and "all" tasks does not apply to Nikola — typically, you would just use `nikola clean` and ignore everything else
09:13:48 <ToApolytoXaos> the output folder maintains empty folders though and in order to remove them, you have to run another command which is again a bit confusing considering its name
09:13:59 <ToApolytoXaos> that is "nikola check -f --clean-files"
09:14:13 <ChrisWarrick> or rm -rf output/*
09:14:27 <ToApolytoXaos> yeah, that's another option, far more simpler
09:14:54 <ToApolytoXaos> but still though, the aforementioned command looks a bit...silly
09:15:33 <ChrisWarrick> it makes sense when you understand what each command does
09:16:09 <ToApolytoXaos> the way I understand is is that the first part, that is  "check -f" validates files
09:16:13 <ToApolytoXaos> correct?
09:17:07 <ChrisWarrick> check -f tells you what files in your output folder are orphans, i.e. created by someone else, or files that Nikola used to create but does not anymore (eg. deleted posts)
09:19:40 <ToApolytoXaos> semantically speaking, check -f is alright; --clean-files does not make any sense though
09:19:49 <ToApolytoXaos> that's my personal opinion though
09:19:52 <ChrisWarrick> it checks for orphans and removes files Nikola did not create
09:21:20 <ToApolytoXaos> well, the word "check" sounds more like a boolean logic, that is "yes the file is correct" or "no, it's broken". maybe "validate" would sounds fancier? ¯\_(ツ)_/¯
09:22:20 <ToApolytoXaos> because "check" word makes me think of it as the Linux kernel logic: [OK], [Failed]
09:24:14 -GitHub[nikola]:#nikola- [nikola] Kwpolska pushed 2 new commits to master: https://git.io/vM2Cc
09:24:14 -GitHub[nikola]:#nikola- nikola/master b465c67 Chris Warrick: Update README.rst...
09:24:14 -GitHub[nikola]:#nikola- nikola/master 83bdd93 Chris Warrick: Version 7.8.3...
09:24:30 <ToApolytoXaos> also, it looks like command "nikola clean -f" is the same as "nikola orphans"
09:26:19 <ChrisWarrick> almost, `nikola orphans` uses a different output format
09:26:26 <ChrisWarrick> but yes, they are synonymous
09:27:18 -GitHub[site]:#nikola- [nikola-site] Kwpolska pushed 1 new commit to master: https://git.io/vM2CP
09:27:18 -GitHub[site]:#nikola- nikola-site/master a664f8a Chris Warrick: Nikola v7.8.2...
09:27:53 <ToApolytoXaos> another observation is how nikola generates robots.txt
09:28:20 -travis-ci:#nikola- getnikola/nikola#8262 (master - 83bdd93 : Chris Warrick): The build passed.
09:28:21 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/7b84f24942c4...83bdd9320a43
09:28:21 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/191572282
09:29:14 <ToApolytoXaos> I have uploaded my old blogger content currently converted to nikola to https://stefanos82.github.io/alifealgorithm/ and obviously a robots.txt should not be located in a subfolder
09:30:37 <ToApolytoXaos> also, what intrigued me is Google's webmaster guidelines https://developers.google.com/webmasters/control-crawl-index/docs/faq#h01
09:31:29 <ChrisWarrick> ToApolytoXaos: ?
09:31:53 <ChrisWarrick> ToApolytoXaos: We always generate robots.txt, but you can disable that if using Nikola in a subfolder (there’s a warning)
09:32:10 <ToApolytoXaos> yeah, it's a yellow warning indeed
09:32:14 -travis-ci:#nikola- getnikola/nikola#8263 (v7.8.3 - 83bdd93 : Chris Warrick): The build passed.
09:32:15 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/v7.8.3
09:32:15 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/191572289
09:33:22 <ChrisWarrick> you can either ignore it, or disable robots.txt generation in conf.py
09:33:45 <ToApolytoXaos> all I see is a robots exclusion
09:34:28 <ToApolytoXaos> what flag should I use to completely disable genering robots.txt file?
09:34:49 <ChrisWarrick> ToApolytoXaos: Right, that’s woefully undocumented
09:35:06 <ToApolytoXaos> oh an Easter egg?
09:35:18 <ChrisWarrick> DISABLED_PLUGINS = ['robots_file']
09:35:33 <ToApolytoXaos> robots_file or robots.txt?
09:36:37 <ChrisWarrick> probably 'robots_file' or 'robots'
09:38:25 <ToApolytoXaos> robots_file does not work
09:38:29 <ToApolytoXaos> let me try robots and see
09:40:20 <ToApolytoXaos> OK, now it does not generate any robots.txt file inside output
09:40:32 <ToApolytoXaos> but does nikola uses robots for its local usage?
09:40:53 <ToApolytoXaos> if you go to localhost:8000/robots.txt display content
09:41:17 <ToApolytoXaos> something like User Agent: * Disallow: /
09:42:23 <ChrisWarrick> `nikola auto` does
09:43:11 -GitHub[nikola]:#nikola- [nikola] Kwpolska pushed 1 new commit to master: https://git.io/vM2lM
09:43:11 -GitHub[nikola]:#nikola- nikola/master 0e2f7b3 Chris Warrick: Add directions on how to disable robots.txt generation/warning...
09:45:40 <ToApolytoXaos> ah it's part of doit?
09:45:58 <ChrisWarrick> no
09:46:30 <ChrisWarrick> Run `doit help` to see all things provided by `doit`, with the only exception of auto (we rename doit auto → nikola doit_auto, and provide our own nikola auto)
09:46:50 <ChrisWarrick> we also like `nikola build` instead of `nikola run`
09:47:17 -travis-ci:#nikola- getnikola/nikola#8264 (master - 0e2f7b3 : Chris Warrick): The build passed.
09:47:18 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/83bdd9320a43...0e2f7b35a49c
09:47:18 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/191577044
09:47:38 <ToApolytoXaos> ah I see
10:20:30 <ToApolytoXaos> ChanServ: I think I have hit a bug
10:20:50 <ToApolytoXaos> I have created an assets folder that contains css and fonts in it
10:21:02 <ToApolytoXaos> when I run it the first time, everything runs as expected
10:21:27 <ToApolytoXaos> I run "nikola auto" and edited my custom.css that is located in files/assets/css/ directory
10:21:39 <ToApolytoXaos> I reduced my font size from 22px to 21px
10:21:53 <ToApolytoXaos> boom; it reverted to default font family
10:22:12 <ChrisWarrick> ToApolytoXaos: try refreshing the page, or checking what your CSS looks like now
10:22:45 <ChrisWarrick> `nikola auto` is one of the less stable parts of Nikola, mainly because it uses unstable stuff we have no command over
10:24:17 <ToApolytoXaos> where should I look for generated custom.css?
10:25:53 <ToApolytoXaos> stupid auto thing
10:26:13 <ToApolytoXaos> I have to refresh a couple of times to make it work
10:26:45 <ToApolytoXaos> still it doesn't work as expected though
10:27:21 <ToApolytoXaos> if you are on a certain page and run some css changes, upon re-run by "nikola auto" the existing css style is broken
10:27:24 <ChrisWarrick> then don’t use it
10:28:34 <ToApolytoXaos> what to not use?
10:28:43 <ToApolytoXaos> if I press F5 to refresh the page, I see the changes
10:38:51 -GitHub[plugins]:#nikola- [plugins] wirew0rm opened pull request #204: Plugin to change previous/next post to reflect section indices instead of global index (master...section_prevnext) https://git.io/vM2Es
10:56:15 <ToApolytoXaos> I'm really awful with CSS. I have found this beautiful font family and cannot produce the same outlook on my browsers https://fonts.google.com/specimen/Bree+Serif
10:57:40 <ChrisWarrick> ToApolytoXaos: add the <link …> snippet to EXTRA_HEAD_DATA, and use something like  body { font-family: 'Bree Serif', serif !important; }   in your CSS
10:58:19 <ToApolytoXaos> the EXTRA_HEAD_DATA I haven't done it; the rest I have inside my custom.css
10:59:33 <ToApolytoXaos> I have downloaded the fonts and added them inside files as assets/fonts/ folder
11:05:39 <ToApolytoXaos> OK, with EXTRA_HEAD_DATA works
11:05:53 <ToApolytoXaos> how to make it work with downloaded fonts?
11:09:23 <ChrisWarrick> CDNs work so much better for this
11:09:30 <ToApolytoXaos> yeah, I guess
11:09:31 <ToApolytoXaos> oh well
11:09:43 <ChrisWarrick> if you really want to re-host fonts, which costs you bandwidth, and possible licensing nightmares, you’re on your own
11:14:06 <ToApolytoXaos> no, I'm alright
13:23:42 -GitHub[plugins]:#nikola- [plugins] Kwpolska pushed 9 new commits to master: https://git.io/vM2yk
13:23:42 -GitHub[plugins]:#nikola- plugins/master d454236 Alexander Krimm: add Plugin to change navigation links in posts
13:23:42 -GitHub[plugins]:#nikola- plugins/master 6b4923d Alexander Krimm: Listen for the right event and minor fixes
13:23:42 -GitHub[plugins]:#nikola- plugins/master 9d1ec67 Alexander Krimm: Add README
13:28:10 -travis-ci:#nikola- [PLUGINS] getnikola/plugins#1139 (master - c8f4a70 : Chris Warrick): The build passed.
13:28:11 -travis-ci:#nikola- [PLUGINS] Change view: https://github.com/getnikola/plugins/compare/b24a4c87158c...c8f4a70cb7a2
13:28:11 -travis-ci:#nikola- [PLUGINS] Build details: https://travis-ci.org/getnikola/plugins/builds/191629904