Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I would like to have a master puppet server for each of my physical locations. However, I don't want to have to maintain them separately. Is there a good model/method for this with puppet?

share|improve this question
"separately" from what? – womble Jul 29 '11 at 0:23

You should put /etc/puppet/config into a source code repository such as Subversion or git. Then on cron, just update /etc/puppet/config with the latest from the repository. You can then check in a change into your code repo and with your next cron run on each puppet master, you'll be updated.

This has the added benefit of having your puppet configuration tracked so you can see who/what/when changes were made.

share|improve this answer
Actually this would be better to tie into a svn or git (please use git it's so much nicer) hook that pushes the update to both hosts – Tacticus Oct 26 '11 at 22:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.