On 05/16/2014 01:53 AM, Matthias Saou wrote:
> On Fri, 16 May 2014 07:28:23 +0200
> David Schmitt <da...@dasz.at> wrote:
> 
>> easy solution: create a local site module (e.g. "matthew") an put
>> every thing there. Manage it like all other modules. I did that at > 
>> https://github.com/DavidS/dasz-configuration/tree/master/modules/dasz
>> and never looked back.
> 

Yeah, I didn't really want to hear that =/. I love puppet (coming from ansible)
because it's amazingly expressive. Forcing me to standardize on a 'site' module
makes everything a little less expressive IMO. And I get the feeling that the
reasoning behind forcing everything to modules is just to keep the code base a
/tiny/ bit simpler.

> I second that! And it's also quite easy to separate modules that are
> managed by puppet (or librarian, or r10k, or...) from those which would
> be "custom" ones, from a private VCS for instance, into different
> "modulepath" directories.
> 

I do this already. I keep my stuff in $confdir/modules and upstream stuff from
the forge in $confdir/.modules. I have a file .puppet-modules which lists the
upstream modules and a git post-receive hook on my master for
installing/upgrading modules in .modules.

> I have this in my [master] (puppet 3.4) :
> 
> manifest = $confdir/environments/$environment/manifests/site.pp

I don't know about 3.4, but in 3.5 and 3.6 you don't need site.pp, just point to
the manifests directory itself. Furthermore, I think that's the default anyway,
so no need to specify it.

> modulepath = 
> $confdir/environments/$environment/modules:$confdir/environments/$environment/site
> 
> With r10k and git branch mapping to $environment, with the "site"
> modules managed inside git alongside the Puppetfile, you'll never look
> back :-)
> 
> With these tools, hiera and/or an ENC, nowadays it's very easy to have
> an empty site.pp and no (or empty) node blocks. All nice 'n clean ;-)
> 
> Also, if you might move manifests between custom modules, I'd suggest
> you use the $module_path variable in file source parameters and
> template paths to make your life easier.
> 
> HTH,
> Matthias
> 

Thanks!

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to