[14:35] <hatch> lazyPower: hey what software do you use for your blog now?
[14:35] <lazyPower> hatch: pellican
[14:36] <hatch> ahh I thought you'd might use Hugo
[14:36] <lazyPower> hugo was in an inconsistent state when i evaluated it
[14:36] <lazyPower> it was a toss up between jekyll and pelican. i opted into python
[14:37] <hatch> ahh gotcha
[14:37] <hatch> I added a few new features to the ghost blog this weekend 
[14:37] <lazyPower> I saw ;)
[14:37] <hatch> (I saw your comment on an issue thx)
[14:37]  * lazyPower thumbs up
[14:37] <lazyPower> you're on the right track
[14:37] <lazyPower> you care about concerns. I'm +1 for that * 100000000
[14:38] <lazyPower> encapsulation = key to a rich experience
[14:38] <hatch> thanks - the big issue now is how to properly add ssl support 
[14:38] <lazyPower> thats the responsibility of the front-end
[14:38] <lazyPower> nginx, haproxy, etc.
[14:38] <lazyPower> and looking over the existing relations - it seems like its a candidate for a new relationship so you can encapsulate teh ssl certificate in the middleware (ghost) - and pass it off over the wire to the web head when it creates teh vhost
[14:39] <lazyPower> but that may not be the propper approach. I haven't given it much more thought than the 5 minutes i spent reading issues. 
[14:39] <hatch> I wish we had a promoted nginx charm
[14:39] <hatch> so I could do haproxy > nginx > ghost
[14:39] <hatch> and call it a day :)
[14:40] <lazyPower> you dont really gain much by putting haproxy in front of nginx imho
[14:40] <lazyPower> nginx as a scale out LB webhead is phenomenal in terms of performance
[14:40] <hatch> well nginx should probably be a subordinate
[14:40] <hatch> is it?
[14:40] <lazyPower> there's use cases for both
[14:40] <lazyPower> yep
[14:40] <hatch> oh interesting
[14:40] <lazyPower> i ran a pure nginx shop @ level
[14:40] <lazyPower> it was the lowest maintenance webheads i had
[14:41] <hatch> so you're the guy to write the nginx charm then? :P
[14:41] <lazyPower> http://nginx.org/en/docs/http/load_balancing.html
[14:41] <lazyPower> hatch: well, let me frame the context here
[14:41] <hatch> I figured this out http://fromanegg.com/post/105250564587/how-to-rewrite-and-redirect-with-haproxy
[14:41] <lazyPower> i have a broken rails charm, dns charm to be completed, kubernetes work to catch up on, docker charm to add features to, and documentation all around to update
[14:41] <hatch> so that I can use the existing haproxy charm
[14:41] <lazyPower> yeah, i did enjoy that read and you're on teh right path there
[14:41] <hatch> oh so you have lots of free time :P
[14:42] <lazyPower> something like that :)
[14:42] <hatch> I'm not sure that haproxy can do ssl with 1.4
[14:42] <hatch> something I'll have to look into this week
[14:42] <lazyPower> i think / feel at this point - you're comign to a cross roads where it makes sense to develop what you want vs jack hammering haproxy
[14:43] <lazyPower> take the existing nginx / apache charms - convert to a sub, and implement the relationship you want/need - propose @ the list for discussion and if they dont like the implementation - PR's are welcome
[14:44] <lazyPower> you win by getting what you want, store wins by getting another implementation of a webhead
[14:44]  * lazyPower afk's to head to the dentist
[14:44] <hatch> looks like haproxy requires 1.5
[14:44] <hatch> enjoy :)
[14:44] <hatch> - for ssl that is
[15:38] <hatch> uiteam I need one more review for my guicharm branch (small) https://code.launchpad.net/~hatch/charms/trusty/juju-gui/add-uuid-configjs/+merge/248826
[15:40] <hatch> don't everyone jump at once :P
[17:07] <sebas5384> rick_h_: ping
[17:22] <rick_h_> sebas5384: pong
[17:23] <sebas5384> rick_h_: hey! I'm at the event, and tomorrow I'm gonna present using the online demo of juju gui
[17:23] <rick_h_> sebas5384: cool a new release was cut with bug fixes
[17:23] <sebas5384> rick_h_: I sow the bugs are still there 
[17:23] <rick_h_> sebas5384: so let me know if you need anything 
[17:23] <rick_h_> huh?
[17:23] <sebas5384> great!!
[17:23] <rick_h_> hatch: ^
[17:23] <rick_h_> sebas5384: try upgrading
[17:23]  * hatch perks up
[17:23] <sebas5384> take a look
[17:23] <sebas5384> demo.jujucharms.com
[17:24] <hatch> demo.jujucharms.com was not updated
[17:24] <rick_h_> sebas5384: oh right, it's not installed there yet
[17:24] <hatch> the real release was
[17:24] <rick_h_> sebas5384: that'll be Tues unfortunately
[17:24] <sebas5384> hmmm
[17:24] <rick_h_> sebas5384: but hte gui charm is updated
[17:24] <rick_h_> so deploy it somewhere and it'll be good
[17:24] <hatch> sebas5384: can you deploy the real charm to an env?
[17:24] <hatch> even local?
[17:24] <hatch> sebas5384: a workaround is to not drag from the charmbrowser
[17:24] <sebas5384> yeah i'm gonna do it locally
[17:24] <hatch> but instead click it then 'add to canvas'
[17:24] <hatch> if you must use demo.jc
[17:25] <sebas5384> hatch: demo.jc ?
[17:25] <hatch> demo.jc.c
[17:25] <hatch> demo.(j)uju(c)harms.(c)om
[17:25] <hatch>  :)
[17:25] <sebas5384> sorry don't know what that is
[17:25] <hatch> abreviation fail
[17:25] <sebas5384> hahahhaa
[17:25] <hatch> lol
[17:25] <sebas5384> ok got it
[17:26] <hatch> lemme know if you run into any other issues
[17:26] <hatch> rick_h_: is supposed to be swapping today :P
[17:27] <sebas5384> i'm have to leave now but I'll be back and install it to see whats happen
[17:27] <sebas5384> later :D
[17:28] <rick_h_> hatch: swapping today?
[17:28] <hatch> frankban: so I'm merging in my branch into the develop-trunk branch now - I complete the merge but I now need to write a comment. SHould I just copy the first msg from the PR?
[17:29] <hatch> rick_h_: yeah, didn't you say you were swapping today
[17:29] <hatch> ?
[17:29] <rick_h_> hatch: oh yea, leaving now :)
[17:29] <hatch> :) cya
[17:29] <frankban> hatch: yes
[17:30] <hatch> thx
[17:32] <hatch> Makyo: I just merged in the branch that was in pending - you may want to pull guicharm
[17:32] <Makyo> hatch, will do, thanks
[17:44] <lazyPower> hatch: does juju-gui have documentation online somewhere?
[17:44] <hatch> lazyPower: user docs?
[17:44] <lazyPower> si
[17:44] <hatch> negative
[17:44] <hatch> there is a guide on how to use it when you first boot it up though
[17:44] <lazyPower> ಠ_ಠ 
[17:44] <hatch> there is also the charm details
[17:44] <lazyPower> well thats better than nothing - can i get a link?
[17:44] <hatch> but that's it
[17:45] <hatch> lazyPower: to see it you can go here https://demo.jujucharms.com/ and then click "More" then click "Tutorial"
[17:45] <hatch> it's pretty basic 
[17:46] <lazyPower> oh
[17:46] <lazyPower> i asked about the wrong product
[17:46]  * lazyPower facepalms
[17:46] <lazyPower> i meant quickstart, sorry
[17:46] <hatch> lol
[17:46]  * lazyPower hangs his head in shame
[17:46] <hatch> not really beyond the help once it's installed
[17:46] <hatch> mbruzek was working on some I think
[17:47] <hatch> lazyPower: I'd love to see some of those docs on docs.jujucharms.com
[17:47] <lazyPower> hatch: your dead to me
[17:47] <hatch> lol
[17:49] <hatch> lazyPower: bug mbruzek I am pretty sure he said he was working on the documentation last week
[17:50] <lazyPower> well this exists
[17:50] <lazyPower> https://pypi.python.org/pypi/juju-quickstart
[17:50] <lazyPower> its rather sparse, but it helps
[17:51] <lazyPower> hatch: if i write the base docs, you guys gonna carry it to the finish line and keep it up to date?
[17:52] <hatch> best bet is to fire an email with your plans to the mailing list 
[17:52] <lazyPower> I can probably churn them out today while i'm digging my hands deep into kubernetes docs
[17:52] <lazyPower> hatch: you mean https://github.com/juju/docs/issues/261 doesn't cover it sufficiently?
[17:54] <hatch> lazyPower: assuming the appropriate parties see that bug :) 
[18:01] <hatch> lazyPower: when adding features to my ghost charm - is it better to queue up a bunch of changes then push up for promulgation review to reduce noise in the queue? Or does mutliple updates not really matter as long as you only do a single review sometime in the future
[18:01] <lazyPower> hatch: i'm a fan of small changes that are dependency linked
[18:02] <lazyPower> but thats personal preference. it makes the review go much faster as concerns are isolated and I know that i'm making an isolated change
[18:02] <lazyPower> it took me a while to grokk launchpad and how it does that - but stub quickly educated me in that realm
[18:02] <hatch> so if I pushed 3 updates, would there be three items in the queue or would it get consolidated into one?
[18:02] <lazyPower> it would be 3 items
[18:03] <hatch> and you don't mind the noise
[18:03] <hatch> I suppose it does make the reviews faster
[18:03] <hatch> but more frequent
[18:04] <lazyPower> yeah, i dont mind the noise. if you have dependency linked changes - it may cause failures in CI if they are dependent on teh functionality landing - so ymmv 
[18:04] <hatch> gotcha - I'll stop queuing them up in GH :)
[18:10]  * mbruzek returns from lunch.  
[18:10]  * mbruzek reads scroll back to see what bus he was thrown under.
[18:11] <hatch> just a school bus
[18:11] <mbruzek> hatch: I I was working on a bundle's documentation when I asked about the quickstart stuff.
[18:11] <hatch> nothing too bug
[18:11] <hatch> big
[18:11] <hatch> ohh
[18:11] <hatch> well then!
[18:13] <mbruzek> Hey hatch. I hosted a Ubuntu Global Jam for Minnesota and we found a few bugs over the weekend on jujucharms.com.  I could not remember where to create the bug so I just did it on launchpad.  
[18:13] <mbruzek> Since getting to work today lazyPower has set me straight that you would like those bugs in github
[18:14] <mbruzek> Do I need to copy them over or do you see the two that I created this weekend about "no author"
[18:14] <hatch> no problem - I pointed them out to the peeps in standup this morning
[18:14] <hatch> thanks for those
[18:14] <lazyPower> hatch: wait until you get the bill ;)
[18:15] <mbruzek> I suspect those could be the way the charm was pushed, to the repository.  If you need something done from a charmer side ... please ping lazyPower
[18:15] <hatch> uhh yeah...sent those to invoices@dev.null 
[18:15] <hatch> :P
[18:15] <hatch> haha
[18:15] <lazyPower> hatch: funny, i have dev.null aliased to fromanegg.com
[18:15] <lazyPower> \o/
[18:15] <hatch> lol
[18:15] <hatch> haha
[18:15] <hatch> so that's why I'm getting all this spam
[18:16]  * lazyPower whistles
[18:20] <hatch> ermahgerd so much documentation kadams54-away 
[18:20] <hatch> :)
[18:24] <hatch> kadams54-away: review done
[18:28] <lazyPower> hatch: just shot the email @ the list. feel free to reign fire down upon my plans
[19:19] <hatch> lazyPower: email looks good to me
[19:19] <hatch> :)
[21:09] <kadams54> hatch: thanks for the docs review. Yeah, there's still undocumented stuff… and I really should update to use doctests… and then there's API docs to generate… *sigh*
[21:10] <hatch> haha - docs are hard work for sure
[21:59] <huwshimi> Morning