\- **Chef server** - This is the central part of the product, and it is the place where the configuration data is stored. \- **Nodes** - A node can be anything from a physical machine, a virtual one, a network device that is managed by **Chef** Some of **Chef**'s essential components are: It uses a pure-Ruby, domain-specific language (DSL) for writing system configuration "recipes"." The definition on official website reads: "Chef is a configuration management tool written in Ruby and Erlang. There are many configuration management tools to configure applications across environments and one of them is *Chef*. Some of this information is not available for all the people involved in the development process, because they should not care about it either.
For example, the information contained in a database URL will be different than that of a URL used in the development stage, which is obviously different than the one used in production. Moreover, they have to be consistent across the development, the QA and the production stages, and point out to the information relevant at each stage. The applications and the operating system can each have different, possible configurations to fit the environment they are deployed in. However, the maintenance and scaling process/part of such apps can be quite challenging sometimes. Building large scale applications is a very rewarding thing.
0 kommentar(er)
