Why does Envoyer need to restart PHP FPM when deploying?

@uni_t Not all projects are the same and sometimes PHP-FPM needs to be restarted for it to load the new code. Perhaps not in your case, but in other cases it might need to do that.

You can uncheck that setting in Envoyer, on a per project basis, if you don't to restart PHP-FPM.

It's because your new deployment is created in a different directory to the one currently being served by php. The release is symlinked from the directory specified in the nginx config.

In order for php to load the new deployment it must be restarted so it follows the updated symlink in your project folder.

How do you disable the "PHP-FPM" restart?

I can't find the disable option everyone seems to be talking about either

@Thatdoorsajar Its in your Server configuration tab

Anyone figured out a good solution to have Envoyer restart php-fpm if you're not using 7? Currently Im getting failures because Ubuntu insists on using interactive authentication despite me putting php5.6-fpm in Visudo. I dread the idea of having to manually restart php-fpm with every release.