> On Mar 11, 2015, at 8:32 PM, Hubert Lubaczewski <dep...@gmail.com> wrote:
>
> Hi,
>
> I'm trying to learn puppet by using it on a test machine I have. Figured that
> for single server, it makes sense to use master-less mode.
>
> So, my question is like this. To set it up, I figured that:
> 1. /etc/puppet would be clone of some repo
> 2. in /etc/puppet/manifests/site.pp, I would add vcsrepo{} that would make
> sure that puppet will update itself on each run
> 3. I'll add a cronjob to periodically run "puppet apply
> /etc/puppet/manifests/site.pp"
>
> Optionally, I would run "git pull" before actual puppet apply, so that puppet
> will run on already updated repo.
>
> Does it make sense? Am I missing something? I know it's pretty basic, but in
> one place I had to write quite a lot of manifests/modules for puppet, and
> finally decided to setup whole machine, on my own, using puppet.
>
> Thanks for any help/guidance,
>
> depesz
>
I've used masterless puppet setups for several years.
My current starter template for puppet projects is at
https://github.com/declaresub/git-puppet-bootstrap . It may be useful for what
you want to do. It is intended for use with VMs; I've tested it with Ubuntu
12.04 and Debian Wheezy on Linode and Vagrant VMs.
I have a simple puppet module for postgresql if you need one too :)
Charles
--
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/600A56EB-E62D-479F-8A52-5E81691A54DC%40dakim.com.
For more options, visit https://groups.google.com/d/optout.
