Try to add the 2 lines below inside your virtualhost
<VirtualHost *:3000>
SetEnv RAILS_ENV production
RackBaseURI /
.......
</VirtualHost>
Don't forget to restart apache.
[]s
Felipe
On Mar 9, 6:33 am, theirpuppet <theirpup...@gmail.com> wrote:
> Hello all
>
> Puppet, puppetmaster, ruby, etc installed from standard Ubuntu 11.10 x86_64
> APT repos
> Dashboard 1.26 from .deb pulled
> fromhttp://apt.puppetlabs.com/pool/oneiric/main/p/puppet-dashboard/
> Apache config pulled
> from /usr/share/puppet-dashboard/ext/passenger/dashboard-vhost.conf
>
> My simple test with webbrick worked a treat. So I installed Apache and
> passenger mod (from Ubuntu APT repos) and that's where I had a problem. The
> error from Apache2 error log:
>
> > [Fri Mar 09 13:09:35 2012] [error] [client 1.2.3.4] Directory index
> > forbidden by Options directive: /usr/share/puppet-dashboard/public/,
> > referer:http://[IPADDRESS]:3000/nodes/unchanged
>
> Adding Options +Indexes is not the resolution as it just displays the
> static files in that directory.
>
> Here's my /etc/apache2/sites-enabled/010-dashboard.conf:
>
> > #PassengerRoot /var/lib/gems/1.8/gems/passenger-2.2.11
> > PassengerRoot /usr/lib/phusion_passenger
> > PassengerRuby /usr/bin/ruby
> > # you may want to tune these settings
> > PassengerHighPerformance on
> > PassengerMaxPoolSize 12
> > PassengerPoolIdleTime 1500
> > # PassengerMaxRequests 1000
> > PassengerStatThrottleRate 120
> > RailsAutoDetect On
> > <VirtualHost *:3000>
> > ServerName FQDN
>
> ServerAlias X.X.X.X
>
> DocumentRoot /usr/share/puppet-dashboard/public/
>
> > <Directory /usr/share/puppet-dashboard/public/>
> > Options None
> > Order allow,deny
> > allow from all
> > </Directory>
> > #ErrorLog /var/log/apache2/dashboard.example.com_error.log
> > LogLevel warn
> > #CustomLog /var/log/apache2/dashboard.example.com_access.log combined
> > ServerSignature On
> > </VirtualHost>
>
> The only thing I can think of is that I had connected via IP Address, not
> FQDN. So I've updated DNS but unfortunately I don't have control over my
> employer's resolvers. Thus I have to wait until the cached failure expires
> - or bother the team responsible...
>
> Any and all ideas are welcome. I think it's either the DNS issue or
> something wrong with Passenger?
>
> Thanks
> David
--
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.
