Logs for #nikola for 2016-06-17

00:30:28 <KwBot> [nikola] izahn opened issue #2377: Avoid percent encoding URLs https://github.com/getnikola/nikola/issues/2377
14:17:38 -GitHub[nikola]:#nikola- [nikola] ralsina pushed 3 new commits to provide-snap: https://git.io/vogvj
14:17:38 -GitHub[nikola]:#nikola- nikola/provide-snap c356d77 Roberto Alsina: add home plug
14:17:38 -GitHub[nikola]:#nikola- nikola/provide-snap 91e670f Roberto Alsina: update to current status
14:17:38 -GitHub[nikola]:#nikola- nikola/provide-snap f318058 Roberto Alsina: handle snapcraft when changing version
14:21:29 <ChrisWarrick> ralsina: well, that was quick: https://bugs.launchpad.net/snappy/+bug/1593371
14:22:21 -travis-ci:#nikola- getnikola/nikola#7190 (provide-snap - f318058 : Roberto Alsina): The build passed.
14:22:22 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/2b5e7dcb2bcf...f3180581af54
14:22:22 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/138371669
14:22:27 <ralsina> well, it always helps when sabdfl acks your bug ;-)
14:23:01 <ralsina> BTW, we have now a nikola snap in the store that allows acces to ~ so it's not all that safe but it will work nicely
14:23:20 <ralsina> also, it seems containment doesn't work on arch (?!)
14:23:32 <ralsina> because of course you don't have apparmor in the host
14:24:01 <ChrisWarrick> what about fedora, which runs selinux?
14:24:46 <ralsina> you can't run selinux and apparor at the same time
14:25:00 <ralsina> so, no idea. I think the instructions suggest you disable selinux anyway
14:25:05 <ralsina> "for the time being"
14:25:16 <ChrisWarrick> # SELinux support is in beta, so on Fedora 24 you currently have to:
14:25:17 <ChrisWarrick> sudo setenforce 0
14:25:40 <ralsina> As soon as snapcraft CLI gets a new things in place, I can even cron a daily build for the "edge" channel and automate uploading releases to stable
14:26:19 <ChrisWarrick> automation is always wonderful
14:26:21 <ralsina> currently it can't mark uploads as published or choose channels for them, so that currently has tobe done on the website
14:26:27 <ralsina> yep
14:26:42 <ralsina> I am trying to save some time on monday to work on automating our releases
14:27:12 <ralsina> in fact, there is a "build me a snap" thing on launchpad already but I have no idea how to hook that to GH
14:27:33 <ChrisWarrick> nikola has 1024 stars on github
14:28:05 <ralsina> tweet it :-)
14:28:13 <ralsina> 2**10 stars is a nice number
14:28:31 <[Tritium]> nice round number
14:29:53 <ChrisWarrick> tweet done
14:31:20 <ChrisWarrick> speaking of fancy milestones, my server’s uptime is 355 days 20:48
14:31:55 <ralsina> ChrisWarrick: also, I am about to get started on the coil snap
14:32:09 <ChrisWarrick> ralsina: awesome, ping me if you need any help
14:32:14 <ralsina> ChrisWarrick: if that works, it's a killer app, I can maybe get it featured somewhere
14:33:01 <ChrisWarrick> can snap do “outside” http servers?
14:34:39 <ralsina> yep
14:34:47 <ralsina> you can just bind a port
14:35:29 <ralsina> ChrisWarrick: BTW, if you can give latest snap from the store a shot, it does build the demo site just fine here, but of course I am on the magical machine where it will always work :-)
14:35:50 <ChrisWarrick> will do
14:35:58 * ralsina considers just launching a quick droplet to check, but too lazy
14:38:07 <ChrisWarrick> ralsina: are there official vagrant 16.04 images?
14:38:21 <ralsina> it's a TLS, so ... I hope so?
14:38:25 <ralsina> LTS
14:39:34 <ChrisWarrick> it’s on atlas only now
14:40:35 <ralsina> our server is still 12.04 ... we should update it this year
14:41:20 <ChrisWarrick> you mean your personal VPS?
14:42:06 <ChrisWarrick> feel free, there’s only one cronjob and one virtualenv for nikola stuff (~/plugins-venv)
14:43:29 <ralsina> it will probably not break anything :-)
14:44:15 * ChrisWarrick runs `snap install nikola`
14:48:27 -GitHub[nikola]:#nikola- [nikola] Kwpolska pushed 1 new commit to provide-snap: https://git.io/vogkd
14:48:27 -GitHub[nikola]:#nikola- nikola/provide-snap d0470c6 Chris Warrick: Make minor fixes to snapcraft README
14:49:34 <ChrisWarrick> still broken :(
14:49:39 <ralsina> Pastebin?
14:49:40 <ChrisWarrick> [2016-06-17T14:49:21Z] ERROR: Nikola: This command needs to run inside an existing Nikola site.
14:50:09 <ralsina> weird
14:50:10 <ChrisWarrick> and the “read-only file system” thing appears when I try to use a relative path with `nikola init`
14:50:30 <ralsina> I wonder why it's using the wrong CWD for you :-(
14:50:59 <ChrisWarrick> there might be something about the store
14:51:16 <ChrisWarrick> when I sideloaded yesterday, there were no CWD bugs
14:56:30 -travis-ci:#nikola- getnikola/nikola#7193 (provide-snap - d0470c6 : Chris Warrick): The build passed.
14:56:31 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/f3180581af54...d0470c6796a4
14:56:31 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/138380446
15:07:11 <ChrisWarrick> ralsina: works really smooth on clean Ubuntu 16.04 LTS box
15:07:18 -GitHub[nikola]:#nikola- [nikola] Aeyoun pushed 1 new commit to master: https://git.io/vogqE
15:07:18 -GitHub[nikola]:#nikola- nikola/master 02affdc Daniel Aleksandersen: Don’t encode tildes in encodelink()...
15:07:21 <KwBot_> [nikola] Aeyoun closed issue #2377: Avoid percent encoding URLs https://github.com/getnikola/nikola/issues/2377
15:11:03 -travis-ci:#nikola- getnikola/nikola#7194 (master - 02affdc : Daniel Aleksandersen): The build was broken.
15:11:04 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/839358fd9a09...02affdcc3cd3
15:11:04 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/138386080
15:43:50 <KwBot> [nikola] Kwpolska reopened issue #2377: Avoid percent encoding URLs https://github.com/getnikola/nikola/issues/2377
15:47:03 <KwBot> [nikola] Kwpolska closed issue #2377: Avoid percent encoding URLs https://github.com/getnikola/nikola/issues/2377
15:47:19 -GitHub[nikola]:#nikola- [nikola] Kwpolska pushed 1 new commit to master: https://git.io/vognl
15:47:19 -GitHub[nikola]:#nikola- nikola/master c8c4dc4 Chris Warrick: Fix #2377 argument order...
15:59:01 <[Tritium]> huh.  I can actually watch the incoming commits and tell "yep, thats going to trigger a rebuild of my entire site.  nope, that ones not"
16:14:00 <[Tritium]> I'm thinking of breaking the nav out of my base template so it would render into a stub html file and using jquery to load it in client side
16:14:31 <[Tritium]> I am unclear on how I could get nikola to render that stub file
16:19:19 <ChrisWarrick> with an empty .html story
16:19:30 <ChrisWarrick> (or almost-empty)
16:23:31 <[Tritium]> the .html story would be the nav that I am stripping out of the site?
16:23:51 <[Tritium]> Oh hell, I'm overcomplicating this
16:27:27 <ChrisWarrick> [Tritium]: you would endd up with a site skeleton that you can put things into via jquery/whatever
16:30:26 <[Tritium]> Im going to experiment in a blank site
16:31:22 <[Tritium]> And I cannot wait for the day I can turn off my local package index (but i doubt that will happen)
16:59:13 <[Tritium]> Progress!  I can build NAVIGATION_LINKS into its own seperate file... but changing it still triggers a render on all pages.
17:10:13 <[Tritium]> well thats in a hard-to-fake-out location
17:22:27 <ChrisWarrick> [Tritium]: we make some assumptions about sites you can’t overcome
17:22:55 <ChrisWarrick> [Tritium]: without replacing NAVIGATION_LINKS with something of your own making, that is
17:24:59 <[Tritium]> ChrisWarrick: My theme of this week with nikola... a one line diff would make this possible (...almost.  if filters passed tasks instead of just the targets, I could do some hackery on the uptodate)
17:25:17 <[Tritium]> thats an API change, and i wont PR that
17:25:43 <ChrisWarrick> we probably wouldn’t accept that anyway
17:26:51 <[Tritium]> no doubt.
17:39:57 <ChrisWarrick> [Tritium]: you could throw together a simple 20-line task plugin  that produces an index.html file and that depends on a new config setting you creeae with your navigation links (but don’t forget about browsers without javascript support!)
17:42:42 <[Tritium]> ChrisWarrick: I think i will be doing a task plugin.  And, for reference, im not doing a single page with dynamic loading of stories, im doing the opposite - every story still has its page, the bootstrap nav is just getting loaded into it at runtime.  I have a minimal default nav in place already
17:43:06 <ChrisWarrick> why would you bother with that?
18:05:30 <[Tritium]> ChrisWarrick: The hosting provider has asked if i can stop reuploading the entire site every time I want to change navigation, if possible
18:06:01 <ChrisWarrick> morons
18:06:20 <ChrisWarrick> do they offer server-side includes?
18:06:23 <[Tritium]> No.
18:06:40 <ChrisWarrick> PHP?
18:06:43 <[Tritium]> No
18:07:07 <ChrisWarrick> tell them to implement one of those, otherwise you can’t comply
18:07:54 <[Tritium]> The reason they ask is they monitor all new uploads, and list them on the front page of their site.  Updating nav floods their front page.  The server is already bogged down only serving static content
18:08:23 <[Tritium]> I mean, this is an easy enough thing to do if i was building from scratch, just got to convince nikola to do it
18:09:44 <ChrisWarrick> decomission NAVIGATION_LINKS and build something of your own without touching global context
18:18:22 <[Tritium]> Yeah
18:28:55 <[Tritium]> I think i found a bug!
18:28:56 <[Tritium]> https://github.com/getnikola/nikola/blob/master/nikola/plugins/template/jinja.py#L89
18:56:43 <ChrisWarrick> [Tritium]: where?
19:00:18 <[Tritium]> open(...) as output: output.write(output.encode)
19:00:25 <[Tritium]> the name output is overloaded
19:01:02 <[Tritium]> I dont think that is actually used in reality
19:02:10 <ChrisWarrick> [Tritium]: oh.
19:09:38 -GitHub[nikola]:#nikola- [nikola] Kwpolska pushed 1 new commit to master: https://git.io/vogHE
19:09:38 -GitHub[nikola]:#nikola- nikola/master 06b18f6 Chris Warrick: Fix template saving (h/t @tritium21)...
19:09:56 <ChrisWarrick> [Tritium]: fixed
19:10:35 <ChrisWarrick> and yes, that code path is pretty useless
19:14:13 -travis-ci:#nikola- getnikola/nikola#7196 (master - 06b18f6 : Chris Warrick): The build passed.
19:14:14 -travis-ci:#nikola- Change view: https://github.com/getnikola/nikola/compare/c8c4dc4bccba...06b18f6cd8a5
19:14:14 -travis-ci:#nikola- Build details: https://travis-ci.org/getnikola/nikola/builds/138450674
19:24:03 <[Tritium]> Alright, I am calling this a lost cause (link issues).  Site admin will have to deal.
19:26:46 <[Tritium]> for an upside to this, it is remarkably easy to extend nikola
19:31:41 <[Tritium]> Actually, let me qualify that - its really easy to extend nikola if you have a browser with tabs and a will to keep 5 open to the source at any given time
20:00:40 <guitarma1> ok here's a question i'm ashamed to have to ask
20:00:52 <guitarma1> I believe I may have lost my nikola source site folder
20:01:04 <guitarma1> but i still have the website up in the cloud but this is the exported html files.
20:01:10 <guitarma1> any way to fix that?
20:01:51 <guitarman> to go in reverse?
20:01:55 <guitarman> site to source
20:02:07 <[Tritium]> guitarman: If you actually lost the site source, the best you can do is recover the source posts with pandoc and a lot of manual editing
20:02:07 <guitarman> I'm guessing no - was looking at the handbook, havent found that.
20:02:26 <guitarman> hmm [Tritium] sounds like more work than i want to do, i may start fresh and learn to be more organized with my files.
20:02:36 <[Tritium]> git
20:02:40 <guitarman> i appreciate the answer though
20:02:40 <guitarman> yeah
20:02:42 <[Tritium]> use git on your source :)
20:02:54 <guitarman> [Tritium]: do you just fire that up to github or your own?
20:03:37 <[Tritium]> I keep the source in a local git repo, and sync it to a server i own just for backup
20:03:49 <[Tritium]> (and dropbox)
20:07:01 <guitarman> [Tritium]: sounds like a good setup
20:07:37 <[Tritium]> (...and I keep my source word documents in onedrive... so i have something to rebuild from if the worst happens)