5 | | With puppet, we can write a collection of puppet configuration files (aka manifests), including specific instructions for each server in our network. Typically, these configuration files are kept in a revision control system like git. puppet runs on each server, reads the configuration files, develops a catalog of all instructions intended for the server on which it is running, and then it executes that catalog, applying all the directions. |
| 5 | We've borrowed and written a collection of puppet configuration files (aka manifests) that define how all of our servers should be configured. |
| 6 | |
| 7 | These configuration files are kept in our [https://git.mayfirst.org/?p=mfpl/puppet.git;a=summary git repository]. Through a cron job, each server updates to the most recent git tag and then launches puppet, which reads the configuration files, develops a catalog of all instructions intended for the server on which it is running, and then it executes that catalog, applying all the directions. |