Checks: Difference between revisions
From Sunhill Framework Documentation
+Incomplete |
→The check command: +Artisan commands |
||
| Line 15: | Line 15: | ||
This tells the check command only to run checks with the given group id | This tells the check command only to run checks with the given group id | ||
--> | --> | ||
Also see [[Artisan commands]]. | |||
== Writing own checks == | == Writing own checks == | ||
To write your own check just create a class with <code>Sunhill\Basic\Checker\Checker</code> as ancestor. | To write your own check just create a class with <code>Sunhill\Basic\Checker\Checker</code> as ancestor. | ||
Revision as of 07:14, 7 October 2024
| This page is incomplete |
Checks are an unified way to perform sanity checks on the installed system. Initially developed to check if the database tables are consistent you can check all kinds of sanity.
The check command
The framework defines a artisan command called check. It is called via
./artisan check
Note that you have to replace artisan with the name of your artisan application.
The check command has one parameter:
./artisan check --repair
This tells the check not just to report an inconsistency but also to try to repair it.
Also see Artisan commands.
Writing own checks
To write your own check just create a class with Sunhill\Basic\Checker\Checker as ancestor.
<?php
use Sunhill\Basic\Checker\Checker;
class MyCheck extends Checker
{
...
}
