Download the PHP package henrywhitaker3/healthchecks-io without Composer
On this page you can find all versions of the php package henrywhitaker3/healthchecks-io. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download henrywhitaker3/healthchecks-io
More information about henrywhitaker3/healthchecks-io
Files in henrywhitaker3/healthchecks-io
Package healthchecks-io
Short Description A simple PHP healthchecks.io wrapper
License MIT
Homepage https://github.com/henrywhitaker3/PHP-healthchecks.io
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package healthchecks-io
PHP healthchecks.io
This package provides simple methods to interact with the healthchecks.io API.
Installation
Usage
This package provides two classes you can use:
Healthchecks
This class is just used to update a healthchecks.io endpoint.
To create a new instance, you need to pass the UUID for the endpoint you want to update:
Once you have your created a new instance, there are 3 methods to use:
HealthchecksManager
This class can be used to interact with the healthchecks.io management API. Creating a new instance is simple:
You now have several methods you can use:
Contributing
Contributions are welcome, but please write tests for whatever you add. Create a new file in the tests/tests directory with the following structure:
As these tests will need valid credentials and a UUID, you will need to setup a .env file to run tests successfully. Simply copy the .env.example to .env and fill in the relevant details.
