This category will be used for general announcements that have impact across all of Progress Chef and/or topics that are relevant to all of our released products.

Chef Infra Client is an agent that runs locally on every node that is under management by Chef Infra. These nodes may or may not be under management by Chef Infra Server. When Chef Infra Client runs, it will bring the node into the expected state and prevent configuration drift.

The Chef Infra Server acts as a hub for configuration data. The Chef Infra Server stores cookbooks, the policies that are applied to nodes, and the metadata that describes each registered node that is under management by Chef Infra Client. Individual nodes then use Chef Infra Client to ask the Chef Infra Server for configuration details, such as recipes, templates, and file distributions.

Chef Workstation is Chef's modern developer tool kit that includes Chef Infra Client, InSpec, and Habitat plus a host of resources, helpers, and testing tools that make automating infrastructure, application, and security testing easier than ever. With Chef Workstation DevOps automators can create, test, and deliver codified artifacts all within their preferred developer environment.

Chef Infra is an infrastructure configuration engine for modern software-driven organizations to ensure every system is configured correctly, consistently and automatically.

Chef InSpec leverages an open-source framework for testing and auditing applications and infrastructure. Chef InSpec compares the actual state of a system with the desired state that is expressed in easy-to-read and easy-to-write code.

Use this category to discuss all things related to Chef Automate!

Chef Habitat is an automation framework that centers application configuration, management, and behavior around the application itself, not the infrastructure that the app runs on.

The majority of discussions related to using the Habitat framework happen here. Thread content frequently consists of support or general use questions.

This category is used by the the Habitat core-team to communicate important announcements to the community.

This category can be used to share development documentation related to contributing to, or operating the Habitat project and tools. All posts in this category should be converted to a “wiki” post.

This category is a place to talk about anything related to the Habitat community organization. You can use this to ask questions, organize or discuss events, or anything that’s not necessarily just about the use of the Habitat framework.

Every week we hold text-based meetings in the #community-meetings room of Chef's community slack. The notes for those meetings are posted here!

Discussion about this site, its organization, how it works, and how we can improve it.

This category is intended for all habitat development discussions whether you’ve got a rust-lang question or need help in contributing to a component, this is the place.

This category is used to announce releases of Chef software and other projects related to Chef. Only Chef Staff and project maintainers can post in this category. All discussion related to the announcements should be posted in other categories. Release announcements will include information such as the list of new features, bug fixes, errata, contributor recognition, etc. Release announcements may also contain some brief feature descriptions, but in-depth feature spotlights will be posted on the Chef blog.