Closed clee231 closed 8 years ago
After reading the description a bit more, I realized that this is only for Laravel 5.1 LTS... Sorry for my misunderstanding...
Also, I see that the changes on master c8af9a952cae324fe8394ddd7c43379ae1c3bd17 fix the aforementioned issues for Laravel 5.2.
Please try the dev-master
version it already has some 5.2 related changes.
Yes, this seems to be no longer an issue after pulling from the latest development branches. Sorry for the confusion.
Using a fresh Laravel 5 installation, it seems that the GAE:setup command will fail due to a change with how application keys are generated. The error is now as follows:
Application keys are now encoded with base64 with seems to have an '=' symbol at the end of the string.
For example: When I generate a new key via artisan (
php artisan key:generate
), something along the lines of the following gets placed on the third line of the default .env file:I haven't had time to take a through look at the code yet, but I think it might have to due with the InitHelper class. This implementation may not support reading in strings with multiple '=' symbols within the line.
Notes on my current setup: