I have figured it out. Simply move "RailsAutoDetect On" into the virtualhost block will resolve the issue.
Basically, their example should be fixed the same way. On Tue, Jul 24, 2012 at 11:30 AM, banjer <jash...@gmail.com> wrote: > I'm having the same exact problem trying to get Apache to serve puppet > dashboard on CentOS 6.3. Apache is set up to serve my puppet master, and > the puppetmaster is configured and working just fine. I get this in the > apache error log: > > Directory index forbidden by Options directive: > /usr/share/puppet-dashboard/public/ > > Here are my configs. Added these lines to /etc/httpd/conf/httpd.conf: > > ServerName merkin.mydomain.com > > # Passenger for rails apps (puppet) > LoadModule passenger_module > /usr/lib/ruby/gems/1.8/gems/passenger-3.0.14/ext/apache2/mod_passenger.so > PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-3.0.14 > PassengerRuby /usr/bin/ruby > > > This is my /etc/httpd/conf.d/dashboard-vhost.conf > > # you may want to tune these settings > > PassengerHighPerformance on > PassengerMaxPoolSize 12 > PassengerPoolIdleTime 1500 > # PassengerMaxRequests 1000 > PassengerStatThrottleRate 120 > RailsAutoDetect On > > Listen 3000 > <VirtualHost *:3000> > ServerName merkin.mydomain.com > > DocumentRoot /usr/share/puppet-dashboard/public/ > <Directory /usr/share/puppet-dashboard/public/> > Options None > Order allow,deny > allow from all > </Directory> > ErrorLog /var/log/httpd/dashboard.com_error.log > LogLevel warn > CustomLog /var/log/httpd/dashboard.com_access.log combined > ServerSignature On > </VirtualHost> > > > When I visit merkin.mydomain.com:3000, all I'm seeing is an Apache test > page. Seems like Hai and myself are using (close to) the same version of > gems and passenger, so perhaps something related to 3.x passenger. > > Perhaps RailsAutoDetect is not auto-detecting correctly? Can I try > explicitly setting RailsBaseURI? If so, what should it point to? > > Thanks for the help. > > > On Thursday, July 19, 2012 7:22:53 PM UTC-4, Hai wrote: >> >> Can someone help me in this forum? >> >> On Thu, Jul 12, 2012 at 4:42 PM, Hai Tao <ehai...@gmail.com> wrote: >> > that is almost exactly what I have , except I put the mod_passenger.so >> > to /var/lib instead of /var/lib64. >> > >> > LoadModule passenger_module >> > >> > /usr/lib/ruby/gems/1.8/gems/passenger-3.0.13/ext/apache2/mod_passenger.so >> > PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-3.0.13 >> > PassengerRuby /usr/bin/ruby >> > >> > But I do not think that would affect anything. >> > >> > The thing is I have no experience with passenger, and I do not know >> > how to trouble shoot this problem. >> > >> > Is there suggestions? >> > >> > Thanks. >> > >> > On Thu, Jul 12, 2012 at 4:30 PM, Clay <clay...@gmail.com> wrote: >> >> I'm running puppet dashboard 1.2.9 , just followed document at >> >> >> >> http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#running-dashboard-in-a-production-quality-server >> >> , >> >> >> >> [root@puppet conf.d]# grep -v ^# dashboard-vhost.conf >> >> >> >> Listen 3000 >> >> <VirtualHost *:3000> >> >> ServerName puppet.domain.com >> >> >> >> DocumentRoot /usr/share/puppet-dashboard/public/ >> >> <Directory /usr/share/puppet-dashboard/public/> >> >> Options None >> >> Order allow,deny >> >> allow from all >> >> </Directory> >> >> ErrorLog /var/log/httpd/dashboard_error.log >> >> LogLevel warn >> >> CustomLog /var/log/httpd/dashboard_access.log combined >> >> ServerSignature On >> >> </VirtualHost> >> >> >> >> I have the passenger module config in /etc/httpd/conf/httpd.conf >> >> because >> >> puppet master is also using passenger. >> >> >> >> LoadModule passenger_module >> >> >> >> /usr/lib64/ruby/gems/1.8/gems/passenger-3.0.13/ext/apache2/mod_passenger.so >> >> PassengerRoot /usr/lib64/ruby/gems/1.8/gems/passenger-3.0.13 >> >> PassengerRuby /usr/bin/ruby >> >> >> >> >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups >> >> "Puppet Users" group. >> >> To view this discussion on the web visit >> >> https://groups.google.com/d/msg/puppet-users/-/rl1IMNDZR3MJ. >> >> >> >> To post to this group, send email to puppet-users@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> puppet-users+unsubscr...@googlegroups.com. >> >> For more options, visit this group at >> >> http://groups.google.com/group/puppet-users?hl=en. >> > >> > >> > >> > -- >> > Hai Tao >> >> >> >> -- >> Hai Tao > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/WHnHWvRpEPEJ. > > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. -- Hai Tao -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.