Deploys via Envoyer Fail and point to an Old Release (at least partially)

Published 1 year ago by nate.a.johnson

I'm having a weird issue. My setup is on Linode via Forge and hot deployed with Envoyer -- so a complete Taylor-made stack.

Sometimes I deploy and the current symlink gets moved to the latest release as it should, but I refresh the page and my CSS and JS that gets compiled via Mix has the wrong hashes in the file names. They are from a previous release.

I've tried running all of the artisan clear commands and none of them help. I restart nginx with zero luck. I can even delete the current synlink and the site keeps on working, so that is concerning. The only thing I have found so far to fix it is to reboot the entire Linode and that is definitely not ideal. So it looks like something is getting stuck in memory somewhere, but I don't know where.

Anyone ever see anything like this?

Thanks!

Best Answer (As Selected By nate.a.johnson)
nate.a.johnson

For anyone with this problem, in Envoyer you can edit your server, tell it what version of php you are using and if you want it restarted after a deploy. Mine was still set to an old version of PHP and upgraded since I built the box with Forge.

nate.a.johnson

I found that php was holding on to references to the old site in memory. Running this fixed it.

sudo service php7.1-fpm restart

I don't know if envoyer doesn't restart php 7.1 properly. I think it used to restart php 7.0 before the upgrade. Maybe the envoyer scripts need to be updated similarly?

nate.a.johnson

For anyone with this problem, in Envoyer you can edit your server, tell it what version of php you are using and if you want it restarted after a deploy. Mine was still set to an old version of PHP and upgraded since I built the box with Forge.

Please sign in or create an account to participate in this conversation.