I am working on RHEL 5.6 server, this is in private DMZ. No access to internet. I have downloaded the files I need to install the Puppet & Ruby. My goal is to install Puppet. I have downloaded....
when I start the install. I get this error message.
I did install ruby on this server. When I do ruby -v, I get this...
Hi,
I am trying to instal the puppet. I get this error. Please help..
yum install puppet-server
Loaded plugins: fastestmirror, presto
Loading mirror speeds from cached hostfile
* base: mirrors.greenmountainaccess.net
* extras: mirror.lug.udel.edu
* updates:... (2 Replies)
I'm looking to deploy a configuration management system at my company and was wondering which config management was better: cfengine or Puppet? Pros/Cons? I'm looking to deploy the free version of each.
Any advice would be greatly appreciated. Thanks. (6 Replies)
Hello all,
can you please let me know if the free version of puppet provides dashboard?
Or how do you get info about failed installation or other staff for the puppet agents?
Sorry for not googling first :) (3 Replies)
Can not complete the installation of a puppet server on a Linux box.
bash: passenger-install-apache2-module: command not found
Please use CODE tags as required by forum rules whenever you display sample input, sample output, and code segments. (1 Reply)
Hello Team,
Do You have any data/books/links related to Puppet? How to start, how to setup first env and execute "puppet" actions?
Thanks in advance!
Patryk (3 Replies)
Discussion started by: nsmcny
3 Replies
LEARN ABOUT CENTOS
bundle-package
BUNDLE-PACKAGE(1)BUNDLE-PACKAGE(1)NAME
bundle-package - Package your needed .gem files into your application
SYNOPSIS
bundle package
DESCRIPTION
Copy all of the .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1)
bundle-install.1.html, use the gems in the cache in preference to the ones on rubygems.org.
GIT AND PATH GEMS
Since Bundler 1.2, the bundle package command can also package :git and :path dependencies besides .gem files. This needs to be explicitly
enabled via the --all option. Once used, the --all option will be remembered.
REMOTE FETCHING
By default, if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.
For instance, consider this Gemfile(5):
source "https://rubygems.org"
gem "nokogiri"
If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to JRuby and
run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.
Even though the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
cific to your platform.
This problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
ing to Linux, or even when developing on OSX and deploying to Linux.
If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
to skip checking for more appropriate gems, and just use the ones in vendor/cache.
One way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
in the gems. For instance, you can run bundle package on an identical staging box during your staging process, and check in the ven-
dor/cache before deploying to production.
March 2013 BUNDLE-PACKAGE(1)