On Jun 5, 2010, at 5:06 AM, Henning Sprang wrote:
> On Sat, Jun 5, 2010 at 12:15 AM, Julian Simpson
> wrote:
>> Try adding a --modulepath to the puppet command line. You may need to tweak
>> your manifests: make sure that file urls are of the form
>> puppet:///some/path.
>
> Thanks!
>
> But
>
> Actually, only this last thing (and that was what I wanted to do
> first) is what really requires to set the confdir explicitly, like
>
> cd /path/to/puppet/dir/manifests
>
> puppet --confdir /path/to/puppet/dir site.pp
>
> or without cd'ing in the manifests dir:
>
> puppet --confdir /path/to
On Sat, Jun 5, 2010 at 2:06 PM, Henning Sprang wrote:
> Now I'm checking if I even could run that somehow if the
> manifests/modules/... structure is somewhere else, e.g. on an nfs
> mount.
Actually, only this last thing (and that was what I wanted to do
first) is what really requires to set the
On Sat, Jun 5, 2010 at 12:15 AM, Julian Simpson wrote:
> Try adding a --modulepath to the puppet command line. You may need to tweak
> your manifests: make sure that file urls are of the form
> puppet:///some/path.
Thanks!
But somehow I felt that wasn't what I was doing back then and searched
a
When I run "puppet /etc/manifests/site.pp" I get onloy import errors.
When I run puppetd it only complains that it cannot access any server.
Try adding a --modulepath to the puppet command line. You may need to
tweak your manifests: make sure that file urls are of the form
puppet:///some
Hi,
I'm pretty sure I once did some experiments with running puppet
wihtout a puppertmasterd - but having a "normal" puppet manifests and
modules structure in /etc/puppet.
Sadly, I can't find how to do that anymore.
I know I can write plain puppet instructions in a file.pp and run them
plainly -
