Date: Wed, 2 May 2012 15:44:26 +0100 From: Kaya Saman <kayasaman@gmail.com> To: glarkin@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Re: Puppet port - Dashboard guide or config reference Message-ID: <CAPj0R5KU%2BOK9sXUj7XPNQRnLWt%2BrJ96XQ4RinbmHTjfT7XqaAg@mail.gmail.com> In-Reply-To: <4FA14375.2090106@FreeBSD.org> References: <CAPj0R5KRQ8dSoLgH=RTprPEDEHKWVBmqz5TMhkiODUCZw3e-vw@mail.gmail.com> <4FA14375.2090106@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks a lot Greg, I have actually just found the link for myself! I would be very happy to share notes with you with regards to Puppet or anything else for that matter as I'm trying to get my company to go FreeBSD in favor of CentOS Linux. Soon when I am better setup I hope to even mirror FreeBSD at home as I have quite a substantial server infrastructure resting in my living room (mostly FreeBSD based). Also with the addition of 1Gbps fiber internet in 3 years for London/UK things should be fenominal. Regards, Kaya On Wed, May 2, 2012 at 3:23 PM, Greg Larkin <glarkin@freebsd.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 5/2/12 10:06 AM, Kaya Saman wrote: >> Hi, >> >> I've managed to get Puppet up and running on FreeBSD 8.2 which I >> built from ports.... however, I am having difficulty in finding >> documentation on how to get the Dashboard up and running. >> >> I am totally new to Puppet though not to FreeBSD, so I've managed >> to hack through quite a bit already and got basic functionality - >> my test client syncs up! woohoo :-) >> >> Can anyone give me a hand or a hint as to where a good Doc on the >> web gui is:? Unfortunately the puppetlabs site isn't much help in >> that respect (unless I missed it?). >> >> Regards, Kaya > > > Hello Kaya, > > What a coincidence - I recently installed Puppet Dashboard on a > FreeBSD machine here as part of a Puppet deployment, and I have an > item on my list to add it to the ports tree in the near future. =A0I > used the following link to help me get it running: > http://docs.puppetlabs.com/dashboard/manual/1.2/index.html > > It was reasonably difficult for a non-Ruby-fluent person like me to > get the dashboard running, though. =A0I had a lot of problems with the > Ruby bits packaged with the dashboard ("vendors" directory) > conflicting with ports I already had installed, and I eventually > manually installed some specific versions of required gems. =A0I hope > there's a way to use the ports tree to install the correct > dependencies, and I'll figure that out as I get into the port development= . > > If you want to exchange tips, ideas, roadblocks, etc. for implementing > Puppet scripts on FreeBSD, I would be happy to do that. =A0We already > ran into one tricky problem: > > - - Spamassassin creates a virtual package when it updates its rules. > Puppet can't deal with that because the package has no origin. =A0We > eventually figured out that we need to invoke the sa-compile script > like so to prevent the package creation: env DISABLE_BSDPAN=3D1 sa-compil= e > > Hope that helps, > Greg > - -- > Greg Larkin > > http://www.FreeBSD.org/ =A0 =A0 =A0 =A0 =A0 - The Power To Serve > http://www.sourcehosting.net/ =A0 =A0 - Ready. Set. Code. > http://twitter.com/cpucycle/ =A0 =A0 =A0- Follow you, follow me > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEUEARECAAYFAk+hQ3UACgkQ0sRouByUApDBdgCffLQ1AA/Exa3fLypk9sw4Y12D > +8QAmJEJVgswZ4ZQ8WxGE6HYPr1lv1c=3D > =3DX9z8 > -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPj0R5KU%2BOK9sXUj7XPNQRnLWt%2BrJ96XQ4RinbmHTjfT7XqaAg>