Wednesday, April 12, 2017

Two Different Laravel Applications using Same Database & Notifications

I have one application built on say 'mysite.com'. Then after sometime a separate admin panel was created and hosted on admin.mysite.com

Both apps are using same database, but different models and code. Both of the apps have to generate emails, notifications and using ShouldQueue interface to run it in background.

Problem is that if I run php artisan queue:work in either app, it fails as soon as it find notification,email generated from other app giving error Class Not Found, which is correct as if site app worker processing any notification generated from admin app or the other way.

I think by separating both queues, there could be a way, but not able to get exact start point for this approach.

Any help?

Thanks,



via devilzk83

Advertisement