[04:45] <shazzner_> yay my gitolite charm is finally working :)
[07:06] <shazzner_> https://bugs.launchpad.net/charm/+bug/906176
[07:06] <_mup_> Bug #906176: Gitolite charm <new-charm> <juju Charms Collection:New> < https://launchpad.net/bugs/906176 >
[07:06] <shazzner_> pretty sure it doesn't meet all criteria for inclusion but wanted to get it in there
[07:14] <poolie> hello?
[09:14] <koolhead11> hi all
[09:22] <niemeyer> Goooood mondays!
[09:23] <koolhead11> :P
[09:27] <rog> niemeyer: yo!
[09:31] <niemeyer> Hey guys
[09:37] <nijaba> good morning charmers and hackers!
[09:37] <nijaba> shazzner_: I posted a few comments on you new charm bug for gitolite
[09:59] <_mup_> juju/go-new-revisions r15 committed by gustavo@niemeyer.net
[09:59] <_mup_> Integrated new tip and fixed it.
[10:00] <koolhead11> quick question
[10:00] <koolhead11> juju deploy --repository=example local:mysql
[10:00] <koolhead11> does not work for me
[10:00] <koolhead11> but
[10:00] <koolhead11> juju deploy --repository=/home/atul/example local:mysql  does work
[10:00] <koolhead11> so am i supposed to give complete path?
[10:01] <koolhead11> or since i was not in my home directory while running juju deploy --repository=example local:mysql
[10:01] <koolhead11> i got the error
[10:11] <koolhead11> also i wrote a charm and trying to deploy it, i got state: install_error
[10:11] <nijaba> koolhead11: juju deploy --repository=example local:mysql will work if you are in the parent dir of example
[10:11] <koolhead11> how can i see that error in detailed form?
[10:11] <koolhead11> nijaba: yes, got that part :P
[10:12] <nijaba> koolhead11: juju debug-hook in one terminal, then juju resolved --retry in another
[10:12] <nijaba> koolhead11: in the juju debug-hook window you will sent be able to manual execute hooks/install and see what went wrong
[10:12] <nijaba> s/sent/then
[10:16] <koolhead11> nijaba:  juju debug-hook gives nitthing, am i supposed to provide some argument too
[10:19] <nijaba> koolhead11: juju debug-hooks needs to be given a unit name and should open a terminal session on the unit
[10:19] <nijaba> juju debug-hooks --help
[10:21] <koolhead11> nijaba: thanks am inside the box.
[10:38] <koolhead11> nijaba: also am i supposed to do some config changes after installing juju to see /var/log/juju ?
[10:40] <nijaba> koolhead11: /var/log/juju?  was not aware there was such a thing.  I always use the command 'juju debug-log' to see juju's logs
[10:41] <koolhead11> nijaba: cool. got it. :)
[10:41] <koolhead11> http://askubuntu.com/questions/81818/failure-to-troubleshoot-a-juju-charm-deployment
[11:48] <koolhead17> i have one more issue http://paste.ubuntu.com/775206/
[11:48] <koolhead17> i had to forcefully switch off my machine while juju was running
[11:48] <koolhead17> now juju -v bootstrap giving me this error
[11:49] <koolhead17> i had to do sudo juju -v bootstrap to get it working
[13:30] <koolhead17> hi again
[13:33] <koolhead17> hostname=`unit-get public-address`
[13:34] <koolhead17> i can define it in my install hook
[13:34] <mchenetz> Morning
[13:47] <niemeyer> koolhead17: So, what's up there?
[13:47] <koolhead17> [19:11] <koolhead17> this is the modified owncloud install script http://paste.ubuntu.com/775300/ [19:11] <koolhead17> and this is the error am getting http://paste.ubuntu.com/775293/ [19:11] <koolhead17> hostname: unbound variable
[13:48] <koolhead17> am i supposed to do anything else
[13:48] <koolhead17> in the charm
[13:50] <niemeyer> koolhead17: It's telling you that the $hostname variable is unbound
[13:50] <niemeyer> koolhead17: Which is true
[13:51] <niemeyer> koolhead17: You have to fix it
[13:51] <koolhead17> niemeyer: where am i supposed to mention about that
[13:51] <koolhead17> https://code.launchpad.net/~koolhead17/charm/oneiric/owncloud2/trunk
[13:51] <koolhead17> am modifying this
[13:51] <koolhead17> after testing it on my juju env
[13:52] <niemeyer> koolhead17: Sorry, I don't understand the question
[13:52] <niemeyer> koolhead17: You see the error message you pasted there?
[13:52] <niemeyer> 2011-12-19 13:24:57,987: hook.output@ERROR: /var/lib/juju/units/owncloud2-0/charm/hooks/install: line 5: hostname: unbound variable
[13:52] <koolhead17> niemeyer: yes
[13:52] <niemeyer> koolhead17: Go to line 5 of your script
[13:52] <niemeyer> koolhead17: What do you find there
[13:52] <niemeyer> ?
[13:53] <koolhead17>   5 juju-log "Retriving  hostname: $hostname"
[13:53] <niemeyer> koolhead17: Precisely
[13:53] <niemeyer> koolhead17: Now, what does the error message say>?
[13:54] <koolhead17> $hostname variable is unbound
[13:54] <niemeyer> koolhead17: Right.. and where is it being bound/defined?
[13:55] <koolhead17> niemeyer: just below that line
[13:55] <koolhead17> got it
[13:55] <niemeyer> koolhead17: Bingo
[13:55] <koolhead17> :)
[13:55] <koolhead17> lemme rerun it
[13:55] <koolhead17> :P
[13:59] <koolhead17> niemeyer: am looking at exiting juju charms 4 writing one
[14:00] <niemeyer> koolhead17: That's a great approach
[14:01] <koolhead17> i will update this trunk and need a review on same once am done.
[14:01] <koolhead17> although i also need to work on integrating mysql db in same currently it works with sqlite
[14:04] <niemeyer> koolhead17: That'll be fun
[14:05] <niemeyer> koolhead17: Charms get a lot more exciting once they start to glue things together
[14:05] <koolhead17> niemeyer: i have my charm ready now without mysql :D
[14:05] <koolhead17> its working on my LXC
[14:05] <koolhead17> :D
[14:06]  * koolhead17 is happy
[14:06] <koolhead17> need to know about getting mysql part integrated
[14:11] <niemeyer> koolhead17: Woot
[14:11] <koolhead17> niemeyer: i have a owncloud2 charm running which uses sqlite
[14:11] <koolhead17> :D
[14:14] <koolhead17> SpamapS: suggested me to keep mysql optional
[14:17] <jcastro> owncloud will be a great charm
[14:18] <koolhead17> jcastro: i will have it uploaded once am home, but it will use sqlite by defualt. am working on mysql integration as well. hopefully that will be added in few days too :D
[14:20] <nijaba> hazmat: : Hello. thanks for the pointer to twisted.conch.  do you know if that will support scp and rsync as well?
[14:32] <nijaba> hazmat: the answer is no: "    def execCommand(self, proto, cmd):
[14:32] <nijaba>         raise Exception("no executing commands")"
[14:33] <nijaba> or I guess I would need to implement it
[14:52] <jcastro> koolhead17: that will be great!
[14:52] <jcastro> nijaba: thanks for the review on gitosis!
[14:52] <koolhead17> jcastro: if you will help me with bzr merge issue i will upload the latest working charm at launchpad
[14:52] <koolhead17> :P
[14:53] <nijaba> jcastro: my pleasure
[15:11] <jcastro> niemeyer: random idea for you:
[15:11] <jcastro> we should do a large "juju status juju"
[15:11] <jcastro> we haven't really told anyone what's going on at a macro level since UDS.
[15:12] <jcastro> not changelog-regurgitation level, but more things like "We want to do what we call colocation, it does foo, bar, and baz, and we need it for certain charms to do foo,bar, and baz, and for this and that."
[15:13] <jcastro> "So far so-and-so has finished this part and that part, so we're making good progress there, we expect that to be ready to test in a few months."
[15:15] <koolhead17> jcastro: is there a way one can help in updating juju wiki?
[15:16]  * koolhead17 will upload owncloud2 charm from home
[15:16] <jcastro> I have a work item/rt ticket to sort out the ACLs
[15:43] <robbiew> koolhead17: \o/ on owncloud2...nice
[15:44] <koolhead17> robbiew: yes sir. :P
[15:45] <robbiew> sweet
[15:47] <jcastro> SpamapS: Is there an easy way to see who has submitted which charms?
[15:48] <jcastro> other than just going through the list of course
[15:48] <jcastro> sorry I should specify, is there an easy way to see who has submitted charms that have been accepted into the store
[15:54] <niemeyer> jcastro: That sounds good
[16:08] <jcastro> ok so maybe for this week's team call at the end I'll record it and then everyone can just say what they're working on in a few sentences and then I can write it up
[16:11] <amithkk> How do i make a charm :D
[16:15] <niemeyer> jcastro: It may be tricky to go that way
[16:15] <niemeyer> jcastro: The call will get long and boring, _or_ it won't be enough to give you good contnet
[16:15] <niemeyer> content
[16:15] <niemeyer> jcastro: I suggest email for that
[16:15] <jcastro> ok
[16:16] <jcastro> niemeyer: should I just mail people directly or use the list you think?
[16:17] <niemeyer> jcastro: I suggest mailing the list with your idea, and then building up content somewhere like the wiki
[16:17]  * jcastro nods
[16:21] <koolhead17> so when i say "juju add-relation wordpress mysql" the hook db-relation-changed gets invoked/working for wordpress?
[16:36] <m_3_> koolhead17: yes, it will often get fired multiple times until all the relation-set calls have resolved
[16:39] <koolhead17> m_3_: say i have a charm which by default uses sqllite and for that i have not created ant db-realtion-changed file
[16:40] <koolhead17> now since i have mysql as optional Requires: in my yaml
[16:41] <koolhead17> now what i see is the configuration file gets written once i select either mysql or sqlite via dashboard
[16:45] <m_3_> koolhead17: so I'd maybe do this by specifying sqlite during install and then have the mysql db-relation hooks change this config and restart... (?)
[16:46] <koolhead17> m_3_: got my answer!! :P
[16:46] <koolhead17> this is what i was looking for
[16:46] <m_3_> requiring a config setting first, and _then
[16:47] <m_3_> _ relating is more work
[16:47] <koolhead17> m_3_: i will need your help in sometime. :)
[16:49] <m_3_> koolhead17: sure, just ping me
[16:49] <shazzner_> nijaba: thanks for your feedback on the gitolite bug report
[16:49] <koolhead17> cool
[16:50] <nijaba> shazzner_: my pleasure
[16:56] <nijaba> m_3_: thanks for the vote of confidence :)
[16:58] <nijaba> m_3_: what's the policy about your own charms? wait for someone else's review or bypass?
[17:00] <marcoceppi> nijaba: Wait for review :)
[17:00] <m_3_> nijaba: don't think we have a policy per se... it's a good idea to mark it as 'new-charm' and wait for review
[17:00] <nijaba> marcoceppi, m_3_: ok, sounds very reasonable
[17:35] <mchenetz1> Good afternoon
[17:37] <jelmer> hi mchenetz1
[17:37] <mchenetz> Hi jelmer
[17:59] <koolhead17> hi
[18:00] <koolhead17> if someone has time to review owncloud2 charm https://code.launchpad.net/~koolhead17/charm/oneiric/owncloud2/trunk
[18:00] <koolhead17> it will be good
[18:00] <koolhead17> as of now i am able to get default sqlite working. am working on mysql part as well
[18:01] <m_3_> koolhead17: please tag the corresponding bug with 'new-charm' and relate the branch.  It'll get added to the charm review queue
[18:01] <koolhead17> m_3_: ok
[19:01] <koolhead17> jcastro: got your mail thanks :)
[20:10] <mchenetz> Working on a gccless version of the brew repo and easy_install, will update shortly… Next up Virtualbox provider...
[20:41] <robbiew> jcastro: so what if we took the juju world tour spreadsheet and made a blueprint with workitems on it?
[20:41] <robbiew> or do we already have that?
[20:42] <robbiew> then we can have assignees to each item...knock them out as the go from TODO to DONE
[20:42] <jcastro> robbiew: I have a call with michelle tomorrow hopefully, where I hope to merge that one with the overall list
[20:42] <jcastro> and then we can make WIs into it if you'd like?
[20:42] <jcastro> I plan to have the entire worksheet/list done before break
[20:42] <robbiew> jcastro: just thinking it would be good for external folks to have an idea of where we plan to be...could just wikitize the list too, I suppose
[20:43] <robbiew> cool deal
[20:43] <jcastro> ok I'll make a note to have it in an easily consumable manner
[20:43] <robbiew> blueprinting is probably overkill...K.I.S.S.
[20:43] <robbiew> so...nevermind...I'll let you do your job
[20:43] <robbiew> ;)
[20:44] <mchenetz> What does jcastro do with Ubuntu/juju?
[20:44] <robbiew> EVERYTHING!!!!
[20:44] <robbiew> lol
[20:44] <jcastro> robbiew: I think an easy fix would be a wiki page + adding it to the fridge calendar or something
[20:44] <mchenetz> hehe… I am trying to figure out who does whqt
[20:44] <robbiew> ack
[20:45] <robbiew> mchenetz: well...depends on what you need...;)
[20:45] <jcastro> mchenetz: I'm your cloud community liaison.
[20:45] <robbiew> jcastro: is a good first start for everything ;)
[20:45] <jcastro> but I can't find your nick in the directory?
[20:45] <mchenetz> robbiew: I don't need anything as of yet. :-) I am still just contributing what I can to a project a whole heartedly believe in
[20:45] <jcastro> robbiew: ok I'll make something after I integrate this with michelle
[20:46] <robbiew> mchenetz: amen to that ;)
[20:46] <jcastro> I want to avoid multiple event lists (again)
[20:46] <jcastro> mchenetz: oh dude, you're our soon-to-be-OSX hero!
[20:46] <robbiew> jcastro: ack...multiple lists suck
[20:47] <mchenetz> jcasto: I hope to get a easy install for osx… I am not sure what the end result will be. I think that the "Easy_install" program and/or python setup.py scripts will be the best way. The only piece i need to figure out is how to distribute some precompiled dependendies
[20:48] <mchenetz> I may end up packaging a install for those who do not want package management too..
[20:48] <jcastro> do you happen to know what it needs for something like the OSX store?
[20:48] <jcastro> the main OS store, not the iOS one
[20:49] <mchenetz> jcastro… I can look into that… I don't think it takes too much. I forgot about it actually… :-)
[20:49] <mchenetz> I did some iOS development a while back and i think it is pretty similar in terms of the procedure
[20:49] <mchenetz> hmmm… IOS juju… hehe
[20:49] <mchenetz> Android juju
[20:50] <mchenetz> juju juju
[20:50] <mchenetz> hehe
[20:50] <jcastro> yeah it's just that "Go find it in your OS store" rolls off the tounge better than "check out easy_install yo."
[20:50] <jcastro> whatever keeps EvilBill happy.
[20:50] <mchenetz> your right… Give me a few days… I'll figure it out
[20:51] <mchenetz> THe only reason i like a repo like easy_install or brew is that you can automagically update versions
[20:51] <jcastro> if you get something sort of working, ping me, we can screenshot it and get the word out at least, in that way if you get stuck we'll at least have something
[20:51] <jcastro> <--- your media tool
[20:52] <mchenetz> jcasto: sounds good
[20:53] <mchenetz> right now, my brew repo (I believe) works, along with easy_install… The only thing is… you need Xcode installed
[20:54] <mchenetz> I am not sure if you guys looked at: https://idserver.inventivedigital.com/wiki/pages/W2g0F6q6a/Juju_Brew_Repo_V01.html
[20:55] <robbiew> jcastro: ^ looks like cloud.u.c material to me! ;)
[20:55] <jcastro> oh nice!
[20:56] <jcastro> robbiew: let me wiki this first, so we have one canonical place for OSX people to look
[20:56] <jcastro> mchenetz: who has tried this so far?
[20:57] <mchenetz> Jcastro: I haven't got any feedback yet… I tried it on 3 of my macs and it worked with either method
[20:57] <mchenetz> The easy_install seems to be a little easier thogh
[20:57] <mchenetz> I really would love comment
[20:58] <jcastro> awesome, ok, I can help you there.
[20:58] <jcastro> is that curl from a github gist the right way to install brew?
[20:58] <mchenetz> yes
[20:58] <jcastro> hah, awesome
[21:00] <jcastro> mchenetz: ok I'll post this to the list first
[21:00] <jcastro> ask for some testers
[21:00] <jcastro> then I'll put the word out on cloud.u.c
[21:00] <mchenetz> jcastro: Thanks… Yeah, testing would definitely be good first
[21:01] <mchenetz> Okay, back to working on the virtualbox provider...
[21:03] <jcastro> https://juju.ubuntu.com/OSX
[21:03] <jcastro> how's this look?
[21:03] <jcastro> is easy_install available by default on OSX?
[21:04] <mchenetz> Easy_install is eavaialbe by default
[21:04] <jcastro> ah, but you still need xcode?
[21:04] <jcastro> which one needs xcode installed, both?
[21:05] <mchenetz> yes because, i think, txzookeeper needs to be compiled
[21:05] <mchenetz> they both need Xcode right now
[21:05] <mchenetz> You don't need to do anything… It' just needs to be installed
[21:05] <mchenetz> it looks good except in firefox, the easy_install line on the wiki doesn't wrap for some reason
[21:06] <marcoceppi> mchenetz: Doesn't wrap in Chrome either
[21:06] <jcastro> that's just a sucky wiki
[21:06] <mchenetz> hehe
[21:07] <mchenetz> my default, piece of crap, osx server wiki wraps. :-)
[21:10] <mchenetz> yeah, it doesn't wrap on my new Nexus either. :-) No wrappy
[21:19] <shazzner__> how would it best work for adding a distributed fs relation for gitolite?
[21:19] <shazzner__> if I add a relation, copy the contents of the local repository to the mounted directory?
[21:20] <shazzner__> and if the relation is broken, copy the contents back?
[21:21] <shazzner__> trying to figure out the best way to approach this
[21:31] <m_3_> shazzner__: so your charm uses a particular directory for serving repos..
[21:31] <m_3_> shazzner__: we could use an nfs-client hook to mount that directory from an nfs server (for instance)
[21:31] <shazzner__> yeah by default it creates a repositories folder in the home directory
[21:32] <m_3_> so basically the charm would default to using the local filesystem
[21:32] <shazzner__> yep
[21:33] <m_3_> but then that local filesystem is an nfs mount from the server
[21:33] <shazzner__> oh I see what you mean
[21:33] <m_3_> that would be a little brittle potentially
[21:33] <shazzner__> yeah
[21:33] <m_3_> but would allow you to potentially turn the nfs server into longer-term storage
[21:34] <m_3_> but would also allow for horizontal scaling (if desired)
[21:34] <shazzner__> right
[21:35] <shazzner__> I'm shooting for optional ceph, nfs relations
[21:35] <m_3_> right... that sounds cool
[21:35] <shazzner__> but this cloud scaling stuff is new to me haha
[21:38] <m_3_> I'd recommend making it solid without the distributed filesystem hooks
[21:40] <shazzner__> yeah, that's my first step
[21:40] <m_3_> there are lots of cases where you really want that... and it'd be fun to add in later
[21:40] <shazzner__> it's functional now, but needs some clean up
[21:40] <shazzner__> yeah :)
[21:42] <m_3_> git on a remote mount would probably be pretty slow and not need the horiz scaling that it would enable
[21:42] <shazzner__> then gitweb hooks etc
[21:42] <shazzner__> true
[21:42] <m_3_> never know though... and again, it'd be fun to add in :)
[21:43] <shazzner__> "fun" ;)
[21:44] <jcastro> shazzner__: welcome to #juju, thanks for working on this charm!
[21:46] <shazzner__> hello Jorge, thank you :)
[21:48] <shazzner__> I wonder if gitweb should be an option component to gitolite or a separate charm
[21:49] <jcastro> can you swap out different UIs with the different hosting solution ones?
[21:51] <m_3_> shazzner__: great question... dunno.  it'd probably be easy to add it as a configurable option... but makes sense either way
[21:51] <jcastro> shazzner__: want to do gitourious next? :)
[21:52] <shazzner__> for gitweb all you need is a path
[21:52] <shazzner__> jcastro: haha maybe, I just picked gitolite since I've worked with it before
[22:00] <m_3_> jcastro: should file a bug for osx testing... somebody can pick it up from there
[22:01] <statik> I'm about to test on OSX now
[22:01] <jcastro> m_3_: I will do that, I just want to know if it works on more than one person's machines, then do a proper call for testing
[22:01] <m_3_> cool
[22:02] <jcastro> i've had 2 people ping so far which is good.
[22:02] <jcastro> I just want to make sure it's not totally hosed before exposing it on cloud.u.c
[22:04] <m_3_> yeah, I need to install juju on the wife's machine :)
[22:04] <m_3_> last time I installed stuff didn't go over well tho
[22:05] <jcastro> I learned never to touch her machines unless it's an LTS.
[22:05] <jcastro> :)
[22:06] <jcastro> mchenetz: ok so I'll have one bug for "getting juju working on osx"
[22:07] <jcastro> and then I'll ask people who find bugs to file new ones and tag them "osx", sound like a plan?
[22:10] <nijaba> m_3_ or jcastro or marcoceppi: SpamapS seems to be off today, and I think I should go ahead and fix bug #906030.  Could you please give me a +1 on doing the merge?
[22:11] <marcoceppi> nijaba: Link?
[22:11]  * marcoceppi LAZY MODE ENABLED
[22:11] <nijaba> https://bugs.launchpad.net/charm-tools/+bug/906030
[22:11]  * nijaba was expecting mup to provide the answer...
[22:12] <nijaba> _mup_: hello?
[22:12] <nijaba> niemeyer: is there a problem with mup?
[22:16] <m_3_> nijaba: there was talk about part of it migrating to juju-dev, but it doesn't look to be up there either
[22:16] <m_3_> nijaba: mup, that is
[22:17] <nijaba> _mup_: ok.  I think we would still want the bug part of mup here, at least for charms
[22:17] <nijaba> that was meant for m_3_
[22:18] <m_3_> ha!
[22:18] <marcoceppi> nijaba: +1 from me, everything seems to work here.
[22:19] <nijaba> marcoceppi: thanks
[22:19]  * marcoceppi prepares to merge, m_3_ has about 60 seconds to yell NO!
[22:19] <nijaba> marcoceppi: would'nt mind the pleasure of doing my 1st merge
[22:20] <marcoceppi> Hey! You're in the Charmers group now \o/
[22:20] <marcoceppi> merge away
[22:20] <nijaba> marcoceppi: thanks
[22:20] <m_3_> marcoceppi: haven't run the test suite myself, but it looks fine
[22:20] <marcoceppi> m_3_: Tests were happy here
[22:20] <m_3_> kewl
[22:25] <jcastro> "haven't run the test suite myself, but it looks fine"
[22:26] <jcastro> calibrated eyeball Mark?
[22:27] <nijaba> jcastro: the size of the change is indeed ridiculous
[22:27] <m_3_> jcastro: just read the code in the MP... didn't pull it to test
[22:28] <m_3_> it's a "trivial" as they say in juju core-dev
[22:28] <jcastro> heh
[22:28] <jcastro> marco ran the tests. :p
[22:30] <m_3_> charm-browser parses readme files... woohoo!
[22:30]  * m_3_ work-item: add readmes _everywhere_
[22:31] <jcastro> ooooh when did that land
[22:31] <jcastro> http://charms.kapilt.com/charms/oneiric/roundcube
[22:31] <jcastro> woo!
[22:31] <nijaba> jcastro: last week
[22:32] <nijaba> jcastro: did you do something on limesurvey or do you want me to blog about both?
[22:32] <jcastro> I did limesurvey
[22:32] <jcastro> I need the mail one
[22:32] <nijaba> jcastro: sorry, missed it then :(
[22:33] <jcastro> and I asked Clint to add a part 2 to the limesurvey one to talk about how charm authors can test with haproxy to make sure it all works.
[22:33] <jcastro> http://cloud.ubuntu.com/2011/12/quick-and-easy-surveys-on-the-cloud-with-juju-and-limesurvey/
[22:34] <jcastro> nijaba: I talked to translation and I'll talk to other teams about using it for ubuntu related stuff
[22:34] <jcastro> run your own survey for your ubuntu team sort of thing
[22:34] <nijaba> jcastro: this is what I have been using for the server survey... but I did not have the charm
[22:35] <nijaba> jcastro: nice piece. Thanks
[22:39] <nijaba> marcoceppi: merged done.
[22:39]  * nijaba feels so empowered :P
[22:39] <jcastro> https://juju.ubuntu.com/CharmGuide
[22:39] <jcastro> marcoceppi: ^^
[22:39] <jcastro> might want to mention common functions that new people might need
[22:45] <nijaba> jcastro: nice choice of example :)
[22:46] <nijaba> hazmat: thanks for the great change to the charm-browser, I like it!
[22:48] <koolhead17> do we need charms for mail server like postfix?
[22:50] <nijaba> koolhead17: yes, we do, but it is a tough one to do properly
[22:50] <nijaba> koolhead17: actually, the imap part is the toughest
[22:50] <koolhead17> hmm.  //o.0\\
[22:51] <koolhead17> because most of the CMS and webapps also needs mail server 4 sending user credentials and stuff
[22:52] <nijaba> koolhead17: look at what I did in limesurvey or roundcube
[22:52] <nijaba> koolhead17: for now, let's rely on external ones
[22:52] <koolhead17> nijaba: okey.
[22:53] <koolhead17> my problem is am working on local LXC of mine :(
[22:53] <nijaba> koolhead17: the biggest problem for imap is that it is a tough one to scale
[22:53] <koolhead17> true
[22:54] <nijaba> koolhead17: and you can't send email to any smtp server you want through it?
[22:54] <koolhead17> yes
[22:55] <nijaba> not sure how to interpret your yes.  are you able to or not? sorry
[22:56] <koolhead17> nijaba: yes i got it.
[22:56] <nijaba> k
[22:57] <koolhead17> my concern was not a bare-bone mail server but web applications like drupal/joomla/wordpress and others
[22:57] <koolhead17> which uses postfix simply 4 sending password reset option and others :D
[22:57] <nijaba> sure
[22:58] <koolhead17> nijaba: as you suggested i will check limesurvey charm
[22:59] <nijaba> koolhead17: limesurey only does smtp client.  roundcube does smtp and imap client.
[22:59] <koolhead17> i will only need smtp :)
[23:03] <mchenetz> jcastro: sounds like a plan… I will keep an wye on the bug report
[23:04] <niemeyer> nijaba: Good question
[23:04] <niemeyer> bug #123456
[23:05] <niemeyer> Looks like it's unhappy
[23:05] <koolhead17> also whats magic charm-helper-sh does :)
[23:05] <jcastro> we need a nice convenience charm tool for "webapp needs to send mail" but doesn't need a fullblown SMTP charm
[23:06] <nijaba> jcastro: really?  It's really trivial to implement and will really depend on the implementation of the tool you want to connext
[23:07] <jcastro> I am thinking aloud
[23:08] <koolhead17> jcastro: that is what i was thinking :D
[23:08] <koolhead17> otherwise what we do is apt-get install postfix
[23:09] <koolhead17> that reminds me i have not added mail server configuration 4 owncloud yet :P
[23:16]  * nijaba off to bed.
[23:16] <mchenetz> Jcastro: Just looking at the wiki… Maybe you should mention that those install methods are mutually exclusive. I am just thinking that some people might run all instructions down the page...
[23:19] <koolhead17> jcastro: just pull everything from here http://askubuntu.com/questions/65359/how-do-i-configure-juju-for-local-usage/65360#65360 in doc for LXC
[23:19] <jcastro> mchenetz: good idea on it.
[23:20] <koolhead17> let me know if you need any help with documentation. Also in charms separate revision file needs to be created instead putting the same inside the yaml
[23:20] <koolhead17> charms example
[23:21]  * koolhead17 off to bed
[23:21] <jcastro> I am hoping for the official docs to be more contributable soon
[23:21] <jcastro> but I need to catch up with hazmat on that
[23:21] <koolhead17> jcastro: just let me know how can i help :)
[23:22] <jcastro> statik: thanks for your detailed analysis