Hi, i would like to complete the disks fact with information about scsi
port. So, I have this custom fact:
> Facter.add(:disks, :type => :aggregate) do
> chunk(:scsiports) do
> disks = {}
> Facter.value(:disks).each do |disk, values|
> disks[disk] = {
> 'scsiport' => Fact
Ok, I was missing the following line in the nginx location statement:
uwsgi_modifier1 7;
Now seems that works correctly (and very fast). When thoroughly adjusted I
will publish the complete configuration. Thanks again.
El miércoles, 3 de octubre de 2012 16:40:28 UTC+2, Juan José Presa Rodal
Hi, I'm trying to configure distributed Puppet with uWSGI server
application without success.
I'm configuring NGINX in a similar way that with Unicorn or Passenger and
also inspiring in this blog entry:
http://www.prontab.com/2011/01/this-page-should-outline-how-to-set-up.html
¿Anybody has exp
e puppet to always update the package to the latest version.
>
> To prevent that, always refer to specific package name, eg.
> linux-headers-2.6.32-41-server , not metapackage linux-headers-server
>
>
> 2012/4/25 Juan José Presa Rodal
>
>> Hi, I've defined this module
Hi, I've defined this module:
package {['build-essential', "linux-headers-${kernelrelease}", 'dkms',
'linux-headers-server']:
ensure => installed,
}
and when the package linux-headers-server it's upgraded in the repositories
puppet tries to upgrade in client too. And as that package has
Hi Florian. great and smart method. But I've found a problem. If i have a
hash with two dimensions I'm losing the information of the first dimension.
Explained:
yaml:
---
routers:
router1:
ip: 1.2.3.4
ports:
1:
foo: true
bar: false
2:
Hi! I'm starting to separate data from code in my puppet modules. I'm using
hiera and can obtain specific hashes or arrays of values. It's amazing. I
can use them in templates in a good way without problems. But in puppet
manifests I'm having some problems. Is this code correct?:
$foo = [{"id"
Ok Daniel, thanks for your reply, but I have not control about these
individual "noreplace" files because are $hostname dependent.
In different hostnames, have different source locations so I cannot define
them in a specific way.
E.g:
hostname1/home/user/foo/bar/johndoe05/file1.cfg
hostname2/h
Ok, I understand. But i have not control about these individual "noreplace"
files because are $hostname dependent.
In different hostnames, have different specific source locations.
So that was the reason for I need something similar to ignore parameter.
(Or a workaround)
Thanks!
--
You recei
Hi, I would like to achieve a conditional file replacement but lightly
different. I deploy recusively a directory with a lot of config files. This
is my resource:
file {"/foo":
ensure => directory,
recurse => remote,
source => "puppet:///modules/module_name/configs/${hostname}/foo"
Hello, I'm making the deployment of an application configuration as follows:
file {"/home/user/foo/bar":
ensure => directory,
recurse => remote,
source => "puppet:///configs/${hostname}/home/user/foo/bar",
ignore => ["file1.cfg","file2.cfg"],
}
I am ignoring these two files
11 matches
Mail list logo