I'm new to laravel and I'm trying to understand some of the stuff that the artisan command line tool is doing but I can't seem to find a clear explanation.
When I type in:
php artisan help view:publish
It gives me the syntax and different flags I can throw, but no explanation of what the command actually does.
When I look on laravel's website to read the documentation on the artisan tool I get an incredibly brief explanation of how to use the tool but nothing on any of it's commands and the development section of the docs show's how to build command but not what they do.
I've searched around online and I've not found anything that helps. I'm sure I'm wearing my frustration glasses and I'm missing some obvious sources, but it's hard to take those glasses off sometimes.
Does anyone know where I can find manual so I can rtf out of it??
Try the aritsan command: $ php artisan list
It will give you a synopsis of all of the built-in (and custom-made) commands. In the case of view:publish, this is what it reports:
view
view:publish Publish a package's views to the application
Related
I find the Symfony Console documentation to be quite good. In clear language, it explains how to use Symfony Console to write console commands in PHP, including how to take user input, how to render output, and even how to write tests for these console commands.
However, the documentation doesn't seem to explain how to run these tests. Assuming one has written a test like CreateUserCommandTest.php, which they provide as an example, how would they run it?
I need to make a tool to Browser test my production system. I have read up all about Laravel Dusk and it seems like a perfect tool. However, I need to run tests automatically via schedule and have a dashboard with the results.
I can easily run the command php artisan dusk from the code using the Scheduler, however, how can I get the results? Is there a better option than simply parsing the Console Output from that command? Ideally I would have a way of getting the status of each test (whether it passed or failed) to be able to log, process and display all that information.
The Dusk documentation hasn't got any more information on running the tests programatically, it only has instructions to run via php artisan dusk.
Has anyone encountered this?
Thank you!
The way I have achieved what I needed is to use the command options for dusk/phpunit.
I used --filter=MyTestClass to single out which test I wanted to run, and --log-junit log.log to log the results for that test, which I then parsed via code as well to fetch the results. This allowed me to build a fully custom dashboard that was able to run each test individually, report the results, send notifications etc.
Not the prettiest solution, but it worked well for what I needed. If anyone encounters better way to achieve that (or just use Dusk in general as a browser/scraper outside phpunit) please do post a comment/answer!
I am the sole person in charge of a website that keeps track of records that other employees submit and compiles them into nice spreadsheets so that non-technical users can easily read them.
The other guy who used to work here quit unexpectedly, and I have to make a small, one-line change to the PHP code that he wrote, the problem is, when I edit the code, it does not seem to change anything. For example, I can completely delete the code that displays an error message, but that error message will still show up. There are other parts of the project that I CAN modify, like XML files and python programs, but the PHP does not seem to care if it is modified.
I vaguely remember a command like 'php artisan serve' but that doesn't seem to help either
After googling the problem, I came across several other commands like 'npm run production' and 'php artisan optimise' but those didn't work either.
Thanks for your help
Are you changing the code directly on the server? Or are you trying it local first? Is the change on a view-file?
Try php artisan cache:clear. It should clear all the caches and probably show your changes.
I'm having a hard time finding out a nice clean way to generate docs. PHPdoc still seems a little scattered.
In any case, I can't seem to get it to generate source code with highlighting, which I seem to have a compulsive need for - being a stack overflow user :D
Here's the command I'm running:
phpdoc project:run --directory /var/www/symbiostock/wp-content/themes/symbiostock/ --target /var/www/PhpDocumentor-output/ --template responsive --sourcecode --force
Without the --force parameter, it tells me I have too many arguments. With it, it just rolls through everything without any apparent generating of highlighted source code.
Is this template sensitive? Only some templates do source inclusion?
I find documentation on phpdocumentor slightly deficient in a few areas (ironically) so I thought I might just post the question.
I don't think that 2.x has implemented the --sourcecode option yet. It's available in 1.x, but 1.x does not handle new features added in PHP 5.3 and beyond.
Are there any decent PHP libraries available for accessing SVN repositories? Right now I just have some scripts executing commands to the command line and parsing the feedback, I'd love to find something less dependent on the command line and more tightly integrated. Any ideas?
A quick google search;
http://au2.php.net/svn
http://php-svn-client.tigris.org
http://pecl.php.net/package/svn
I think you are fine just the way you are. WebSvn, from websvn.tigris.org, the Subversion people themselves, does it the same way. I also shell out to the command line and parse the responses in my app BugTracker.NET.