Hi Mark, You need to run the puppet command as sudo.
sudo /opt/puppetlabs/bin/puppet module install <module-name> doing so will install modules in the correct path. /etc/puppetlabs/puppet/environments/production/modules/ I am using RHEL 7 and I normally run the command: sudo su - before running puppet commands. That way I am running puppet as root and all of the modules show up in the webui. Disclamer: I am not a linux guy (yet), so I don't know for sure that my recommendations above are "best practices" Hope that helps. Jason On Tuesday, March 31, 2015 at 6:45:09 AM UTC-7, Mark S wrote: > > Hi, > I've set up a monolithic install of PE to evaluate it for our organisation > but am running into problems even following the Quick Start Guides. I'm > trying to follow the Windows quick start guide and have successfully > followed Step 2, searching for and installing the 'registry' module. > However if you follow the guide to the letter using the command 'puppet > module install puppetlabs-registry' it will install the module to > ~/.puppet/modules instead > of /etc/puppetlabs/puppet/environments/production/modules unless you use > the '--environment production' parameter. > > Next when following Step 3 where you create a new node group and add a new > class to it, I cannot see the new registry module in the class list. I can > see the stdlib dependency there, just not registry. > > What am I doing wrong here? > > Thanks, > > Mark > -- 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://groups.google.com/d/msgid/puppet-users/dde861cc-264b-4ce3-ae56-d01d089daf88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
