Weave Code
Filagora Push Laravel Package
filagora/filagora-push
Filagora Push is a Laravel package for sending and managing push notifications. It provides a clean API for configuring providers, composing messages, and dispatching alerts to users, helping you add reliable notification delivery to your app with minimal setup.
Web push for Filagora: browser subscriptions with the safety checks, stale clean-up, privacy, and push alerts for mentions, thread updates and private messages.
Frequently asked questions about Filagora Push
- What Laravel and PHP versions does filagora/filagora-push support?
- The initial assessment covers v0.1.0 and does not state exact Laravel or PHP version constraints, so check the package's composer.json before installing. Treat the API and database schema as pre-1.0 and subject to change. Test the package against your application's Laravel version in staging before production use.
- How do I install and configure Filagora Push in a Laravel app?
- Install the package with Composer, then publish its configuration and migration files using Artisan. Configure allowed_hosts and the VAPID or web-push credentials required by your sending package. Run the migration only after confirming it owns the push_subscriptions table and index set.
- Which web push sending package and VAPID setup does Filagora Push assume?
- Filagora Push complements a web-push sender package rather than replacing it; delivery mechanics remain with the sender. The assessment does not name a specific sender package, and VAPID credentials are configured through that sender. Confirm the sender's requirements and your VAPID keys before enabling alerts.
- Why are all my push subscriptions being refused or rejected?
- Subscriptions can be refused when allowed_hosts is misconfigured because the package enforces HTTPS-only endpoints, the default port, and a host allowlist. It also refuses endpoints when the URL parser and HTTP client interpretations disagree. Default-port-only validation may reject legitimate nonstandard endpoints, so review your host and port policy carefully.
- Do I need to disable the sending package's push_subscriptions migration?
- Yes, this package owns the push_subscriptions model and migration, while the sending package should not also own the table. Disable or remove the sender's push_subscriptions migration to avoid conflicts. Verify index parity with any existing table before running migrations in production.
- What user model contract do PushNotifier and PushPreferences expect?
- PushNotifier and PushPreferences work with any user or person model, but your model must satisfy the contract expected by those classes. PushPreferences defaults to AllowsAllPush, which needs product and privacy review for your application. Map PushCategory values to your preference rules and alert listen switches explicitly.
- Can I use mention, thread update, and private message alerts without Filagora Forums or Messages?
- The mention, followed-thread, and private-message alerts depend on filagora-forums and filagora-messages. Enable those listeners only when the corresponding packages are installed and configured. Otherwise, optional module coupling can cause runtime failures.
- How are queued notifications, retries, and stale subscription clean-up handled under load?
- The package expects queue workers and adds writes such as last_used_at during delivery plus cleanup jobs for stale subscriptions. The initial assessment does not detail retry, rate-limit, or 404/410/429/5xx handling, so verify those behaviors in the sender and your queue configuration. Test pruning and concurrent delivery under load before relying on it in production.
- Does Filagora Push support privacy export and erasure for push subscriptions?
- Filagora Push includes privacy contributor support for export and erasure, which is a positive sign for production readiness. You must verify that it integrates with your host application's privacy framework and data-retention process. Test export and erasure flows against real subscription data before launch.
- Is filagora/filagora-push production-ready, and how should I test endpoint validation?
- Treat v0.1.0 as pre-1.0, with API and schema changes possible before a stable release. The endpoint validation logic is high-risk security code, so add dedicated tests for HTTPS-only enforcement, host allowlists, default ports, resync restrictions, and parser/client disagreement cases. Run those tests in staging against your Laravel version and routing conventions before deploying.
Weaver
How can I help you explore Laravel packages today?