Closed fr3ddy closed 3 years ago
My current assumption is, that due to the fact that the entry point is changing when using Laravel Vapor, the constant
LARAVEL_START
is not set.
I think your assumption is correct. The constant is defined in Laravel's index.php file, which I also assume is not called in Vapor (I don't have experience with the platform). We also had this issue when running the application with Octane.
I'm going to make "a fix" and set the value if the constant is not defined. The timing might not be exact, but better than making the app crash.
@fr3ddy I've just released the fix. Could you install the new v3.0.6
version and try again?
Greate support. Thank you. Works like a charm!
Hey, after adding the package as describe I've tested it locally and it was working like a charm. Now I did deploy it with Laravel Vapor onto AWS and we are getting the following errors:
and the following (but I would assume, they are related).
In case anybody has experienced the same issue, I would be happy to hear your opinion on how we can solve that. My current assumption is, that due to the fact that the entry point is changing when using Laravel Vapor, the constant
LARAVEL_START
is not set.Regards, Frederik