- From: Noah Kantrowitz <
>
- To:
- Subject: [chef] Re: Extending Opscode Chef server
- Date: Mon, 29 Jul 2013 17:49:44 -0700
On Jul 29, 2013, at 5:40 PM, DV wrote:
>
Hello everyone,
>
>
I am looking to add extra functionality to our Chef server to suit our
>
needs - things like a different authentication backend, restrictions on
>
node naming, better activity logging / change notification, perhaps an
>
integration with version control system, and a bunch of other miscellaneous
>
requirements. Some of these should be done on the server side rather than
>
client side to enforce compliance.
>
>
I tried searching for any documents on extending Chef server but couldn't
>
find any. Is this something that's never been done before? Can someone
>
familiar with Chef server architecture point me in the right direction on
>
where I'd start?
You will most certainly have to just read the erchef code, this is well
outside the realm of things we document. You can try asking for help in #chef
as you go, but most of the erchef team doesn't hang out on IRC.
--Noah
Archive powered by MHonArc 2.6.16.