Level 4
This was caused by having Forge settings Meta > Website Directory set to "/public" instead of "/current/public"
Thanks @TaylorOtwell !
1 like
Sep 23, 2016
1
Level 4
Envoyer deploy does not change release
We are using Envoyer with a Forge deployed AWS EC2 server.
Since switching to Envoyer, no code changes that Envoyer deploys are reflected on our site.
For instance, no views look different even after clearing the views cache. No code changes output anything different to the logs. The "schedule:run" command never uses the new thenPing statements we added since switching to Envoyer and it will only run once when it is first added under Forge then it stops working.
In the "Activate New Release" deployment stage it shows this in the log after each deploy, so it appears PHP is restarting:
Release Activated (20160923160925)!
PHP-FPM Detected: Reloading
What might be going on here?
Please or to participate in this conversation.