Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[11.x] docs(queue): Add docs for forcing the default connection #9665

Closed
wants to merge 1 commit into from

Conversation

victorelec14
Copy link
Contributor

Added documentation to specify that the queue:work command can be forced to use the default connection. Two examples were provided: one using null and another using an empty string.

Added documentation to specify that the `queue:work` command can be forced to use the `default` connection. Two examples were provided: one using `null` and another using an empty string.
@taylorotwell
Copy link
Member

I don't see why we would need to document this? Just don't pass a connection at all.

@victorelec14
Copy link
Contributor Author

Hi @taylorotwell ,

I think it would be a good idea to document this. On some deployment websites (or in scripts), there are times when the "connection name" is a required field and cannot be left empty. Because of this, some people create a new connection without realizing that they can enter "null" as the connection name to use the default value.

For example, in the case of Ploi, it doesn’t allow you to leave it empty, but very few people know that entering "null" will select the default connection. Even the developer of Ploi wasn’t aware of this until I opened a support ticket.

image

This is not the first time I have seen this issue. It also happens in scripts that pass an empty string "" or use different commands depending on whether there is a value or not.

I think it would be good to reconsider this.

Thank you.

Docs: https://laravel.com/docs/11.x/queues#specifying-the-connection-queue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants