Laravel 5 Modules Service Provider And Compatibility With Laravel Doctrine

Is this the best service provider to use for segmenting a Laravel 5 app into modules? Also does anyone have experience working with this and Laravel Doctrine. If so what level of compatibility do the two have with one another. I’m trying to gauge the best way to segment an app into modules while also using doctrine instead of Eloquent.

1 Like

You might have a better chance to get an answer here.


You’re are probably right.

Though so far the pingpong package for modules looks legit.

The modules package is not compatible with doctrine Laravel. The first issue I’ve run into is generating and running migrations. Both laravel doctrine and modules use very different strategies. I rather not but I think I might build a bridge which also allows for module dependencies. Does anyone know of anything like that? The doctrine laravel migration process would need to take into account the module which the migration is located and dependencies of the module.

For anyone else whom would like to use modules with doctrine I have resorted to just using the standard laravel-doctrine implementation of modules. All the migrations are stored in the single top level directory instead of within individual modules. This approach seems to work fine. Not to mention there would need to be some type of dependency resolution chain for migrations within separate modules which I think is an unnecessary complexity considering modules are really just a way to better organize code into dedicated namespaces.

1 Like

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.