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 
harder to read the more you need to configure). In the modules itself? Or 
do you have to write modules which will start those modules?

Op vrijdag 20 december 2013 19:04:33 UTC+1 schreef Christopher Wood:
>
> 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 -0800, Peter Nijssen wrote: 
> >    Hi, 
> >    I started to use vagrant with [1]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 the puppet forge etc 
> etc. 
> >    Now I need to configure those parts like which mods enabled for 
> apache. 
> >    Which vhost files. etc. 
> >    Everything is done in the main manifest file called site.pp. However, 
> I 
> >    was wondering, does it really has to become one gigantic file? 
> >    Isn't it somehow better to split up? I noticed I can split up using 
> >    "import", but it's not really good practice apparently. 
> >    I guess it's neither a good practice to somehow write it down in the 
> >    modules itself.  
> >    Or isn't it really common to use existing modules and just write your 
> own? 
> >    If I look around at github for default boxes, I see a lot of people 
> who 
> >    all wrote the apache part on their own for example. 
> >    Or do I have to write my own module, which splits everything up in 
> >    classes. 
> >    Basically what I want to achieve is that I seperate files where I can 
> >    configure apache, php, mysql etc etc. Or to hear what actually is 
> best 
> >    practice. I am only going to use it for one OS, so it doesn't have to 
> take 
> >    a lot of OS'es into account. 
> >    Thanks! 
> >    Peter 
> > 
> >    -- 
> >    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...@googlegroups.com <javascript:>. 
> >    To view this discussion on the web visit 
> >    [2]
> https://groups.google.com/d/msgid/puppet-users/9b216ae5-b811-46ce-a869-778d07d49717%40googlegroups.com.
>  
>
> >    For more options, visit [3]https://groups.google.com/groups/opt_out. 
> > 
> > References 
> > 
> >    Visible links 
> >    1. https://puphpet.com/ 
> >    2. 
> https://groups.google.com/d/msgid/puppet-users/9b216ae5-b811-46ce-a869-778d07d49717%40googlegroups.com
>  
> >    3. https://groups.google.com/groups/opt_out 
>

-- 
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/5c62d2f8-812a-4975-9337-8e45bdcf211d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to