> I manage a web/mail/dns server for my own small business and so far
> maintained the test and production servers by hand, keeping config files
> under cvs and using scp to copy them to the servers. Looking for a
> better way to do this (prompted by the more and more tedious work to do
> when upgrading the OS on a server and the planned hardware replacement)
> I stumbled upon puppet and so far this seems like the best solution.
> What won me over was the excellent tutorials
> <http://docs.puppetlabs.com/learning/>.
> I am now trying to figure out the best way to organize my work, and I
> need help from the experts, as I did not find any info on these
> questions of workflow setup.
> I don't think the 'tutorial' way of editing files directly under
> /etc/puppet/{manifests,modules} is recommended for real work; I want to
> use another directory, which I can also mount on my workstation, for
> editing the files.
> There is the 'confdir' setting, but it affects more than what I consider
> the 'data' part of the layout (manifests, modules, nodes, ....) so I am
> considering this setup in /etc/puppet/puppet.conf:
>     $datadir = "/some/fs/puppet"
>     manifestdir = "$datadir/manifests"
>     modulepath =
> "$datadir/modules:$confdir/modules:/usr/share/puppet/modules"
> except that it is not possible to define variables in config files, but
> this works fine:
>     manifestdir = "/some/fs/puppet/manifests"
>     modulepath =
> "/some/fs/puppet/modules:$confdir/modules:/usr/share/puppet/modules"
> 
> so everything puppet-internal is still in /etc/puppet, and I can hack
> away (under CVS control) at the files under /some/fs/puppet.

I have all my manifests and modules stored in a GIT repository. I'm
working with the files in my /home, and I have a Rakefile with a
"deploy" target defined. So typing "rake deploy" will push the local
repo to the central server and login to the puppetmaster via SSH and
pull the latest files from the central server.

The only thing I haven't figured out yet is what to do with sensible
files (private keys etc) that I want managed by puppet. Somehow, having
those in the repo doesn't seem nice to me. Any recommendations?

Cheers, Andreas.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to