Using Envoy as alternative to Envoyer but having trouble

You'll need to run sudo service nginx reload as part of your deployment script, otherwise nginx won't follow the symlink to the new directory.

Edit: Actually, it may be sufficient to just reload FPM (sudo service php5-fpm reload).

In the event that it's not, you'll need to add the following to /etc/sudoers

# Allow forge user to reload nginx
forge ALL=NOPASSWD: /usr/sbin/service nginx reload

#includedir /etc/sudoers.d

Make sure you add it before the includedir line.

@deringer I already tried restarting nginx, it doesn't seem to matter. It doesn't seem like nginx would need restarted if all I am doing is changing an existing symlink, isn't that the point of the symlink, so it can be easily changed without disrupting anything?

Thanks!

You have to restart/reload it to recache the real path. realpath_cache_size and realpath_cache_ttl settings are in php.ini

http://php.net/manual/en/ini.core.php#ini.sect.performance

Duration of time (in seconds) for which to cache realpath information for a given file or directory. For systems with rarely changing files, consider increasing the value.

@deringer So I just tested it again, and had the same issue, but I noticed something. I went into my releases folded and delete the old releases then it started working.

@bashy Ok so you are saying that nginx is pointing to the correct release, it's just that when the index.php page is hit and bootstraps the application, it's still loading from the old release because the path has been cached?

@deringer Ok cool runig php5-fpm reload worked. Now it makes sense, it seems the problem wasn't nginx or even the symlink not working, it was as @bashy pointed out, PHP was caching the real path which was causing laravel to load old files when bootstrapping the application.