You would need to run that command in a separate near duplicated service as that is a long running process.

How it works? can you please explain a little.

You create another service in your project, it needs to deploy from the same source and have all the same service variables, you would only need to adjust its start command to run the queue.

Thanks It works, but it's not a efficient way to do this.

Hola brody, estoy en ese paso de agregar queues:work pero no entendí los pasos que se deben realizar soy nuevo en railways.
Muchas gracias.

Thanks It works, but it's not a efficient way to do this.

Hola Saptarshidy, logró realizar alguna forma de hacerlo funcionar?
Gracias.

Please use English.

What steps do you need clarification on?

Hello, were you able to get it to work somehow? Thanks.

Please use English.

What steps do you need clarification on?

Yes, please help me with that. I don't quite understand how to configure Laravel Reverb to make it work correctly. I'm not sure if I need to change REVERBHOST, REVERBPORT, REVERB_SCHEME, and how to register it in Railway.
I am very grateful.

I don't know anything about reverb and this thread has not mentioned anything about reverb either.

No problem, I was referring to queue:work. Sorry for the confusion, I just happened to be looking at Laravel Reverb. So, regarding php artisan queue:work, how should it be registered to work properly?