Closed paullaffitte closed 4 years ago
I'm currently using Envoy as a global just fine. Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.
Thanks!
Actually I found another issue about the same problem that I have #178 and it seems that the dependencies used in this version are just obsolete. Maybe you have manually upgraded them to make it work globally, but it should not be considered as stable then. I guess the only solution that I have now is to downgrade to the previous version, or maybe upgrade to 2.x.
Now I have a question because I read in the upgrade guide to 2.x that it will only support Laravel since version 6.0. What does it means? If Envoy can run in standalone why Laravel 6.0 would be a minimum requirement?
@paullaffitte People also use envoy as a dependency of their Laravel apps.
Description:
When installed globally like said in the docs, envoy fail to run. Actually I need to install it as a dev dependency of my Laravel project to make it work. This is annoying because I don't want to install my project dependencies on my CI pipeline (using gitlab), because it then takes more time to deploy and is not used for deployment since it's not run on my production server.
Here is the error that I get :
Steps To Reproduce:
composer global require laravel/envoy --no-progress
~/.composer/vendor/bin/envoy run deploy --commit="$CI_COMMIT_SHA"