CINC Is Not Chef

bognition wrote: post #5

arm32 wrote: post #3

I'm dumb and can't figure out wtf this is.

Chef is an infrastructure as code configuration system. The binaries are now proprietary. This is a FOSS replacement.

Huh. Given Ruby/Chef lost, are the Chef maintainers going for a final financial squeeze of whoever is still on the platform?

Re: CINC Is Not Chef

#7

Post by slipheen » Fri, Apr 04, 2025, 6:06 PM UTC

arm32 wrote: post #3

I'm dumb and can't figure out wtf this is.

A few years ago, Chef (configuration software, sort of like ansible) changed their license, and this is a fork which maintains the open source.

Re: CINC Is Not Chef

#8

Post by jonathaneunice » Fri, Apr 04, 2025, 6:09 PM UTC

2013 called and wants its favorite infrastructure as code (IaC) tool back.

Re: CINC Is Not Chef

#9

Post by slipheen » Fri, Apr 04, 2025, 6:10 PM UTC

0cf8612b2e1e wrote: post #6

bognition wrote: post #5

Earlier quoted context omitted.

Chef is an infrastructure as code configuration system. The binaries are now proprietary. This is a FOSS replacement.

Huh. Given Ruby/Chef lost, are the Chef maintainers going for a final financial squeeze of whoever is still on the platform?

I think the license change and initial fork was back in 2019? It's been a while.

Re: CINC Is Not Chef

#10

Post by holysoles » Fri, Apr 04, 2025, 6:13 PM UTC

lgeorget wrote: post #4

klooney wrote: post #2

Are there Chef Habitat users in the wild?

Are we talking about the orchestration software, like Ansible and Puppet, or is it something else?

Its a variant of the orchestration software. I'm not sure this is as enticing as other permissive licensed projects like OpenTofu/Ansible (push) or OpenVox (pull) based on available documentation/market share.

Of note, this is not affiliated with Chef itself [1], but looks like Chef has blessed it [2]

[1] https://cinc.sh/disclaimers/ [2] https://cinc.sh/blog/cinc_client_is_live/