On Jul 5, 2010, at 8:20 AM, Dan Carley wrote:
> On 5 July 2010 15:11, Thomas Bellman <[email protected]> wrote:
> On 2010-07-03, Jeff McCune wrote:
>
> > In this module, if you use the following orginization puppet will
> > autoload everything:
> >
> > manifests/init.pp contains class apache { }
> > manifests/disable.pp contains class apache::disable inherits apache {}
> > manifests/virtualhost.pp contains define apache::virtualhost(){}
>
> Yuck! Forcing each class or define into its own file sucks royally.
> No sane person wants their code organized like that.
>
> Really? I find it a much more manageable way to work, rather than wading
> through lines of `init.pp` to find the relevant class or maintaining lists of
> slightly artificially named `import` statements. It also provides some more
> reliable behaviour with regards to caching of compilation failures.
I usually put some of the really small classes in init.pp. For instance, do
you put your packages classes in their own file?
class apache::package {
package { apache2: ensure => present }
}
Would you put this in it's own file?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
