- What is webard/nova-zadarma and what does it do?
- webard/nova-zadarma is a Laravel Nova integration for the Zadarma VoIP service. It brings Zadarma telephony data such as calls and account details into the Nova admin panel for quick access and management. It is not a general-purpose telephony abstraction outside Nova, so it only fits teams using Laravel, Nova, and Zadarma.
- How do I install webard/nova-zadarma in a Laravel Nova app?
- Install it with Composer, publish the package config, publish Nova assets, and configure your Zadarma credentials. You also need a publicly reachable HTTPS webhook endpoint for Zadarma callbacks. Validate the install in a sandbox with a test Zadarma account before touching production.
- Which Laravel, Nova, and PHP versions does webard/nova-zadarma support?
- The provided context does not list exact Laravel, Nova, or PHP constraints, so confirm them in the package composer.json and README before adoption. v2.0.0 is a major release, so verify Nova major compatibility and Laravel LTS support explicitly. Build a version compatibility matrix and test the exact combination in a sandbox.
- Is webard/nova-zadarma compatible with Laravel Nova 4 or Nova 5?
- Compatibility with specific Nova majors is not established in the supplied context, so do not assume Nova 4 or Nova 5 support. Check the package composer.json, README, and release notes, then install it in a test Nova app. If you are on an older Nova version, confirm asset publishing and widget behavior before upgrading.
- What breaking changes are in webard/nova-zadarma v2.0.0?
- v2.0.0 is a major-version jump from v1.1.2 with only a high-level changelog, and terms like refactored and cleaned imply possible breaking changes. Review the GitHub diff for config keys, routes, service providers, and widget behavior. Back up published config, update the Composer constraint to ^2.0, republish or merge config, and regression-test call events and the Nova UI.
- How does webhook signature verification work in webard/nova-zadarma?
- Version 2 adds webhook signature verification, and you should treat it as required configuration rather than optional hardening. Confirm the exact algorithm, header name, secret rotation process, and replay protection from the source or vendor. The webhook route must be publicly reachable over HTTPS and correctly excluded from CSRF without weakening auth controls elsewhere.
- How do I migrate from webard/nova-zadarma v1.x to v2.0.0?
- Branch the upgrade and review the v2.0.0 diff before changing your Composer constraint. Back up published config, update to ^2.0, republish or merge config changes explicitly, and update webhook signature settings. Verify widget position and regression-test call events and admin UI behavior in staging before a canary production deploy.
- Is webard/nova-zadarma production ready and what are the risks?
- Production readiness is vendor-claimed, not independently established, and the technical risk is medium. The main concerns are the v2.0.0 major release, dependence on Nova internals, and reliance on an external telephony provider. Pin versions, monitor upstream releases and Zadarma API changes, assign an internal owner, and keep a rollback plan.
- How should I secure the Zadarma webhook endpoint in Laravel?
- Expose the webhook only over HTTPS, verify the Zadarma signature, and exclude the route from CSRF where required. Keep authentication controls intact elsewhere, rotate secrets safely, and confirm replay protection. Keep handlers stateless, queue non-critical work, and monitor signature mismatches, stale config cache, and Zadarma rate limits.
- Does webard/nova-zadarma support multi-tenant or per-user call widgets?
- The supplied context does not establish whether the widget is scoped per user or tenant, so verify this before relying on it. Review how permissions and roles are handled and test multi-tenant behavior in a sandbox. If you need strict tenant isolation, confirm it in the code or add your own authorization layer.