On Wednesday, November 20, 2013, Mark Shuttleworth wrote: > On 20/11/13 12:06, Ramez Hanna wrote: > > I noticed there is a bug open for a charm for trac > > so i started working on it, to conytribute to charms and learn more > > about juju > > I would be glad if someone would help me out with requirements for the > > deployment of trac > > I am an experieced sys admin > > I use ansible extensively and can code in python as well > > my initial attempt at trac is here > > https://github.com/InformatiQ/charm-trac > > any guidelines or requirements or best practices for production level > > charms are most welcome > > > > Thank you Ramez, this is very welcome! It would be interesting to see > whether you can integrate ansible into the charm in a useful way. We > have some precedent (I think in charm-helpers) for making it easy to use > other config systems like puppet and chef, exposing juju data in ways > that chef-solo can take advantage of, for example. > > Mark > I was able to ise charmhelpers to get basic trac charm working I actually found and fixed a bug in it Wuth ansible and puppet and the like juju gains a lot of traction Ansible is great but the inventory mgmnt is not that good as juju
Deployment of trac can have so many optiins and i was hoping for some guidance on what should i expose and what i shouldn't -- BR RH http://informatiq.org
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
