countless-integers / laravel-health-check
Customizable health-checks Laravel applications
Installs: 12 890
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 0
Open Issues: 6
Requires
- php: ^8.2
- ext-json: *
- illuminate/config: ^10|^11
- illuminate/container: ^10|^11
- illuminate/database: ^10|^11
- illuminate/http: ^10|^11
- illuminate/support: ^10|^11
Requires (Dev)
- aws/aws-sdk-php-laravel: ^3.9
- mockery/mockery: ^1.6
- orchestra/testbench: ^8|^9
- phpunit/phpunit: ^9.6|^10.5|^11.1
- vimeo/psalm: ^5.23.1
Suggests
- aws/aws-sdk-php-laravel: Needed for AWS service setup checks
- dev-master
- 3.0.0
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- 1.1.0
- 1.0.1
- 1.0.0
- 0.1.0
- 0.0.4
- 0.0.3
- 0.0.2
- v0.0.1
- dev-dependabot/composer/vimeo/psalm-tw-4.28or-tw-5.0
- dev-chore/upgrade-min-php-version
- dev-chore/update-badge
- dev-chore/add-testing-matrix
- dev-chore/swtich-to-gh-actions
- dev-chore/compatibility-with-php8
- dev-dependabot/add-v2-config-file
This package is auto-updated.
Last update: 2024-10-15 16:33:47 UTC
README
Installation
PHP 8.0+ is required.
$ composer require countless-integers/laravel-health-check
$ php artisan vendor:publish
Configuration
Package publishes its config to your project's and it can be found at config/health-check.php
.
Gotchas
- even though all checker classes are optional, all the libraries that they depend on are not
- no aliases for check, instead check class names are used
Configuration keys
checkers
List of checker classes that should run on service check. By default, all available checkers are included in the exported configuration. You can disable the ones you don`t want by removing their key from this array.
Some of the checkers can or need to be configured. List of available configuration options:
extended_checks
Same format as checkers
, but these checks are only run if the endpoint was called with extended
option (see below).
Other options
Contribution guidelines
PR-s need to:
- include a description explaining the problem and solution
- pass static analysis (uses psalm, ran on CI)
- pass test (uses codeception, ran on CI)
Running tests
You can use composer scripts:
-
to run all tests:
$ composer test
-
to run only unit tests:
$ composer unit-test
-
to run only unit tests with test coverage:
$ composer unit-test-coverage
-
to view the coverage report (mac only):
$ composer coverage-report
-
to run static analysis:
$ composer static-analysis
-
to run all:
$ composer qa