- Does goldenline/algolia-bundle work with Laravel?
- No. goldenline/algolia-bundle is a Symfony bundle: its class extends Symfony's Bundle base class and it wires services through a DependencyInjection Extension and a Configuration tree, none of which Laravel boots. Composer will install it into a Laravel project, but no service provider is registered and no runtime behaviour appears. Making it work would mean hand-writing a Laravel service provider that rebuilds the bundle's internal service graph, which is effectively a fork of an unmaintained package.
- Is goldenline/algolia-bundle still maintained?
- There is no meaningful evidence of maintenance. The repository has zero stars, zero dependents, and no community validation, which usually signals an abandoned package. GoldenLine's public repositories of this vintage are largely dormant, and the bundle appears to predate the official algolia/search-bundle that now occupies this niche. Treat it as a reference read rather than a dependency.
- What PHP and Symfony versions does goldenline/algolia-bundle require?
- Expect legacy constraints along the lines of php >=5.5 or ^7.0 and symfony/framework-bundle ^2.8 or ^3.0, typical of a bundle from that era. Modern Laravel 10 and 11 applications require PHP 8.1+ and Symfony 6.x components, so the requirements collide. Forcing the install with --ignore-platform-reqs only ships code that was never executed on the runtime you would deploy.
- What is the best Algolia package for Laravel?
- The idiomatic path is Laravel Scout with the official Algolia driver, which gives you model-driven indexing, searchable attributes, and queue-friendly syncing. If you need richer indexing semantics, algolia/scout-extended layers additional features on top of Scout. Both are maintained and integrate with Laravel's service container and queue system out of the box, none of which goldenline/algolia-bundle can offer.
- How is goldenline/algolia-bundle different from the official algolia/search-bundle?
- Both target Symfony rather than Laravel, but the official algolia/search-bundle is the actively maintained successor and covers the same integration ground. goldenline/algolia-bundle is an earlier, unmaintained attempt whose only real value was the container wiring, not the search logic. If your target application is Symfony, choose the official bundle; if it is Laravel, neither is the right answer.
- Can I use the Algolia PHP SDK directly in Laravel without a bundle?
- Yes, and for a Laravel application that is a reasonable option. You can bind algolia/algoliasearch-client-php as a singleton in a service provider and inject it wherever you need to push records or run queries. Note that the client went through breaking major versions, with v3 introducing a generated per-operation API that drops the legacy AlgoliaSearch\Client surface. A thin wrapper around the current SDK is roughly the same effort as porting this bundle, but with a maintained foundation underneath.
- How do I install and configure goldenline/algolia-bundle in a Symfony application?
- In Symfony the bundle is enabled through the kernel's bundle registration and configured through the Configuration tree its DependencyInjection Extension exposes, with services registered automatically by the container. That model is exactly why it cannot be dropped into Laravel, which has no bundle discovery, no Extension, and no config tree loader. Verify the licence file exists and is compatible with your distribution model before evaluating further.
- Will Composer install goldenline/algolia-bundle into a Laravel 10 or 11 project?
- Composer may resolve and install the archive, but success at the install step means nothing here. Its PHP and symfony/framework-bundle constraints typically conflict with the PHP 8.1+ and Symfony 6.x requirements of modern Laravel, so resolution often fails outright. If it does install, you are left with a dead dependency in vendor/ that registers no providers, no config, and no commands.
- How do I test Algolia search and indexing in a Laravel application?
- Test against an abstraction rather than the real service, so indexing and query calls can be faked or mocked without network access. Laravel Scout's engine abstraction lets you swap in a fake or mock the Algolia client in your test suite, and queued indexing can be asserted with the standard queue fakes. goldenline/algolia-bundle provides no Laravel testing hooks at all, so it offers nothing here.
- How do I migrate from goldenline/algolia-bundle to Laravel Scout?
- Because the bundle registers nothing in Laravel, there is usually no runtime behaviour to migrate, only the requirements it was shortlisted to satisfy. Specify what you actually needed, such as custom index naming, tenant scoping, or queued indexing, then implement those on Scout with the Algolia driver or algolia/scout-extended. Writing those requirements down first prevents the same category mismatch from recurring with the next package.