- What is ladumor/one-signal used for?
- ladumor/one-signal is a thin Laravel wrapper around OneSignal's notification APIs. It lets Laravel applications send push notifications to devices, users, and segments and manage notifications without hand-rolling HTTP calls, config, and payload formatting. It is an infrastructure adapter, not a full notification orchestration platform. Preference management, templating, compliance, retries, and delivery observability remain application-owned.
- How do I install and configure ladumor/one-signal in Laravel?
- Install it with Composer, publish the package config if the package provides one, and set your OneSignal app ID and API key through environment-based configuration. Then send a test notification to an internal device or segment in a non-production OneSignal app. The package is intended to minimize setup, but you should still confirm the exact config keys and authentication model against the package source and OneSignal's current API.
- Which Laravel and PHP versions does ladumor/one-signal support?
- The provided evaluation does not list specific Laravel, PHP, or Guzzle version constraints. Check the package's composer.json, release tag, and changelog before adopting it, because a recent release alone does not prove compatibility or API coverage. Verify the constraints against your application's Laravel and PHP versions as part of a timeboxed spike.
- Can ladumor/one-signal send push notifications to segments, users, and devices?
- The package overview says it can target devices, users, and segments and create and manage notifications. That covers common push campaigns, but you should verify whether the wrapper exposes every OneSignal endpoint you need, such as topics, subscriptions, templates, scheduled messages, outcomes, and webhooks. If coverage is partial, you may need direct HTTP calls for advanced cases, which creates a second integration path to maintain.
- Does ladumor/one-signal support queued, batch, scheduled, or retried notifications?
- The evaluation does not confirm support for queued, batch, scheduled, or retried sends, rate-limit handling, or idempotency. You can wrap package calls in Laravel jobs and queues, but retry policy, idempotency keys, and rate-limit backoff would then be application-owned. Confirm the wrapper's behavior before relying on it for high-volume or guaranteed delivery.
- Can I use ladumor/one-signal with multiple OneSignal apps or tenants?
- Multi-tenant or multiple OneSignal app support is not confirmed in the provided information; the package may be single-app only. If you need per-tenant app IDs or credentials, verify how configuration is resolved at runtime and whether it can be overridden safely. Otherwise, keep tenant-specific OneSignal configuration in your own adapter layer.
- How does ladumor/one-signal handle errors and logging?
- Error handling is not described in the provided evaluation, so verify whether failures surface as exceptions, return codes, or logs. You should map those failures to your application's internal failure states and avoid letting raw OneSignal payloads or errors leak across the codebase. A wrapper interface plus explicit exception translation makes this easier to test and replace.
- Is ladumor/one-signal actively maintained and safe for production?
- Treat it as a low-adoption package: it has roughly 123 stars and zero dependents, which means limited community validation and elevated single-maintainer or abandonment risk. MIT licensing is favorable because it reduces fork and vendor risk. Run a non-production spike, pilot behind a feature flag, and keep the ability to fork or replace the wrapper.
- How should I test ladumor/one-signal before deploying to production?
- Test it in a non-production environment with a sandbox OneSignal app and internal test devices. Verify sends to devices, users, and segments, and check error behavior, logging, secret handling, and queued sends if you use them. If possible, add contract tests against the OneSignal sandbox so API or auth changes are caught before production.
- What are alternatives to ladumor/one-signal for Laravel OneSignal integration?
- Alternatives include direct OneSignal HTTP calls through Laravel's HTTP client, OneSignal's own SDKs, or a more actively maintained Laravel wrapper. The best choice depends on which OneSignal endpoints you need, the API version and auth scheme supported, and how much maintenance risk you can accept. Regardless of choice, depend on an internal NotificationGateway interface rather than the package facade so you can swap implementations later.