- Is gally/gally-standard a Laravel package?
- No. Despite appearing in Laravel-oriented package searches, gally/gally-standard is the standard data-model and configuration layer of Gally, a Symfony-based headless searchandising suite built on Doctrine, API Platform, and Elasticsearch or OpenSearch. It assumes Symfony's dependency injection container, bundle configuration, and entity mappings, none of which map onto Laravel's service container, Eloquent models, or HTTP kernel. In-process use inside a Laravel application is therefore a poor architectural fit.
- Can I install gally/gally-standard with Composer inside a Laravel app?
- Installation is technically possible but not advisable. The package pulls a substantial Symfony, Doctrine, and API Platform dependency tree that will coexist awkwardly with the Symfony and PSR contracts Laravel already ships. You would then need a custom service-provider bridge, configuration translation, and auth wiring just to boot it. The effort is high and the reuse is low compared with consuming Gally over HTTP.
- How do I integrate Gally with a Laravel application?
- Treat Gally as a sidecar service: Laravel talks to the Gally API over HTTP or GraphQL using the Laravel HTTP client, and Gally owns indexing, querying, and merchandising rules against Elasticsearch or OpenSearch. Keep catalog and merchandising writes out of the synchronous request path by dispatching Laravel jobs and queues that push data into Gally. Wrap the endpoints behind an interface so the search backend can be swapped later without touching application code.
- Does gally/gally-standard work with Laravel Scout?
- Not out of the box, because Gally is not a Scout engine and gally/gally-standard does not implement Scout's engine contract. A reasonable compromise is a thin custom Scout engine that wraps the Gally API, giving your team a familiar developer interface while Gally remains the search backend. That wrapper is your code to maintain, so budget for it explicitly rather than assuming drop-in Scout support.
- What license does gally/gally-standard use and is it safe for a commercial SaaS?
- The package is released under OSL-3.0, a reciprocal copyleft license with an External Deployment clause that can trigger source-disclosure obligations for modified code offered as a network service. For a closed-source commercial SaaS that is a material legal risk and should go through legal review before any dependency is taken. Depending on your distribution model, API-level integration with an unmodified Gally service may be more defensible than embedding or modifying the code, but confirm that with counsel.
- Which PHP, Symfony, Elasticsearch and Laravel versions does gally/gally-standard support?
- You must verify the supported matrix yourself before committing, since the repository does not publish a clear compatibility table. Check PHP 8.x support, Symfony 6 versus 7 constraints, and whether the target is Elasticsearch 7 or 8 rather than OpenSearch. Any Laravel 10, 11, or 12 compatibility you read about applies only to your client-side HTTP integration, not to the package itself. Pin exact versions because the release cadence is low.
- Does gally/gally-standard require the full Gally core and runtime to work?
- Yes in practice. gally-standard is the data model and configuration layer, so it expects Symfony bundle configuration, Doctrine entity mappings, and API Platform resources to be present. Consuming it standalone as a Laravel library would mean reimplementing large parts of the Gally runtime. The realistic deployment is the complete Gally service running alongside your Laravel application.
- What are good alternatives to gally/gally-standard for search in Laravel?
- If you only need full-text search rather than searchandising, Laravel Scout with Meilisearch, Typesense, Algolia, or an OpenSearch driver is simpler and far better supported in the Laravel ecosystem. Gally only earns its complexity when you genuinely need merchandising rules, boosts, and curated results management. Decide whether search relevance tuning is a core product requirement before adopting a Symfony sidecar.
- Is gally/gally-standard actively maintained and production ready?
- Adoption signals are weak: roughly six stars and zero dependents means it is effectively unproven in the wild, so bus factor and abandonment risk are high. The listed last release date also appears anomalous and should be checked against the actual repository tags before you plan around it. Pin versions, and have a clear answer for who owns upgrades if upstream stalls.
- How should I sync catalog data from Laravel into Gally?
- Make indexing event-driven: Laravel domain events for product and category changes flow onto a queue, and jobs push them to the Gally API with idempotency keys so retries are safe. Add a full-reindex command for recovery and schema changes, and run dual writes during a cutover behind a feature flag. Compare relevance and latency against your existing search before switching traffic.