Check out this package: https://github.com/caffeinated/shinobi

The developer does what you are trying to do. Also, his coding practices are really good!

illuminate3 said:

Check out this package: https://github.com/caffeinated/shinobi

The developer does what you are trying to do. Also, his coding practices are really good!

Thank you for your link!

@shahid ,

Any fix for the Warning: Ambiguous class resolution issue ?

arunkumar339 said:

@shahid ,

Any fix for the Warning: Ambiguous class resolution issue ?

Actually if you will use Namespace with database migration files and moves to project folder. then "composer dump-autoload" will throws this warning because same name-spaces are used in two different places. If you will not assign name space with migrations files. then it will not throw this warning. for now i fixed in this way.

To put it another way, I resolved my own issue with this by removing this section from my composer.json:

"classmap": ["migrations"	]

@weotch - good call. Did this in my package's composer.json and it removed the warnings.