[12:09] <jcastro> how do I get to the gui in the latest beta? I see it's deployed a unit in the admin environment
[12:10] <jcastro> but going to the ip in my browser doesn't work
[12:36] <jrwren> jcastro: `juju gui` will launch browser with url or display url.
[12:45] <jcastro> thanks
[12:56] <jcastro> jrwren: can I destroy models from the gui?
[12:58] <jrwren> jcastro: i don't know. I do not think that you can, yet.
[14:03] <hatch> jcastro: you can using the latest develop (but it's broken right now, hopefully will be fixed today)
[14:06] <jcastro> hatch: how do I use bleeding edge gui in 2.0 land?
[14:08] <hatch> jcastro: `make dist && juju upgrade-gui /path/to/dist` :)
[14:09] <hatch> but if you try that now it will break
[14:09] <jcastro> hah
[14:09] <jcastro> man dude, next time just kick me in the knee
[14:09] <jcastro> it would be sweet to have a config option to always deploy trunk gui though
[14:10] <hatch> I don't think so, we want people to use the latest stable release
[14:10]  * jcastro nods
[14:12] <hatch> jcastro: I think having the two steps makes it easy enough while providing enough of a roadblock to indicate that "maybe you should know what you're doing" to continue
[14:13] <hatch> jcastro: but we will make the gui easier to build in the future to lower that barrier 
[14:16] <jrwren> jcastro: but you can build a trunk tarball yourself and juju upgrade-gui like hatch said ;]
[14:16] <jrwren> hatch: how could it be any easier?  make sysdeps deps tarball wait and hour for it to break, clean-all try again, pray? :]
[14:16] <hatch> lol
[14:17] <hatch> by simplifying the deps required to build