Am 30.03.2016 um 07:07 schrieb Alex Samad:
> So I am thinking I need a puppet servers. all the linux boxes need
> access to this server on port 80 & 443
No. Puppet server listens on port 8140.
> My first task is to standardize the standard username's GID/UID used.
> currently there is a script t
Hi
I am just about finished running through the tutorial.
I am planing ahead for rolling out puppet to manage my linux servers.
So I am thinking I need a puppet servers. all the linux boxes need access
to this server on port 80 & 443
My first task is to standardize the standard username's GID
On 3/28/16 12:44 PM, Sans wrote:
Hi there,
I'm setting up a multi-tenancy WordPress environment, where multiple
sites are structured as: /var/www/. Long story short: I want
to put a line in the wp-config.php based on existences of a file in
wp-content (under each site_location, provided by my us
On 29/03/16 12:40, Sans wrote:
Hi Trevor,
I don't think "Templates" are technically executed on the Master -
that's for the client/agents. The asset(s) we define in the template has
to native to the agent. You can say everything gets complied on the
master. Correct me, if I'm wrong.
ERB (as w
> Notice: /Stage[main]/Ssh/Ssh_authorized_key[admin]/ensure: created
> Debug: Creating /home/admin/.ssh
> Error: /Stage[main]/Ssh/Ssh_authorized_key[admin]: Could not evaluate: No
such file > or directory - /home/admin/.ssh
Well, does the directory /home/admin/.ssh exist?
--
Lowe Schmidt | +46 72
Hi,
I am using # puppet-module-ssh
In the yaml file I have:
ssh::keys:
admin:
ensure: present
user: admin
type: dsa
key: ...==
But when running puppet agent I get:
Notice: /Stage[main]/Ssh/Ssh_authorized_key[admin]/ensure: created
Debug: Creating /home/admin/.ssh
Error: /
On 29 Mar 2016, at 13:47, Rohit Sharma wrote:
> Hi Team,
>
> By default when we install foreman puppet-master running/listen agent request
> on 8140, but I need to it on 443 only
AFAIK foreman listens on 443.
Why do you want to move away from 8140?
puppet config print | grep 8140
You need to
Ok, thank you.
EmAr.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https:
Can you specify what your manifest looks like? Yes
scheduled_task { $titulo_tarea_mantenimiento:
ensure => present,
enabled => true,
command => $lineaComandos,
user => $usuario,
password => $contrasena,
arguments => $parametros_mantenimiento,
trigger => {
schedule => da
Hi tell me the location of file, I want change all communication held on
443 rather then 8140.
On Friday, December 20, 2013 at 7:44:08 PM UTC+5:30, Ramin K wrote:
>
> On 12/20/2013 6:05 AM, Alex wrote:
> > Hi,
> >
> > we want to migrate our puppet master to run on 443 rather than on 8140.
> >
Hi Team,
By default when we install foreman puppet-master running/listen agent
request on 8140, but I need to it on 443 only
Can any one help me out to configure puppet master over 443 than 8140.
Please tell me the detailed step.
Thanks in advanced
Regards
Rohit
--
You received this message
Hi Trevor,
I don't think "Templates" are technically executed on the Master - that's
for the client/agents. The asset(s) we define in the template has to native
to the agent. You can say everything gets complied on the master. Correct
me, if I'm wrong.
w.r.t. custom-fact, as I said, it cannot
Hi Trevor,
I don't think "Templates" are technically executed on the Master - that's
for the client/agents. The asset(s) we define in the template has to native
to the agent. You can say everything gets complied on the master. Correct
me, if I'm wrong.
w.r.t. custom-fact, as I said, it cannot
Hi San,
Templates are executed on the master and so it will be checking the
existence on the master as written.
You'll need to write a custom fact (they're easy)
https://docs.puppetlabs.com/facter/3.1/custom_facts.html. Something like a
boolean 'has_wp_extra_config' would be ideal.
Then, in your
14 matches
Mail list logo
