On 09/16/2012 12:30 AM, Papp Tamas wrote:
hi All,
/usr/lib/ruby/vendor_ruby/1.8/rubygems/dependency.rb:247:in
`to_specs': Could not find rack (~ 1.1.0) amongst [] (Gem::LoadError)
from /usr/lib/ruby/vendor_ruby/1.8/rubygems/dependency.rb:256:in
`to_spec'
from /usr/lib/ruby
hi All,
I'm trying to install puppet-dashboard. When I start it:
# /etc/init.d/puppet-dashboard start
* Starting Puppet Dashboard NOTE: Gem.source_index is deprecated, use
Specification. It will be removed on or after 2011-11-01.
Gem.source_index called from
On 06/01/2012 04:34 PM, jcbollinger wrote:
Sorry about the late answer.
You didn't say what those modifications were, but probably they are
what's killing you. For the modules and classes in this example,
If I see well, the only one is a node.pp imported from site.pp .
Puppet's autoloader
On 05/31/2012 03:22 PM, jcbollinger wrote:
I suspect you have a problem either with paths or with permissions.
I don't find anything related to this.
Supposing you have not configured custom directories, your setup
should look like this:
puppet base
L puppet.conf
L manifests/
L
hi All,
I'm a bit new to puppet. Is there a mailing list for puppet beginners?:)
I have a service module called postfix, which defines file in a class:
file {
'/etc/postfix/main.cf':
owner = root,
group = root,
mode = 644,
content =
On 05/30/2012 05:58 PM, Ryan Coleman wrote:
The issue here is how your module is structured in relation to what
Puppet expects to automatically find your manifests.
In jay module, manifests directory, Puppet expects init.pp to have the
jay class.
If you want to have a jay::postfix class,
On 05/31/2012 12:29 AM, Papp Tamas wrote:
On 05/30/2012 05:58 PM, Ryan Coleman wrote:
The issue here is how your module is structured in relation to what
Puppet expects to automatically find your manifests.
In jay module, manifests directory, Puppet expects init.pp to have the
jay class
