[QUESTION]: Deploying to productioin

[welsipieters]

Hi!

First of all, thanks for this package. I've been using it for a couple days now across various microservices and it works very nicely.

I'm wondering though, how you suggest deploying this to production? Within our platform we're talking about thousands of events across services. Having to provide a event.name within the php artisan rabbitevents:listen command just seems 'unrealistic' (for lack of a better word) in this scenario.

What would be your thoughts on this, and would you perhaps be open to a merge request from me for such functionality?

Cheers!

[masterjus]

Hi Wesley

We also have many events on our projects but we easily manage them by Supervisor. Our configuration is pretty similar to this https://laravel.com/docs/8.x/queues#supervisor-configuration. I don't know what deployment system are you using, but this is a good solution to deploy supervisord configs https://docs.ansible.com/ansible/2.4/supervisorctl_module.html to your servers.

You also could use wildcard events if you wish.

And... if you like our package, feel free to add a star to it :)

[masterjus]

@welsipieters

[welsipieters]

Hi Eugene,

Pardon my late reply. The wildcard events will do for my use case. Out of curiosity, could you give me an anonymized example of your supervisord configuration? (and in your case whatever you pass to supervisorctl) Perhaps that would help me navigate the waters a bit better.

Perhaps it would be an idea to add an (opinionated?) section to the README.md on how to deploy this to production in a sensible and manageable way? I could potentially see this growing into a jungle of events if not careful, haha.

Cheers!

[masterjus]

Hi Wesley

We've created a config file per project in the /etc/supervisord/conf.d/ folder and supervisord automatically load them.

We suggest reading official Laravel documentation before :) But maybe you're right and we need to add this section.

[masterjus]

As there's no activity, I'm closing this Issue.