My rationale for it is exactly that. Focus on learning how Puppet itself
works, and then learn the add-ons after the fact. On top of that, Hiera
isn't a requirement for use - you can just as easily use something like
Foreman (which, from what I've seen of it so far looks really good.) But
even in m
Well, so I didn't know if it was "good form" to modify modules to hold
site-specific configuration items.
I think part of my frustration is that I haven't been able to find a doc,
or maybe one doesn't exist, that shows what a decent "production" Puppet
environment might look like. I think it'd be
Ah, okay this makes more sense for me. So I know that I can stick this in
the same file with the node definitions, but there's got to be a better
place for it to go. Where would the "proper" place be for it to go?
Many thanks for your responses. They've been very helpful.
On Sun, Jun 22, 2014 at
Thanks for the answer. I grasp the fundamentals of what you're saying, but
right now I'm a little leery of delving into Hiera when I don't really know
the fundamentals of Puppet itself yet. My reading through those docs would
only confuse me more. (Not that those docs are probably not good - it'
Alright, this is definitely a Puppet 101 question, and I am sure that the
Puppet docs have an answer for this and I am just dense and can't find it.
I'm trying to teach myself Puppet, with the goal of managing the VPS I run
with it. Additionally, when I get a better grasp on things, I want to
