[02:13] <rick_h_> lazyPower: <3 my hero
[02:13] <rick_h_> ty
=== kadams54 is now known as kadams54-away
=== kadams54 is now known as kadams54-away
=== makyo_ is now known as Makyo
=== Makyo is now known as makyo_
=== kadams54 is now known as kadams54-away
=== makyo_ is now known as Makyo
[18:53] <firl> anyone know if there is a way to have juju gui/juju point to a local repo? or how to deploy my own internal repo?
[18:57] <rick_h_> firl: sure thing, there's a juju-gui-source config that can fetch from github
[18:57] <rick_h_> firl: oh sorry, you mean for charms
[18:57] <firl> rick_h_ yeah I want to deploy charms to an internal server
[18:57] <rick_h_> firl: so you can't do that from the GUI, you can do that from juju via local: charms. 
[18:58] <rick_h_> firl: and the juju-deployer will do some more things like git repos for the charms and the like if I recall
[18:58] <firl> gotcha, is it pretty involved in pretty much making a private juju charm repo for the gui to pull from
[18:59] <firl> or is it going juju-gui -> juju  for the charm browsing
[18:59] <rick_h_> rick_h_: well it's juju that has to talk to it and juju only talks to the public charmstore
[18:59] <rick_h_> bah firl ^ 
[18:59] <firl> haha :)
[18:59] <firl> so juju-gui just transparently talks to juju for the charms, k
[19:00] <firl> then I should be asking in the #juju room probably
[19:00] <rick_h_> firl: right, the only path around the charmstore is the local charm setup on disk which the deployer uses to pull things down and do the local repo
[19:00] <firl> yeah I can deploy local charms non issue, and it works well
[19:01] <firl> but for juju-gui to deploy new services from the local repo doesn’t quite work
[19:01] <firl> correct?
[19:01] <rick_h_> firl: right, because that involves uploading the zips and typically they're not zipped so the browser is a bit limited there
[19:02] <firl> kk, and juju-gui can’t replicate a service that already exists to duplicate it ( not add unit )
[19:02] <firl> because I could “pre load" the services, and juju-gui can see them all
[19:03] <rick_h_> right, we might be able to set something like that up but the use case is limited enough we've not added it
[19:03] <firl> gotcha, I could also just have the “zip” file and drag it to the UI ? http://askubuntu.com/questions/409637/how-do-i-deploy-a-local-charm-from-the-juju-gui
[19:03] <rick_h_> yes
[19:04] <firl> thank you so much, do you know if the ability to have an internal charm store to deploy from is something that is on the timelime ?
[19:06] <rick_h_> we're definitely working on making things better for locked down/offline environments, but no timeline atm
[19:07] <firl> gotcha, maybe if the PoC goes well it can be something I can help with; I’ve been really enjoying juju-gui for a while
[19:07] <rick_h_> firl: <3 definitely happy to gather feedback and work with folks
[19:09] <firl> thanks mate
[20:34] <jcastro> jrwren: hey, jim pharis is visiting me and he's wondering what the UI uses as it's js framework
[20:35] <jcastro> aka what did we pick post-YUI?
[20:44] <jrwren> jcastro: its YUI
[20:45] <jrwren> jcastro: It's still YUI. Nothing migrated.
[21:32] <rick_h_> jcastro: we're working on more pure JS, react (soon), and limping along because nothing is a good YUI replacement
=== kadams54 is now known as kadams54-away