I'm setting up a pair of VM's to do some puppet testing on, and I am trying
to figure out how to install puppet without having the the system also
install ruby.
I already have ruby installed through RVM, and I'd like to get puppet to
use that ruby.
For the record, I'm using CentOS 6.3 as the O
On Friday, September 21, 2012 7:59:46 AM UTC-7, jcbollinger wrote:
>
> You have a wrong concept: yum and rpm don't care whether any particular *
> software* is installed, they care only about what *packages* (RPMs) are
> installed. That's why they don't care about the Ruby you've installed via
On Friday, September 21, 2012 1:11:22 PM UTC-7, Michael Stanhke wrote:
>
>
> > As long as we're talking about installing from source, there's a 4th
> option:
> > use RVM's Ruby 1.9.2-p230 to install the Puppet gem. Instructions are
> here
> > (though you'll need to adapt it to your specific env
On Friday, September 21, 2012 7:11:18 PM UTC-7, Jakov Sosic wrote:
>
> On 09/22/2012 03:21 AM, jdehnert wrote:
>
> > I'm aware of the issues of installing software through source vs. pkg
> > management systems. I should have mentioned that I've been in IT fo
I can't seem to find any direct reference yo this in the puppet 3.0 docs so
does anyone know if puppet 3.0 can handle yum groupinstalls without resorting
to using an exec?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion
I want to pass a few variables through to the other files in a module. I
have a define statement that sets one default...
define redis::install ( $port = 6397, $version )
What I am unclear on is how far does this define reach in my module? For
instance, do I need to have everything that u
I have asked this question over at ask.puppet.com, but there has been no
response at all.
I did notice that there is a very old thread about this problem, but there
was never any solution posted.
I'm hoping that Ken Barber is still on this list and can remember if he was
able to help resolve
Greetings All,
I decided to try and implement the puppetlabs-puppetdb and
puppetlabs-postgres modules after I had both puppetdb and postgres
installed and working on my puppet server. This was ill advised as it
broke my working setup and no amount of re-configuring seems to be able to
get thi
leting your
> routes.yaml file (if PuppetDB is the only thing in there). Restart the
> puppet server and things should work again.
>
> Trevor
>
> On Fri, Jun 10, 2016 at 11:36 PM, jdehnert > wrote:
>
>> Greetings All,
>>
>> I decided to try and implement
Thanks Wyatt. I am just trying to disconnect my puppetserver from
puppetdb, but I do want to re-connect them in the future. Your information
is very helpful. I find it easy to get confused about what part us causing
what problem when I have puppetserver, puppetdb, puppetdb terminus,
postgre
We have a BINGO!. That did the trick. Thank You Trevor, and thanks to
everyone who offered assistance. I truly appreciate it.
On Saturday, June 11, 2016 at 9:27:16 PM UTC-7, Trevor Vaughan wrote:
>
> Get rid of this: storeconfigs = true
>
> Trevor
>
--
You received this message because you
Thanks Wyatt. I am just trying to disconnect my puppetserver from
puppetdb, but I do want to re-connect them in the future. Your information
is very helpful. I find it easy to get confused about what part us causing
what problem when I have puppetserver, puppetdb, puppetdb terminus,
postg
12 matches
Mail list logo
