[Solved] Symlink issue after app build process

#1
For some reason we're not able to get LSWS to follow symlinks our deployment script sets. Symlinks work okay when set initially, but not when changed. (We're using Capistrano for a PHP app if that helps.)

Our symbolic links are set up as follows:
  • public_html => current/public
  • current => releases => latest

ls -la shows that the symlinks are set properly, however the content shown to the user is from an earlier build. A graceful restart doesn't get it to 'take.' I don't know if it's some sort of caching issue.

The same script is working fine on our dev server that runs Apache and has identical OS, packages, etc.

Running LSWS: 4.0.20 / CentOS 5.6 / WHM 11.3b27

Any help greatly appreciated!
 
#2
Fixed via restart config

I wasn't triggering the restart properly.

In case this helps somebody in the future:
  • Add your user to your sudoers file w/ appropriate abilities
  • Comment out "Defaults requiretty" in your sudoers file
  • Add "default_run_options[:pty] = true" to your Capfile
 
Top