=== \b is now known as benonsoftware [06:45] good morning [08:46] dholbach: Morning o/ if you want to catch up with the deployment: https://portal.admin.canonical.com/88368 [08:48] it's resolved? [08:48] and good morning :) [08:53] dholbach: no, but the fix could now be a simple case of fixing the connection to the db. Let's say I have high hopes for today. [08:54] ok... I was just wondering because the ticket said: Resolved: 1 week after opening / 1 day ago (Wed Feb 10 06:57 2016) [13:16] davidcalle, I just added automatically generating a .md snapcraft reference: https://github.com/ubuntu-core/snapcraft/pull/318/files :-) [13:17] it'd be the first customer for letting the md importer run a command after checking out the branch [13:21] dholbach: it parses plugins for doc? [13:23] it runs 'snapcraft help plugins', 'snapcraft help nodejs', etc [13:23] dholbach: nice :D [13:24] right now I'm thinking I should probably just write out one file, reference.md or something instead of one per topic [13:30] dholbach: it depends, if a plugin is heavily documented, it will look weird if they are all on the same page. On the other hand, having multiple pages makes linking easier and less confusing. BTW, yesterday I've built the juju doc, to see how it's done, it's nice and could probably be turned into a django app :) [13:32] davidcalle, there's one markdown file with 96 lines, the others are almost all in the range of 15-20 lines [13:32] davidcalle, which technologies do they use? [13:36] dholbach: md -> html, minimalist python server, static menu they update manually when a new doc is available, versions auto-generated by checking different git branches. [13:37] nice [13:39] dholbach: we should steal their UI at some point :) [13:39] yes, very much so [13:39] I talked to didrocks yesterday and we came to a similar conclusion [13:40] same :D [13:42] almost sounds like a decision ;-) === mhall119_ is now known as mhall119