Chef

If you need to file an issue against another Chef project, you can find a list of projects and where to file issues in the community contributions section of the Chef docs. We use GitHub issues to track bugs and feature requests. If you need help please post to our Mailing List or join the Chef Community Slack. This repository contains the core services that make up the Chef Infra Server. The quickest way to get a Chef Infra Server development environment is to follow the instructions in the dev directory. This environment is based on Vagrant and features hot reloading of code. You can build a Chef Infra Server package locally with HashiCorp Vagrant and Test Kitchen. Once the build is complete, the package should be in omnibus/pkg. By default the dev-build target will create an Ubuntu 18.04 build. A top-level docker-compose.yml file exists for running Chef Infra Server from Habitized Docker images: knife-ec-backup, used to backup your Chef Infra Server for disaster recovery or migrations. knife-opc, used to provide administrative command-line control to the Chef Infra Server from the console If you're looking to contribute to certain parts of the Chef Infra Server, familiarity with the following related tools is also beneficial, depending on the area. The chef/chef-server repository, like many other Chef Software repositories, leverages an internal utility called Chef Expeditor to create a pub-sub model of actions across our various CI/CD utilities.