Wednesday, January 31, 2018

Laravel Forge/Envoyer using old releases since upgrading to 5.5 - development

Laravel Forge/Envoyer using old releases since upgrading to 5.5

I am experiencing very strange behavior since upgrading to Laravel 5.5, where the site will continue to show an old release after successfully deploying with Envoyer.

The current folder is correctly set to the newest release, however the site still shows the old release.

If the old release folder is manually deleted, or gets deleted via deploying enough times, the entire site will break, and this shows up:

Warning: include(/home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/../vlucas/phpdotenv/src/Exception/InvalidPathException.php): failed to open stream: No such file or directory in /home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/ClassLoader.php on line 444

Warning: include(): Failed opening '/home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/../vlucas/phpdotenv/src/Exception/InvalidPathException.php' for inclusion (include_path='.:/usr/share/php') in /home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/ClassLoader.php on line 444

Warning: include(/home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/../symfony/debug/Exception/FatalThrowableError.php): failed to open stream: No such file or directory in /home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/ClassLoader.php on line 444

Warning: include(): Failed opening '/home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/../symfony/debug/Exception/FatalThrowableError.php' for inclusion (include_path='.:/usr/share/php') in /home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/composer/ClassLoader.php on line 444

Fatal error: Uncaught Error: Class 'SymfonyComponentDebugExceptionFatalThrowableError' not found in /home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php:122 Stack trace: #0 /home/forge/sitefoo.com/envoyer/releases/20180130124512/public/index.php(53): IlluminateFoundationHttpKernel->handle(Object(IlluminateHttpRequest)) #1 {main} thrown in /home/forge/sitefoo.com/envoyer/releases/20180130124512/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php on line 122

Once you restart the server after deleting the old folder, everything will go back to normal and the correct release will be used.

Does anyone have any ideas on what’s going wrong or how to solve this problem?

Thanks



from Laravel Questions and Answers https://laravelquestions.com/laravel/laravel-forge-envoyer-using-old-releases-since-upgrading-to-5-5/
via Lzo Media

2 comments:

  1. Its very helpful information and Thanks for the great article.
    Techtiq solutions is leading laravel developer uk offering various integrated IT Services including SEO Services & Digital Marketing Services.

    ReplyDelete
  2. It's really a valuable blog post. Thanks for sharing this nice article.

    Looking for a Mobile App Development Company in UK? Reach Way2Smile Solutions UK.

    ReplyDelete