- How do I install gally/gally-sample-data in a Laravel project?
- Add the package with Composer as a require-dev dependency in the Laravel application that hosts your Gally instance. Then run Gally's install and migration steps, execute the seed or import command the package ships with, and build the Elasticsearch or OpenSearch indices. A developer familiar with Laravel can usually reach a working demo search in a few hours. Pin the package to the exact Gally core version you are running before you seed.
- Is gally/gally-sample-data safe to use in production?
- No. It is a fixture and demo-data package, not a production data path, and it should be treated as a require-dev concern. The seed command is easy to invoke and can overwrite or pollute shared or staging environments. Use it for local bootstrap, CI fixtures, and demos only, and isolate invocation to those profiles.
- Which PHP and Gally versions does gally/gally-sample-data support?
- The package targets PHP 8.x and a Laravel-based Gally install backed by MySQL or PostgreSQL for metadata and Elasticsearch or OpenSearch for indices. There is no broad version contract published, and the fixtures are tightly bound to Gally core index mappings and entity schemas. Verify the composer.json constraints against your PHP and Gally core versions, and pin to the exact core version in use. Any Gally upgrade can silently break seeds or produce documents that no longer match your templates.
- What data does gally/gally-sample-data actually seed?
- It populates a Gally index with a small synthetic catalog: demo products, categories, and attributes, plus likely merchandising rules so search, facets, and rules can be exercised immediately. Confirm which entity types your installed version covers, including whether it ships index mappings and templates or only documents. Because the fixture set is small and synthetic, it will not surface performance, relevance-at-scale, or long-tail taxonomy problems.
- Is seeding idempotent, and is there a documented teardown or reset path?
- There is no community-verified evidence of idempotency or a documented teardown command, so assume neither until you test it. Run seeding only against disposable local or CI databases, and capture the Gally index names beforehand so you can rebuild or drop them. If you need repeatable runs, wrap the seed step in your own reset script that recreates indices before importing.
- Can I use gally/gally-sample-data for CI and automated relevance testing?
- Yes, this is one of its strongest use cases. It gives you deterministic fixtures for search-relevance and rule-engine regression tests without needing a real catalog or PIM connection in the pipeline. Pin the Elasticsearch or OpenSearch major version in CI too, because analyzer and mapping behavior differ across majors and can change relevance results.
- What license does gally/gally-sample-data use, and can I fork it?
- It is released under OSL-3.0, a reciprocal weak copyleft license. Internal use is generally fine, but distributing modified versions triggers source-disclosure obligations. If you plan to fork or redistribute the fixtures, route it through legal first.
- Is gally/gally-sample-data actively maintained?
- There is essentially no external validation: zero stars, zero dependents, and single-vendor ownership, with a health score around 20 out of 100. The last-release timestamp appears to reflect automated mirroring or CI tagging rather than a curated release cadence. Verify that published tags map to real, tested Gally versions before adopting, and ask the vendor about their support model and release cadence for this package specifically.
- Does gally/gally-sample-data work with both Elasticsearch and OpenSearch?
- Gally targets Elasticsearch or OpenSearch for indexing, so the sample data is written against whichever engine your Gally install uses. The mappings and templates come from Gally core, not from the fixtures, so a mismatch shows up as mapping conflicts or silently dropped fields. Pin your engine major version explicitly, since analyzers and mapping behavior change between majors.
- What should I use instead of gally/gally-sample-data to load a real catalog?
- For real ingestion, use Gally's connectors such as the PrestaShop or Magento modules, or its REST ingestion API. Plan a separate workstream with its own mapping, validation, and relevance QA, because the sample package is not a catalog migration or import tool. Treat the sample fixtures as a way to shorten time-to-first-search during evaluation, then migrate to a proper ingestion pipeline before going live.