Class 'Dotenv' not found

[deven003]

I am getting following error while running

php artisan gae:setup --config --cache-config --bucket="your-bucket-id" --db-socket="cloud-sql-instance-socket-connection-string" --db-name="cloud-sql-database-name" app-id

PHP Fatal error:  Class 'Dotenv' not found in /var/www/anglist/vendor/shpasser/gae-support-l5/src/Shpasser/GaeSupportL5/Setup/Configurator.php on line 69

  [Symfony\Component\Debug\Exception\FatalErrorException]  
 Class 'Dotenv' not found                                 

I am using Laravel 5.2

[shpasser]

As of now the package is not compatible with Laravel 5.2. Larvel 5.2 makes use of a newer version of Dotenv. I am still working on support for Laravel 5.2 and it is not yet ready. Very soon I'm going to create a new branch called 5.2 in order to maintain Laravel 5.2 compatible version of the package. Since Laravel 5.1 is LTS the current version of the package is here to stay.

[deven003]

thanks @shpasser for the update. Keep up the good work.

[suku-h]

Hey has the dotenv update for laravel 5.2 completed?

[shpasser]

Not yet, last two months I was too busy, to release a 5.2 compatible version. I hope to get it done in two weeks.

[agentmilindu]

Hi @shpasser, how is the developments going on for 5.2 support? :) Badly wanting to move to 5.2 on GAE. And we too can contribute :)

[shpasser]

Certainly, I would appreciate if you could help me to test and fix the new version before I publish it as stable.

[agentmilindu]

@shpasser Of course, with pleasure! :D I have a Laravel 5.2 app awaiting to be deployed on GAE, stuck with this Class 'Dotenv' not found error. If you can push your 5.2 branch, we can help you with testing and fixing :)

[shpasser]

Please start testing the first update was already pushed to master branch.

[agentmilindu]

Hi @shpasser, we are still working on this. We migrated to 5.2 from 5.0 we had to do lot of changes in our controllers and Auth model. Now we could reach where we use the Queues and Emailing! :D They too works nice! :D

[shpasser]

Thanks for the update.

[agentmilindu]

Hi @shpasser, when using Mailgun as email provider, I'm getting the following error. It seems the problem is with Guzzle's HTTPS.

production.ERROR: exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: POST https://api.mailgun.net/v3/rsvp.lk/messages.mime resulted in a 401 Unauthorized response: Forbidden

I tried using cURL Lite also, that also gives errors. It is really good if we can use cURL Lite. Can we do something for this?

[shpasser]

Hi @agentmilindu, I would prefer to stop discussing the issues here, please open a separate issue for every topic, so we could discuss them in a proper manner. Anyway, I will look into the mail related issue.