-
Notifications
You must be signed in to change notification settings - Fork 35
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
Compatibility with Sail commands #29
Comments
I'm going to need some more details! What happens if you run sail artisan queue:work outside of Solo and what happens when you run it as a Solo command? |
|
Ah ok, perfect! Thank you |
Thanks for that, I should have tried that :)
Note, the process most likely returned an error like "command not found",
it would be a good improvement to display the error in solo, so users can
self help.
Cheers for looking into this to both.
…On Sat, 23 Nov 2024, 03:53 Aaron Francis, ***@***.***> wrote:
Ah ok, perfect! Thank you
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AH265NUO4PM7SFPUWPU2IX32B5AQPAVCNFSM6AAAAABSIHQZZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJTHE2DCOJWHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Good thinking! I'll see what I can do there. |
Outside of displaying the error to know whats going on, the reason this happens is because This is similarly how npm handles it when you run use a binary installed as a dependency. |
Oh huh, I would've just assumed that it inherited the path that existed. Is that not true? |
It probably inherits |
That's correct, I expect most people to have it as an alias, it's suggested in the Sail docs during the install steps: https://laravel.com/docs/11.x/sail#configuring-a-shell-alias |
Yup, so it may be beneficial to Solo to add Maybe even add |
Hey,
It's all in the title!
Great package, would love to be able to use it with sail commands that require to be running within docker, like schedule:work, queue:listen etc..
Still using it for Logs (pail) / Vite in the meantime :)
The text was updated successfully, but these errors were encountered: