Weave Code
Sdk Php Laravel Package
mirafive/sdk-php
A PHP SDK for integrating Mirafive services into your applications. Install via Composer, configure your credentials, and interact with the API through a simple, consistent client designed for PHP and Laravel projects.
MIRA FIVE SDK for PHP
Frequently asked questions about Sdk Php
- What is mirafive/sdk-php used for?
- It is a lightweight PHP client for integrating Mirafive services into PHP or Laravel applications. It provides typed request and response handling for event ingestion and feature-flag evaluation. It is framework-agnostic rather than a Laravel-only package, so Laravel wiring may need to be added by your application.
- How do I install mirafive/sdk-php with Composer?
- Install it through Composer using the package name mirafive/sdk-php, then configure your Mirafive credentials in your application bootstrap or config layer. The provided overview describes Composer installation and configurable credentials but does not prescribe a single configuration file. For Laravel, you would typically wrap that configuration in a service provider or config entry.
- Does mirafive/sdk-php support Laravel auto-discovery, facades, or a service provider?
- The provided release information does not document a Laravel service provider, facade, publishable config, or package auto-discovery. The SDK is described as framework-agnostic, so Laravel adoption likely requires a thin adapter for container bindings, configuration, cache, HTTP client, and lifecycle flush. Confirm with the vendor before assuming drop-in Laravel integration.
- Which PHP and Laravel versions are supported by mirafive/sdk-php?
- The provided overview does not state explicit PHP or Laravel version constraints. It is Composer-installable and standards-oriented, using PSR-friendly HTTP and optional PSR-16 caching, but tested PHP and Laravel version ranges are not listed. Validate compatibility in your target Laravel version before adopting it.
- How do I configure credentials and the Mirafive API host?
- The SDK is described as having simple setup with configurable credentials. The evaluation also references API keys, host configuration, and default-host overrides that should be managed per environment. The exact configuration keys and override mechanism are not detailed in the provided text, so check the package source or vendor docs.
- How should I handle event batching and flush in Laravel queue workers or Octane?
- Events use buffered track and identify calls, an immediate send method, and lifecycle flush, with batches bounded at 1,000 events or 1 MiB. In request/response Laravel apps, wire flush into termination or a queued delivery path. In queue workers, Octane, and other long-running processes, use explicit flush points rather than relying only on shutdown or destructors.
- What happens in consentless mode if an identifier is refused?
- In consentless mode the SDK refuses identifiers as a safety posture. The provided evaluation lists exception, dropped event, or reported result as possible behaviors that must be confirmed, so do not assume the exact outcome without checking the implementation. Design consent-state mapping explicitly because identified event shapes may need to change.
- How does the circuit breaker affect production reliability?
- The SDK has a 3-second per-flush deadline, a 1-second connect timeout, and a 30-second circuit breaker after a failed flush or segment lookup. The breaker is shared through PSR-16 cache, so it can suppress traffic across processes. That may be acceptable for analytics but should be reviewed and made observable for flag-dependent critical paths.
- How should I test mirafive/sdk-php before using it in production?
- The flag evaluator reportedly passes shared Mirafive fixtures and supports ETag revalidation, segment lookups, server-counted exposures, and an escaped bootstrap block. Treat fixture success as necessary but not sufficient; validate with real flag documents, stale-cache behavior, and browser bootstrap security checks. Also test your Laravel adapter, flush lifecycle, consent mapping, and circuit-breaker visibility.
- Is mirafive/sdk-php production-ready and what are the maintenance concerns?
- Version 1.0.0 is a first release with a declared API but no migration history or prior assessment in the provided material. It is best treated as a controlled pilot rather than an assumed enterprise-standard Laravel integration. Confirm maintenance expectations, supported versions, and Laravel-specific support with the vendor.
Weaver
How can I help you explore Laravel packages today?