- How do I install parse/php-sdk in a Laravel app?
- Install it with composer require parse/php-sdk. The package uses PSR-4 autoloading under the Parse namespace. It does not ship a Laravel service provider or facade, so you create your own config entry, singleton client initialization, and any adapters you need.
- Is parse/php-sdk a Laravel package with a service provider?
- No, it is not a Laravel package; it is a framework-agnostic REST client for Parse Server. It can be used inside Laravel, but you must write the integration glue yourself, including config, singleton setup, and exception mapping. The SDK's static client state can sit awkwardly with Laravel's container scoping and parallel tests.
- Which PHP and Laravel versions does parse/php-sdk support?
- Release 2.4.0 explicitly adds PHP 8.3 support, so treat PHP 8.3 as supported and tested. PHP 8.4 is unverified, and current Laravel major versions are unverified. Confirm in your own CI before committing to the integration.
- Is parse/php-sdk a good fit for a greenfield Laravel backend?
- If Parse Server is already your system of record, the SDK is a good bridge for Laravel admin, reporting, or back-office work. For a greenfield Laravel app, it is a poor fit because you trade migrations, transactions, joins, and database constraints for a schemaless remote API. Use it as a narrow anti-corruption-layer client, not as your primary persistence layer.
- How do I use parse/php-sdk with multiple Parse apps or tenants?
- The SDK initializes client credentials as static global state, which makes multiple Parse apps or tenants difficult. Long-lived queue workers, parallel tests, and per-tenant configuration all become harder. If you need many Parse apps in one Laravel process, treat this as a likely blocker.
- Does parse/php-sdk support transactions or atomic batch writes?
- No. Parse batch operations are not atomic, and the SDK does not provide cross-call transactions. Partial writes are a real failure mode, so design idempotency keys, reconciliation jobs, and compensating actions where needed.
- How should I handle the Parse master key in Laravel?
- Keep the Parse master key server-side only, loaded from environment or secrets management, and never expose it to browser or mobile clients. A leak or accidental client-side use is the highest-severity risk in this integration. Restrict which code paths can use it and log administrative operations.
- Can I use Laravel Http::fake or Telescope with parse/php-sdk?
- No, the SDK uses raw cURL rather than Guzzle, so calls are invisible to Laravel's Http::fake, Telescope, and generic retry or circuit-breaker middleware. You need to build your own observability and resilience decorator around the client. Plan for logging, timeouts, retries, and metrics explicitly.
- Does parse/php-sdk support Live Queries and Cloud Code?
- The SDK supports Cloud Functions, but it does not support Parse Live Queries. If business logic already lives in Parse Cloud Code, be careful not to duplicate the same rules in Laravel services. Decide where each rule is authoritative before you build.
- What is the maintenance status and license of parse/php-sdk?
- Maintenance reads as caretaker-level: the sole 2024 release is a runtime-compatibility patch, with around 808 stars and no tracked dependents, so you own the roadmap. The license is reported as NOASSERTION because GitHub could not classify the LICENSE file. Treat that as a legal review gate before production use.