- How do I install mortezamasumi/fb-sms in a Laravel application?
- Install it with Composer using composer require mortezamasumi/fb-sms, then follow the package's standard Laravel setup, which typically means publishing a config file and providing gateway credentials through environment variables or a secret store. Check the package's composer constraints before installing, especially if your app is not on Laravel 13. The v5.3.0 release note only states Laravel 13 support, so confirm compatibility with your current PHP and Laravel versions first.
- Does mortezamasumi/fb-sms support Laravel 13?
- Yes, the v5.3.0 release note explicitly lists support for Laravel 13. However, the supplied context does not confirm whether that release also drops older Laravel or PHP versions. Pin the package version and review the composer diff before updating, because a caret constraint may absorb v5.3.0 automatically.
- How do I configure fb-sms credentials in Laravel?
- The package is positioned as a configurable Laravel SMS integration, so setup should follow the usual pattern: publish the package config and supply the fb-sms account credentials via environment variables or your secret manager. Do not commit credentials to source control. Verify the exact config keys against the package README or config file during a short integration spike.
- Can I use fb-sms to send OTP codes and alerts?
- Yes, the package is described for SMS notifications, OTPs, and alerts in Laravel and PHP applications. OTP delivery is time-sensitive, so test latency, retry behavior, and provider rate limits before relying on it in production. Also confirm sender-ID and regulatory registration requirements for the destination country, since those can block OTP delivery independently of the package.
- Should I send SMS through a queued job with fb-sms?
- Yes, sending SMS through a Laravel queued job is the safer default because it keeps external gateway latency out of the request cycle and gives you retry and failure handling. Keep phone numbers and message bodies in mind as personal data when configuring queue payloads and failed-job storage. Wrap the package behind an application-owned SMS sender interface so queued jobs depend on your abstraction, not the vendor class.
- Is mortezamasumi/fb-sms safe to use in production?
- It can be a reasonable outbound-edge dependency, but the supplied assessment is low-to-moderate confidence because no source review, test coverage, or issue-tracker analysis was provided. The main risks are a single maintainer, one-commit releases, and dependency-resolution changes from the Laravel 13 compatibility release. Pin the version, review the diff, wrap it behind your own interface, and validate logging and PII handling before production use.
- Does fb-sms log phone numbers or SMS message content?
- The supplied context does not confirm the package's logging behavior, so treat this as an item to verify during your spike. SMS payloads contain phone numbers and message bodies, both of which are personal data. Check debug logs, queue payloads, and failed-job records, and add redaction or disable verbose logging if payloads are exposed.
- How can I test fb-sms SMS sending without hitting the real gateway?
- The review context does not include test coverage data or a documented fake for this package, so plan to isolate it behind your own SmsSender interface and stub that interface in unit tests. For an end-to-end check, use any sandbox or test credentials the fb-sms provider offers if available. Keep one real staging send as an acceptance test, because gateway behavior and delivery reports live outside the package.
- What are the alternatives to fb-sms for Laravel SMS?
- Alternatives include Laravel's notification system with a provider-specific SMS channel, other Laravel SMS gateway packages, or a small custom HTTP client for your chosen provider. The right choice depends less on the wrapper and more on gateway reliability, sender-ID support, country coverage, pricing, and delivery-report semantics. If you already use Laravel notifications, a custom channel may be simpler than adding another package.
- Is mortezamasumi/fb-sms actively maintained?
- The v5.3.0 release, which adds Laravel 13 support, signals that the maintainer intends to keep the package alive across framework upgrades. That reduces abandonment risk compared with a package with no recent releases. However, it is a single-author package with one-commit releases and no visible CI governance in the supplied note, so keep the bus-factor risk in mind and keep the integration swappable.