- Is octopush/sms-bundle a Laravel package?
- No. octopush/sms-bundle is a Symfony bundle for integrating the Octopush SMS API, and the Bundle suffix signals Symfony heritage rather than native Laravel support. It uses Symfony dependency injection and YAML configuration, so Laravel applications should treat it as an API reference or adapter source, not a drop-in package.
- Can I install octopush/sms-bundle in a Laravel application with Composer?
- Composer may install it if PHP and Symfony dependency constraints allow, but installation does not make it Laravel-native. It may require Symfony bundle registration or symfony/framework-bundle, and those dependencies can conflict with a Laravel app. Inspect composer.json at the 2.0.0 tag for PHP and Symfony constraints before adding it.
- Does octopush/sms-bundle support Laravel 10 or Laravel 11?
- There is no confirmed Laravel version support in the provided context, and the package is described as suitable for legacy Symfony 3/4-era applications. Laravel ships Symfony components, but requiring full Symfony bundle registration remains a red flag. Verify declared constraints rather than assuming Laravel auto-discovery or compatibility.
- How do I configure Octopush credentials in octopush/sms-bundle?
- The bundle uses YAML-based configuration for Octopush credentials, default sender name, and country settings. In Symfony, those values are configured once and injected through the service container. In Laravel, you would normally use config/services.php and environment variables inside your own adapter instead.
- How do I send an SMS with octopush/sms-bundle?
- The bundle exposes a service API for sending single or bulk SMS messages. In Symfony you would retrieve that service from the container and call it from application code. In Laravel, wrap the relevant call logic behind an internal SMS contract so bundle classes do not leak into domain code.
- What changed in octopush/sms-bundle 2.0.0 for the Octopush v2 API?
- Version 2.0.0 appears to be a major release that swaps the package to the newer Octopush API version. The evaluation notes that authentication models, endpoint hosts, and response schemas often change in such migrations, so verify the API key or header model, base URL, and send response shapes. Also check whether PHP, Symfony, and test constraints were raised, because the release may otherwise leave the bundle structure untouched.
- Does octopush/sms-bundle support delivery receipts or webhooks under Octopush v2?
- That is not confirmed in the provided context and needs explicit verification against the 2.0.0 code and Octopush v2 documentation. Do not assume delivery-receipt or webhook support based only on the version bump. If you need status callbacks in Laravel, plan to implement webhook handling in your own application layer.
- Is octopush/sms-bundle safe for production Laravel apps?
- The technical risk remains high because the package has near-zero community validation, weak test posture, possible abandoned maintenance, and likely Symfony version coupling. A v2 migration is also a classic point for credential, endpoint, and response-schema changes that must be verified. Treat it as a reference implementation rather than a critical dependency, and audit credentials, logging, and PII handling before production use.
- What license applies to octopush/sms-bundle, and can we fork it?
- The provided context does not state the license, so confirm it directly in the repository before depending on or forking the package. If the license permits, forking only the Octopush v2 request and response logic into your own adapter is safer than adopting the Symfony bundle. Keep your internal SMS interface as the ownership boundary.
- What is the best Laravel approach instead of using octopush/sms-bundle?
- Build a Laravel-native OctopushSmsSender using the Http facade, config/services.php, environment variables, queued jobs, and typed provider exceptions. Use the package as a time-boxed reference for Octopush v2 auth headers and payload shapes, then test your adapter with Http::fake and contract tests. If an official Octopush v2 SDK exists, wrap it behind the same internal SMS contract so the provider remains replaceable.