[Capistrano] Document root symlink causes "Symbolic link not allowed or link target not accessible"

[Charles Brian Quinn]

A client wanted to deploy on their Suse Enterprise Linux Server (SLES)
10, recently, and I kept getting this nasty nasty message along with
some Novell apparmor non-sense in the apache and document specific
logs.  Images/stylesheets and generally everything out of the public
document root wouldn't show.  Specifically the message was:

Symbolic link not allowed or link target not accessible:
/srv/www/project/current, referer: http://test.project.com/

It ended up being that Apache on SLES did not/could not use a symlink
as the actual directory from which to serve out content.  if I
replaced the /srv/www/project/current symlink with the actual
directory, it worked fine.

The fix I ended up using, was I changed my apache setup from:

<Directory "#{deploy_to}/current/public">

to:

<Directory "#{deploy_to}">

so the Document root stayed:

DocumentRoot #{deploy_to}/current/public

but the actual Directory with Options for FollowSymlinks turned on was now:

<Directory "/srv/www/vhosts/project">

and now the symlink option could be followed to get to the current release.

Hope this helps someone,
-- 
Charles Brian Quinn
self-promotion: www.seebq.com
highgroove studios: www.highgroove.com
slingshot hosting: www.slingshothosting.com
main: 678.389.9462  fax: 678.826.0969

Ruby on Rails Bootcamp at the Big Nerd Ranch
Intensive Ruby on Rails Training:
http://www.bignerdranch.com/classes/ruby.shtml

--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---