Closed nateajohnson closed 7 years ago
Develop/master branch should always be considered unstable. That's standard.
We'll be doing a fair amount of work on this in the coming days.
Thanks. I figured so, but wanted to get this out there. I'll wait until the official 1.0 release that supports Laravel 5 and test it then.
0.6 will be released tomorrow or the day after, which is the last L4 release for the project. After that, I imagine either 1.x or 0.7.x will be L5 onwards.
Could you please share your doctrine.php config, @nateajohnson?
Here it is...
<?php
return [
'simple_annotations' => false,
'metadata' => [
// Paths to entities here...
base_path('app')
],
'proxy' => [
'auto_generate' => false,
'directory' => null,
'namespace' => null
],
// Available: null, apc, xcache, redis, memcache
'cache_provider' => null,
'cache' => [
'redis' => [
'host' => '127.0.0.1',
'port' => 6379,
'database' => 1
],
'memcache' => [
'host' => '127.0.0.1',
'port' => 11211
]
],
'repository' => 'Doctrine\ORM\EntityRepository',
'repositoryFactory' => null,
'logger' => null
];
@nateajohnson are your entities in the app directory?
Yeah, they are in the app directory. And it works just fine most of the time. The only thing that was failing was the schema generation when in a laravel production environment (where there is a compiled.php file - all classes in one big file for performance reasons). In a local environment it works fine because laravel doesn't create the compiled.php file. Now if I run the artisan optimize command and create compiled.php locally it fails there too. It appears the schema generator is finding compiled.php with duplicate class declarations which are conflicting with the scanning of the non-compiled classes.
That's my best guess at the issue.
Closing because project is no longer maintained. Thanks.
I am using the develop branch in a Laravel 5 app. If this branch isn't quite ready, just let me know. Anyway, I get the following error with the doctrine artisan commands. It only happens when there is a compiled.php file in storage/framework. Since a local app ignores that file, all is well. But in production it uses that file. If I delete that file, I can run the artisan commands and regenerate the file, but I doubt that is what you are after.
Thanks Nate