[Puppet Users] One big manifest?

Hi, I started to use vagrant with puphpet . Very nice. However, the gui of puphpet gives me too few options, so I want to configure everything myself. So, I decided to write everything from scratch, using modules. Modules like apache, mysql, php, phpmyadmin which are in th

Re: [Puppet Users] One big manifest?

Looks like you might want to start here: http://docs.puppetlabs.com/puppet/latest/reference/modules_fundamentals.html Also check up on how to do hiera lookups from within puppet3. Other than that, structuring your modules tends to be a bit site-dependent. On Fri, Dec 20, 2013 at 08:38:03AM -080

Re: [Puppet Users] One big manifest?

I read that document, however, it doesn't provide me the answer. Should I write, in general, my own modules? Or should I use predefined modules? And I if use predefined modules, should the configuration of those modules happen all in site.pp? (Which sounds me like a big file which is getting ha

Re: [Puppet Users] One big manifest?

This is just a question with so many answers. have you tried the puppet enterprise quick start guide ? It is a good way to learn the concepts and get you started quickly. Get in touch with local puppet users. Looks to me you are dutch speaking, so get in touch with the dutch or belgian puppet

Re: [Puppet Users] One big manifest?

Thanks for your answer. I've only been a week now in the world of puppet. I started to use it, because I am charmed with the puppet + vagrant combination as a developer. Also, we currently are managing a growing number of servers by hand and I believe puppet can be a nice answer to keep everythi

Re: [Puppet Users] One big manifest?

--- Original message From: Peter Nijssen Date: 2013/12/21 08:00 (GMT-05:00) To: puppet-users@googlegroups.com Subject: Re: [Puppet Users] One big manifest? Thanks for your answer. I've only been a week now in the world of puppet. I started to use it, because I am charmed wi

Re: [Puppet Users] One big manifest?

Hi Peter, Your instinct is correct. Just like many programming languages that allow you to keep all of your code in one file (or one function, even), it's not a good idea. As you mentioned, you can use import to pull in other files, but the better solution is to use puppet's autoloading func

Re: [Puppet Users] One big manifest?

; > Sent from my Verizon Wireless 4G LTE smartphone > > > > ---- Original message > From: Peter Nijssen > > Date: 2013/12/21 08:00 (GMT-05:00) > To: puppet...@googlegroups.com > Subject: Re: [Puppet Users] One big manifest? > > > Thanks fo

Re: [Puppet Users] One big manifest?

Hi Chad, Greet to hear that my instinct was correct. As noted in the docs of puppet, using import is not recommended. So that's why I didn't want to use that either. So basically my configuration should be in modules. That was basically my biggest "problem". Let's say I use a apache module from