- How do I install gnello/laravel-mattermost-driver in a Laravel app?
- Install it with Composer using composer require gnello/laravel-mattermost-driver. On modern Laravel versions the service provider and facade are auto-discovered, so no manual registration is needed. Then publish the config file with php artisan vendor:publish and add your Mattermost webhook URL or access token to your .env file. Most teams can get a test message into a Mattermost channel in well under a day.
- Which Laravel, PHP, and Mattermost versions does this driver support?
- The package targets Laravel applications from the 5.5 era through modern releases, but the officially tested version ranges are not prominently documented. Before committing, verify three axes: your Laravel major version, your PHP runtime, and your Mattermost server's API contract. Because the code footprint is small, a minor fork to patch a version constraint is a realistic option if the package lags your stack.
- Is this a Laravel notification channel or just a facade wrapper?
- It follows the canonical Laravel package pattern: a service provider, a facade, and a publishable config file, with a channel-style class for sending messages. In practice most usage is direct facade or channel-class calls rather than a drop-in Laravel NotificationChannel, so confirm the exact surface in the source before designing around it. Wrapping it behind your own Notifier interface keeps your application decoupled and makes swapping drivers later trivial.
- Does it support Mattermost incoming webhooks and bot or personal access tokens?
- Yes. The driver supports the incoming webhook path for simple channel posts and also accepts access tokens, delegating broader REST API operations to the upstream gnello/php-mattermost-driver. Incoming webhooks are the lowest-friction option for chatops alerts and deploy notifications. Bot or personal tokens are the better fit when you need to target users or channels dynamically.
- How do I configure the Mattermost webhook URL and credentials?
- Run php artisan vendor:publish to generate the package config file, then drive the values from environment variables rather than hardcoding them. You typically set the incoming webhook URL for simple posts, or a personal or bot access token plus base URL when using the REST API. Keep these values out of version control and set them per environment, so switching or rolling back is a config change rather than a code change.
- Can Mattermost notifications be queued or sent asynchronously?
- There is no documented native queue integration, so the package's calls are effectively synchronous HTTP requests. The practical pattern is to dispatch your own Laravel queued job or use a queued notification that calls the driver, giving you retries and backoff for free. This also keeps slow Mattermost API responses off your request cycle during deploys and alert storms.
- How are Mattermost rate limits and transient API errors handled?
- Error handling is not a documented strength of this package, and the upstream driver surfaces API responses rather than providing built-in retry semantics. Treat HTTP 429 responses and 5xx errors as expected and handle them yourself with Laravel's retry helpers or queued jobs with backoff. Add structured logging around failures so a silently dropped chatops alert does not go unnoticed.
- Is this package safe to use in production and is it still maintained?
- The main risk here is project maturity, not engineering complexity: it is a single-maintainer package with a small user base and limited visibility into test coverage. The Apache-2.0 license is a genuine mitigant, because the code is small enough that forking and maintaining it internally is realistic rather than a rewrite. Pin the package and its upstream dependency in composer.lock, wrap it behind an internal interface, and budget a modest amount of ongoing ownership.
- How do I test Mattermost notifications without spamming real channels?
- Create a dedicated test channel in your Mattermost instance and point a non-production webhook at it during development. In automated tests, mock the facade or fake the underlying HTTP calls so your suite never hits the Mattermost API. Also write a couple of integration tests that assert error handling, since failure behavior is the part most likely to bite you in production.
- What are the alternatives to this Laravel Mattermost driver?
- The simplest alternative is calling Mattermost incoming webhooks directly with Laravel's HTTP client, which removes a dependency for basic channel posts. If you need the full REST API, the upstream gnello/php-mattermost-driver can be used without the Laravel wrapper. Teams migrating from Slack or Microsoft Teams often introduce this package as a secondary channel behind an internal interface, prove parity on low-stakes alerts, then switch production traffic over with an env revert as the rollback path.