forked from getsentry/sentry-php
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
meta: Update readme, remove upgrade guide for now (getsentry#735)
* meta: Update readme, remove upgrade guide for now * fix: CS * fix: Restore upgrade.md * fix: CR
- Loading branch information
Showing
18 changed files
with
64 additions
and
163 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,14 +16,7 @@ | |
|
||
The Sentry PHP error reporter tracks errors and exceptions that happen during the | ||
execution of your application and provides instant notification with detailed | ||
informations needed to prioritize, identify, reproduce and fix each issue. Learn | ||
more about [automatic PHP error reporting with Sentry](https://sentry.io/for/php/). | ||
|
||
## Features | ||
|
||
- Automatically report (un)handled exceptions and errors | ||
- Send customized diagnostic data | ||
- Process and sanitize data before sending it over the network | ||
information needed to prioritize, identify, reproduce and fix each issue. | ||
|
||
## Install | ||
|
||
|
@@ -51,30 +44,18 @@ and [`http-message-implementation`](https://packagist.org/providers/psr/http-mes | |
## Usage | ||
|
||
```php | ||
namespace XXX; | ||
|
||
use Sentry\ClientBuilder; | ||
|
||
require 'vendor/autoload.php'; | ||
use function Sentry\init; | ||
use function Sentry\captureException; | ||
|
||
// Instantiate the SDK with your DSN | ||
$client = ClientBuilder::create(['server' => 'http://[email protected]/1'])->getClient(); | ||
init(['dsn' => '___PUBLIC_DSN___' ]); | ||
|
||
// Capture an exception | ||
$eventId = $client->captureException(new \RuntimeException('Hello World!')); | ||
|
||
// Give the user feedback | ||
echo 'Sorry, there was an error!'; | ||
echo 'Your reference ID is ' . $eventId; | ||
try { | ||
thisFunctionThrows(); // -> throw new \Exception('foo bar'); | ||
} catch (\Exception $exception) { | ||
captureException($exception); | ||
} | ||
``` | ||
|
||
For more information, see our [documentation](https://docs.getsentry.com/hosted/clients/php/). | ||
|
||
|
||
## Integration with frameworks | ||
|
||
Other packages exists to integrate this SDK into the most common frameworks. | ||
|
||
### Official integrations | ||
|
||
The following integrations are fully supported and maintained by the Sentry team. | ||
|
@@ -95,15 +76,11 @@ The following integrations are available and maintained by members of the Sentry | |
|
||
## Community | ||
|
||
- [Documentation](https://docs.getsentry.com/hosted/clients/php/) | ||
- [Documentation](https://docs.sentry.io/error-reporting/quickstart/?platform=php) | ||
- [Bug Tracker](http://github.com/getsentry/sentry-php/issues) | ||
- [Code](http://github.com/getsentry/sentry-php) | ||
- [Mailing List](https://groups.google.com/group/getsentry) | ||
- [IRC](irc://irc.freenode.net/sentry) (irc.freenode.net, #sentry) | ||
|
||
|
||
Contributing | ||
------------ | ||
## Contributing | ||
|
||
Dependencies are managed through composer: | ||
|
||
|
@@ -116,79 +93,3 @@ Tests can then be run via phpunit: | |
``` | ||
$ vendor/bin/phpunit | ||
``` | ||
|
||
|
||
Tagging a Release | ||
----------------- | ||
|
||
1. Make sure ``CHANGES`` is up to date (add the release date) and ``master`` is green. | ||
|
||
2. Create a new branch for the minor version (if not present): | ||
|
||
``` | ||
$ git checkout -b releases/2.1.x | ||
``` | ||
|
||
3. Update the hardcoded version tag in ``Client.php``: | ||
|
||
```php | ||
namespace Sentry; | ||
|
||
class Client | ||
{ | ||
const VERSION = '2.1.0'; | ||
} | ||
``` | ||
|
||
4. Commit the change: | ||
|
||
``` | ||
$ git commit -a -m "2.1.0" | ||
``` | ||
|
||
5. Tag the branch: | ||
|
||
``` | ||
git tag 2.1.0 | ||
``` | ||
|
||
6. Push the tag: | ||
|
||
``` | ||
git push --tags | ||
``` | ||
|
||
7. Switch back to ``master``: | ||
|
||
``` | ||
git checkout master | ||
``` | ||
|
||
8. Add the next minor release to the ``CHANGES`` file: | ||
|
||
``` | ||
## 2.1.0 (unreleased) | ||
``` | ||
|
||
9. Update the version in ``Client.php``: | ||
|
||
```php | ||
namespace Sentry; | ||
|
||
class Client implements ClientInterface | ||
{ | ||
const VERSION = '2.1.x-dev'; | ||
} | ||
``` | ||
|
||
10. Lastly, update the composer version in ``composer.json``: | ||
|
||
```json | ||
"extra": { | ||
"branch-alias": { | ||
"dev-master": "2.1.x-dev" | ||
} | ||
} | ||
``` | ||
|
||
All done! Composer will pick up the tag and configuration automatically. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.