Download the PHP package gldt/raven without Composer
On this page you can find all versions of the php package gldt/raven. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package raven
Short Description Carry Laravel Nightwatch issues into GitHub issues via webhooks.
License MIT
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 raven
🐦⬛ Raven
Carry Laravel Nightwatch issues into GitHub issues, automatically.
Like the ravens of the Night's Watch, this package delivers word from your monitoring to where your team actually works. When Nightwatch detects a new exception or performance problem, Raven opens a GitHub issue. When the problem recurs, Raven reopens it. Your team closes issues in GitHub when the work is done — Raven never closes them for you.
How it works
Nightwatch pushes events to Raven via a signed webhook. Raven verifies the signature, then maps each event to a GitHub action:
| Nightwatch event | What Raven does in GitHub |
|---|---|
issue.opened |
Creates a new issue, stores a Nightwatch ↔ GitHub mapping |
issue.reopened |
Reopens the mapped issue and adds a "this recurred" comment (or creates a fresh issue if no mapping exists yet — e.g. the original predates Raven) |
issue.resolved |
Adds a comment noting it was resolved — leaves the issue open |
issue.ignored |
Adds a comment noting it was ignored — leaves the issue open |
GitHub is the source of truth for "done." Nightwatch drives creation and recurrence; humans close issues in GitHub.
Requirements
- PHP 8.4+
- Laravel 11, 12, or 13
- A GitHub repository to file issues in
- A Nightwatch account with webhooks
Installation
Publish the config (optional — it works with sensible defaults):
Run the migration to create the mapping table:
Configuration
Set these in your .env:
Labels applied to created issues are configurable in config/raven.php:
GitHub token
Create a fine-grained personal access token scoped to the target repository with Issues: Read and write. That's the only permission Raven needs.
Raven authenticates via a token by default. The GitHub calls live behind a
Gldt\Raven\Contracts\GitHubClientinterface, so you can bind your own implementation (e.g. a GitHub App) in a service provider without touching the rest of the package.
Nightwatch webhook
In your Nightwatch application settings, add a webhook pointing at:
Set a signing secret and use the same value for RAVEN_WEBHOOK_SECRET. Raven verifies every request with an HMAC-SHA256 signature, so requests without a valid signature are rejected with a 403.
Multiple environments (one install)
You don't need a separate Raven deployment per environment. A single install can receive webhooks from several Nightwatch environments by adding a source segment to the path — /webhooks/nightwatch/{source} — with a distinct signing secret per source:
Then point each Nightwatch environment at its own URL:
Each request is verified against that source's secret; an unknown or unconfigured source is rejected with a 404. All sources file into the same RAVEN_GITHUB_REPOSITORY, and issues are tagged with an env:<source> label so they stay distinguishable. The bare /webhooks/nightwatch path keeps working and uses RAVEN_WEBHOOK_SECRET.
Adding an environment is just two .env lines (a name in RAVEN_WEBHOOK_SOURCES and its RAVEN_WEBHOOK_SECRET_<NAME>) — no config file to publish, and it survives php artisan config:cache.
Processing
Webhook handling is dispatched to a queued job so the endpoint responds instantly and the GitHub calls (and their retries) happen in the background. Make sure a queue worker is running:
(With the default sync queue connection it runs inline, but a real queue is recommended in production.)
Duplicate protection
Duplicate webhook deliveries and job retries won't open a second GitHub issue for the same Nightwatch issue. Issue creation is serialized per Nightwatch issue id using an atomic cache lock, with the raven_issue_links unique index as the final backstop.
The one residual gap is a process crash after GitHub accepts the new issue but before Raven records the link: a later retry can't see the orphaned issue and will create a fresh one. The unique index prevents a duplicate link row, not a duplicate issue on GitHub. This window is inherent to pairing a non-transactional external API call with a local write, and is the only path to a duplicate.
This relies on your cache store supporting atomic locks — redis, memcached, database, dynamodb, file, and array all do. The only configuration that won't work is sharing the in-memory array store across separate worker processes (not a real-world setup). If you've pointed CACHE_STORE at something custom, make sure it implements Illuminate\Contracts\Cache\LockProvider.
Testing
The suite uses Orchestra Testbench to boot a minimal Laravel app and Http::fake() to assert GitHub calls without hitting the network.
License
MIT
All versions of raven with dependencies
illuminate/contracts Version ^11.0 || ^12.0 || ^13.0
illuminate/support Version ^11.0 || ^12.0 || ^13.0
illuminate/http Version ^11.0 || ^12.0 || ^13.0
illuminate/database Version ^11.0 || ^12.0 || ^13.0
illuminate/bus Version ^11.0 || ^12.0 || ^13.0