[21:22] <hatch> jujugui ping, anyone around?
[21:25] <hazmat> hatch, pong
[21:26] <hatch> hey hazmat I'm just doing some weekend hacking and can't for the life of me remember the command to build the gui from within the deployed charm
[21:27] <hazmat> hatch, define deployed charm and build gui?
[21:27] <hazmat> hatch, the gui charm has config options for source
[21:27] <hatch> gui charm is deployed to ec2 and I want to modify a file then re-make it on prod
[21:27] <hatch> yeah, I don't want to pull down a whole new branch or push up a whole new thing if I can help it
[21:28] <hatch> thing being gui source
[21:28] <hazmat> hatch, not sure that's an option you'd have to hack under the hood for that.. http://manage.jujucharms.com/~juju-gui/precise/juju-gui/config
[21:29] <hatch> yeah I do, I remember there was a fairly 'simple' hack but I  can't remember heh
[21:29] <hatch> oh well
[21:29]  * hazmat pulls latest charm
[21:30] <hatch> I'm on ~2g right now so uploading/downloading is painful haha
[21:31] <hatch> make that - anything- is painful :D
[21:32] <rick_h_> hatch: howdy
[21:32] <hatch> ahoy!
[21:33] <rick_h_> hatch: you have a branch of the charm right?
[21:33] <hatch> rick_h_ I have been trying to not pull it down
[21:33] <hazmat> hatch, modifying /var/lig/juju-gui and then make and maybe restart guiserver should do it i think
[21:33] <hatch> it would probably take a day at this speed
[21:34] <hazmat> hatch, you on the slopes?
[21:34] <hatch> hazmat was going to but decided to go to the lake instead
[21:34] <rick_h_> hatch: just commit and push that change to a branch
[21:34] <rick_h_> hatch: then update teh juju-gui-source to that hash.
[21:34] <rick_h_> errr that branch
[21:34] <rick_h_> hatch: it'll take a few min but then it'll rebuild from that branch
[21:35] <rick_h_> hatch: and it'll do it on ec2 so not an issue
[21:35] <hatch> rick_h_ seems like kind of a round-a-bout way no? should I not be able to just edit the code on the charm and `make something` to have it re build?
[21:35] <rick_h_> you only have to get up the git push
[21:35] <rick_h_> hatch: well ootb it's using a unzip'd dir and not a real env
[21:35] <hazmat> if its on remote
[21:35] <hatch> rick_h_ ohhh right
[21:35] <rick_h_> hatch: so things like dev deps and such might not be there yet
[21:35] <rick_h_> hatch: so it's a few steps, I think the git branch thing is the cheapest way atm. 
[21:36] <hatch> ok I guess I'll have to do it the normal way
[21:36] <hatch> yeah
[21:36] <rick_h_> hatch: you can configure it to use uncompressed files and such
[21:36] <hatch> yeah, I need to edit too many things
[21:36] <hatch> :)
[21:36] <rick_h_> hatch: and then you should be able to fine those files and edit them, but then it's a non-prod env
[21:36] <hatch> yeah
[21:36] <hatch> need prod
[21:36] <hatch> unfortunately
[21:36] <hatch> oh wells
[21:36] <rick_h_> then yea, make a branch and let the ec2 machine do the fetch/build
[21:37] <hatch> new slack task! make target in the charm to build from local source ;)
[21:54] <hatch> hazmat good work on the Digital Ocean plugin :) 
[21:54] <hatch> I can't wait to give it a try
[22:05] <hatch> hopping back offline, thanks for the help