- From: David Balatero <dbalatero@gmail.com>
- To: chef@lists.opscode.com
- Subject: Re: Typical use of chef
- Date: Tue, 28 Apr 2009 09:23:05 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SCfG8JJUxMzknzha3iqvuDsj72S2rL3VjWW8gZvRI1PLdfk3LtNfPhx3UDcD/sfG0l IYbSdPLdNF+0XqWKpiCU/1gte2QAp3NHRy8uGAxwx59bP1w43Puia+yAwnXnmeKkWBc5 +4HZq7v68iKGfta8+riN7bPlHwyo2E70/ns4g=
You might be, but you seem to have a just as valid reason to use Chef as anyone else :)
There are probably so many Ruby shops involved simply because Chef is implemented on top of Ruby, and thus is easy for everyone to understand / debug / maintain.
On Tue, Apr 28, 2009 at 9:18 AM, Miguel Cabeça
<cabeca@ist.utl.pt> wrote:
Hi,
I was just wondering what is the typical use of chef for the users in this mailing list. It seems to me that the majority of chef's users are ruby shops, or otherwise web/lb/db companies with a hosting or cloud infrastructure.
Am I alone in using chef as a configuration tool for any type of server (mail, ldap, kerberos, gateway, router) or workstation in an academic scenario?
Best Regards
Miguel Cabeça
Archive powered by MHonArc 2.6.16.