All Artisan arguments not passed through

[tymondesigns]

Hi mate.. Great job on the package

When I run something like ./vessel artisan preset none

It seems like the last argument is not being passed through as seen here

This obviously works when running php artisan preset none on the host.

And other single argument commands work as expected such as ./vessel artisan horizon

Am I doing something wrong here?

Cheers

EDIT: it's weird that this doesn't work since you use php artisan "$@" in the bash script... confused lol

[fideloper]

Hi! I’ve passed many arguments through I believe - can you see if it’s other commands or just this one? Perhaps there’s something special about using “none” Is they command specific to you’re laravel app? I don’t remember if the preset command is an out of the box command or not. Thanks!

…

On Fri, Oct 20, 2017 at 13:44 Sean Tymon ***@***.***> wrote: Hi mate.. Great job on the package When I run something like ./vessel artisan preset none It seems like the last argument is not being passed through as seen here [image: image] <https://user-images.githubusercontent.com/1801923/31836953-f635cb54-b5ce-11e7-8cfd-2ecf5011abd8.png> This obviously works when running php artisan preset none on the host. Am I doing something wrong here? Cheers — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#18>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAch08JJIxJgNzfK6CsRSQImBpH89LsRks5suOoTgaJpZM4QBEk_> .

[tymondesigns]

Yea the command is a native Laravel one

It is kind of weird that it doesn't fit with all the other commands that are separated by a colon (All of those seem to work by the way)

I can't think of another command that has a separate argument

[fideloper]

Gotcha - I’ll check it out soon and see if I can find a reason - thanks!

…

On Fri, Oct 20, 2017 at 14:31 Sean Tymon ***@***.***> wrote: Yea the command is a native Laravel one <https://laravel.com/docs/5.5/frontend#introduction> It is kind of weird that it doesn't fit with all the other commands that are separated by a colon (All of those seem to work by the way) I can't think of another command that has a separate argument [image: image] <https://user-images.githubusercontent.com/1801923/31838648-ada5b1fe-b5d5-11e7-854d-6ccf7512208c.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#18 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAch0zxkCqZdm6EKMtuTQ4ZB2gNcD_s3ks5suPUhgaJpZM4QBEk_> .

[tymondesigns]

I've found the problem line

it's here:

As you can see when I shutdown the containers, it works as expected!

I'm not skilled enough at bash to fix it though Apparently I am 😄

[tymondesigns]

Actually PR #19 fixes the issue

[fideloper]

Fixed in d8b9026. I'll make a release soon, gotta just test another commit (unrelated) as well.

[tymondesigns]

Cool that dogfooding is possible haha

[fideloper]

Love it :D