- How do I install misaf/laravel-sms-gateway-kavenegar in Laravel?
- Install it with Composer using composer require misaf/laravel-sms-gateway-kavenegar, then follow the laravel-sms-gateway setup to register the driver. Publish any package configuration and add Kavenegar credentials through environment variables. Before using v2.0.0 in production, review the changelog and diff because it is a major release.
- What Laravel and PHP versions does this Kavenegar SMS package support?
- The provided information does not list exact Laravel and PHP version constraints. Check the package composer.json, README, and v2.0.0 changelog before upgrading. Validate compatibility in a branch against your application's Laravel and PHP versions.
- How do I configure Kavenegar credentials and sender number in Laravel?
- Configuration is typically done by publishing the package config and setting Kavenegar API credentials and sender details in environment variables. Keep secrets out of source control and follow your existing Laravel secret-management standards. For v2.0.0, diff published config files instead of overwriting production settings.
- Can I use this package to send OTPs and verification codes in Laravel?
- Yes, it is intended as a Kavenegar driver for laravel-sms-gateway so Laravel apps can send SMS for notifications, one-time passwords, verification codes, and alerts. Keep OTP and alert logic in your application or notification classes, with the package wired behind a small internal SMS interface. Test send and failure paths before production rollout.
- What changed in v2.0.0 and is it a breaking change?
- v2.0.0 is a major release, which usually signals possible breaking changes, but the provided release notes only link to a changelog comparison. Review the changelog and diff for changes to config keys, namespaces, public APIs, Laravel/PHP support, and Kavenegar behavior. Keep production on v1 until that review and staging validation are complete.
- Is this package compatible with Laravel notifications and queues?
- It is designed for Laravel and should fit Laravel notification and queue patterns through the laravel-sms-gateway integration. Confirm queue-worker compatibility and whether retry, delivery-report, or error-handling behavior changed in v2.0.0. Run contract tests for queued sends and failures.
- How do I migrate from v1.0.0 to v2.0.0 safely?
- Keep production on your current v1 constraint, create an upgrade branch, and update Composer to v2.0.0 there. Review the changelog and diff, re-publish or diff configuration files, and check namespaces, facades, config keys, and method signatures. Run existing SMS tests plus send, error, and queue tests, then validate with staging Kavenegar credentials before a canary rollout.
- Does this package handle delivery reports, retries, or error handling?
- The provided information does not confirm how v2.0.0 handles retries, delivery reports, or error handling. Inspect the source, changelog, and tests, and verify behavior against your Kavenegar account type and API version. Operationally, keep a runbook for SMS failures and provider escalation.
- Is misaf/laravel-sms-gateway-kavenegar actively maintained and safe for production?
- Maintenance risk depends on maintainer activity, test coverage, release discipline, and license terms, none of which are evidenced in the provided data. Treat it as a critical third-party integration with an owner, upgrade cadence, and monitoring. Check recent releases, tests, license, and Kavenegar API compatibility before commercial production use.
- What are alternatives to this package for sending SMS via Kavenegar in Laravel?
- Alternatives include using Kavenegar's official API or SDK directly, writing a small custom HTTP client, or choosing another laravel-sms-gateway driver. If you want to avoid lock-in, depend on an internal SMS interface or Laravel notification channel and place this package behind it. Compare maintenance, testing, and provider support before switching.