deployer: Releases don't become current

  • Deployer version: 7.1.3
  • Deployment OS: MacOS

After some working releases the most recent release is not becoming current anymore. When this happens, I need to deploy as often as my kept releases are set to (5). Then it works for this release but after that, releases are again not set to current. This startet to happen at version 7.1.1 I think and I guess this is an issue of the symlinks. On my FTP clicking on “current” folder leads me not to the most recent release also. Releases displayed in dep releases are correct

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 17 (6 by maintainers)

Most upvoted comments

NOW it clicks. Your problem is not deployer. But most likely the opcache or statcache of PHP.

PHP has a cache for realpath solution, that means, that PHP knows that the file:

/current/public/index.php -> /releases/10/public/index.php

But once you have a new release, everything is fine on filesystem level, but PHP still has the old (now wrong) cache entry:

/current/public/index.php -> /releases/10/public/index.php

instead of

/current/public/index.php -> /releases/11/public/index.php

Check your hosting, wether you can run cachetool (there is a great contrib for it!) or restart php.

Hope that helps.

Linking the domain in my hosters settings panel directly to /releases/11/public works but /current/public outputs the content of release 10