Hello,
I like Nigel's response better -
Regards,
-Roy
On 6/16/10 10:02 AM, Nigel Kersten wrote:
On Wed, Jun 16, 2010 at 8:56 AM, Stefan Schlesinger wrote:
Hello folks!
Since you cannot include modules twice, or overwrite anything
within a namespace, I'm looking for a way to orga
On Wed, Jun 16, 2010 at 8:56 AM, Stefan Schlesinger wrote:
> Hello folks!
>
> Since you cannot include modules twice, or overwrite anything
> within a namespace, I'm looking for a way to organize my modules.
>
> I initially started to create the following structure, which
> will avoi
Hello,
You might consider having an "ono" environment, and "webserver" and
"mailserver" modules...
Regards,
-Roy
On 6/16/10 9:56 AM, Stefan Schlesinger wrote:
Hello folks!
Since you cannot include modules twice, or overwrite anything
within a namespace, I'm looking for a way to orga
Hello folks!
Since you cannot include modules twice, or overwrite anything
within a namespace, I'm looking for a way to organize my modules.
I initially started to create the following structure, which
will avoid storing redundant configuration in your manifests:
node server01.o
Hi
Our team is providing Linux servers to different departments in our
company. We want to change our configuration management tool and use
puppet in the future. I read the book “Pulling Strings with Puppet”
and the documentation on the puppet webpage.
When I understood correctly, the way to go
