Yes, I am in the app (aka project) directory. The artisan file is in the directory that I am in.
Next...if I run the following command I get output (a list of the available commands):
php artisan list
But if I run this command (purposefully leaving out a required argument), i don't get any error though i expect one:
php artisan make:command
Now my real issue is that I've been trying to develop something that will run be scheduled in app/Console/Kernel.php as a scheduled task, but I need to debug it. So I've been attempting to run it directly and have tried the following command (though I think the tests are useless since artisan seems to be unhappy in its configuration:
php artisan app/Http/Controllers/Cron@getInventory
result: no output
things i've tried
- there is nothing in storage/logs/laravel.log
- the command
find -L ./ -name '*.php' -print0 | xargs -0 -n 1 -P 4 php -l | grep "Errors parsing"uncovers no files that have syntax errors composer updatecomposer installphp artisan optimize
Please offer solutions that will (a) cause php artisan bad:command to complain which hopefully help me (b) validate whether php artisan app/Http/Controllers/Cron@getInventory is the right way to call the command line facing scheduled task controller containing the methods that will run in schedule:run.
from Newest questions tagged laravel-5 - Stack Overflow http://ift.tt/2kC8eQJ
via IFTTT
Aucun commentaire:
Enregistrer un commentaire