Graham Campbell
Graham Campbell
Well, yes, but in order to comply with the license, that means you cannot show the logos to anyone.
Instead of using `getenv`, use Laravel's `env` function. It is threadsafe, unlike PHP's `getenv` function.
NB The `env` function has existed since Laravel 5.4 and is the recommended way to access environment variables when needed. Finally, in Laravel 5.8, the long-standing issue of the thread-safety...
You can still recover the old behaviour of Laravel 5.7 if you need it, in 5.8, by using your own bootstrapper. Just define the following class in your app: ```php
Deleting those requirements is a very bad idea, since this package really does require them.
> did you ever find a solution to this problem? Do $user->toArray() or something, but don't try to serialise the entire user object - that won't work.
It doesn't work because you end up trying to serialise the entire laravel service container and all resolved objects, lol.
NB, this is improved in laravel 5 with queuable entities.
@Zizaco This is easily fixable by setting correct git config.
I'm on windows, and everything's fine for me. https://i.starbs.net/A8NZ