For the AIO, you can certainly get passenger working. (Although we'd love to hear why PuppetServer isn't working or what you want).
Config files on a gist: https://gist.github.com/stahnma/cf89dfa79b053f138eb1 This should get you most of the way there. You might have to sub out passenger versions or something. export PATH=/opt/puppetlabs/puppet/bin:$PATH # install passenger gem install --no-rdoc --no-ri passenger # you need gcc, apr or build-essential installed # this command is different if using nginx passenger-install-apache2-module --languages ruby -a # create a puppet user # Add our user and group if getent group 'puppet' &> /dev/null; then /usr/sbin/groupmod --system 'puppet' else /usr/sbin/groupadd --system 'puppet' fi if getent passwd 'puppet' &> /dev/null; then /usr/sbin/usermod --system --gid 'puppet' --home '/opt/puppetlabs/server/data/puppetmaster' --shell '/usr/sbin/nologin' 'puppet' else /usr/sbin/useradd --system --gid 'puppet' --home '/opt/puppetlabs/server/data/puppetmaster' --shell '/usr/sbin/nologin' 'puppet' fi # create public dir mkdir -p /opt/puppetlabs/server/data/puppetmaster/public mkdir -p /opt/puppetlabs/server/data/puppetmaster mkdir -p /var/log/puppetlabs/puppetmaster chown puppet:puppet /opt/puppetlabs/server/data/puppetmaster/public /opt/puppetlabs/server/data/puppetmaster /var/log/puppetlabs/puppetmaster /opt/puppetlabs/server/data/puppetmaster/ config.ru cp -p ./config.ru /opt/puppetlabs/server/data/puppetmaster/config.ru cp -p ./passenger-apache.conf /etc/apache2/sites-available/puppet-passenger sed -i 's/__PASSENGER_VERSION__/5.0.16/g /etc/apache2/sites-available/puppet-passenger On Fri, Jul 17, 2015 at 2:53 PM, Ramin K <[email protected]> wrote: > On 7/17/15 2:25 PM, Felix Frank wrote: > >> On 07/17/2015 10:08 PM, Felix Frank wrote: >> >>> Hi list, >>> >>> I'm currently trying to get Puppet 4 to work with nginx/passenger. I had >>> that working with Puppet 3.x pretty well, but the new packaging stumps >>> me. >>> >>> For one, the config.ru file is no longer being packaged, apparently. >>> It's missing from my systems regardless of whether puppet-agent or even >>> puppetserver are installed (having it in the latter would be kind of >>> weird, too, I guess). >>> >>> Now I can retrieve the config.ru right from github, so that's not a >>> blocker. Next issue: The puppet user and group is now owned by package >>> puppetserver, apparently. Just getting the puppet-agent AIO will not >>> create it on my Debian 8 system. (The fact that there is not yet a >>> puppetserver package for jessie is an additional hinderance at this >>> time.) >>> >>> Currently, both WEBrick and Passenger error out on this testing VM >>> running Debian 8 with PC1. >>> >>> There should probably be tickets for these issues, but I'd like to >>> gather some feedback first. Has anyone gotten their feet wet with >>> non-puppetserver masters that run 4.x? >>> >>> Cheers, >>> Felix >>> >> >> Following up on that story: Creating puppet user and group helped, >> apparently. But no dice with passenger. >> >> Using the OS Ruby will not work, obviously, since /opt/puppetlabs/... is >> not in its lookup path. Works as designed. But then the vendored Ruby >> from that tree has no rack support. >> >> I failed to install the passenger gem there as well, because apparently, >> Phusion only supports Ruby up to 2.1.3, whereas Puppet bundles 2.1.6. >> >> I did try to get system Ruby to load Puppet by adding this at the top of >> config.ru: >> >> $LOAD_PATH.unshift('/opt/puppetlabs/puppet/lib/ruby/vendor_ruby') >> >> But no dice. Puppet still cannot be loaded because (apparently) system >> Ruby's openssl support is not up to par. Now perhaps it's possible to >> load even more stuff from the vendored Ruby, but this whole approach >> feels horribly wrong anyway, so I'm stopping right here. >> >> As it stands, I guess if I really want to run Puppet 4 through >> Passenger, I will need to install from source. Thoughts? >> >> Thanks, >> Felix >> >> > I wrote a how-to on using different Rubies for your Puppet master and am > using it to run a Ruby 2.1.6/Puppet 3.7.x master. I would attempt something > similar in your case. > > > http://ask.puppetlabs.com/question/16983/performance-improvements-without-updating-to-puppet-server/ > > Install Passenger 4.x via packages. Doesn't need to be built on the Ruby > you plan to use. > Point to /opt/puppetlabs ruby via PassengerRuby vhost directive. > > Other than those two steps, it sounds like you're pretty close. > > Ramin > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/55A97952.9030403%40badapple.net > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAMto7L%2BNjRigz-W4Nm6ZiFqhD2yU3VDkoFK4W-h7MpFTXXWX-A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
