- How do I install limenet/laravel-elastica-bridge in a Laravel application?
- Install the package with Composer using composer require limenet/laravel-elastica-bridge, then follow the repository instructions to publish or edit its configuration. Confirm the service provider is registered or auto-discovered, and set your Elasticsearch connection and index options. Run your Laravel config cache commands after configuration changes if your deployment uses config caching.
- What does limenet/laravel-elastica-bridge do?
- It is a simple bridge between Laravel and Elasticsearch that uses the Elastica client. The package wires indices, mappings, connections, and search into Laravel's service container and configuration so they can be managed like other Laravel services. You can query Elasticsearch through Elastica's fluent API while keeping index settings in Laravel config.
- How do I configure Elasticsearch indices and mappings with this package?
- Configuration is handled through the package's Laravel config files, where you define connections and index settings such as mappings. The bridge then exposes those settings through Laravel's container so your application can resolve the Elastica client and use it for searches. Publish or edit the config and clear or rebuild Laravel's config cache after changes.
- Which Laravel and PHP versions does limenet/laravel-elastica-bridge support?
- The provided evaluation is based only on the v2.2.0 release note and does not include a supported-version matrix. Check the repository README and composer.json for the exact Laravel, PHP, Elastica, Elasticsearch, and Sentry SDK constraints before installing or upgrading. Do not assume compatibility with a specific Laravel version until those constraints are confirmed.
- How do I set the Elasticsearch log level in v2.2.0?
- Use the elastica-bridge.logging.level configuration key or the ELASTICSEARCH_LOG_LEVEL environment variable. The setting is opt-in and defaults to debug, so existing behavior is preserved unless you raise it. The release note does not document validation for invalid values, so use a known log level and verify the resolved value after config caching.
- Is ELASTICSEARCH_LOG_LEVEL safe to use with php artisan config:cache?
- Treat it like any Laravel env-backed configuration value: Laravel reads it when building the cached config, and later env changes require rerunning php artisan config:cache. The evaluation flags the difference between the package config key and the env var name as a configuration-ambiguity risk. Test the resolved value in staging with config caching enabled before relying on it in production.
- What are the production risks of leaving Elasticsearch logging at debug?
- At debug level, Elasticsearch request and response bodies can be logged, which may increase memory use and expose sensitive payloads when Sentry breadcrumbs are enabled. Raising elastica-bridge.logging.level can reduce memory pressure and breadcrumb volume, but it also reduces diagnostic visibility. The provided evaluation does not document a specific payload-size or memory threshold for changing the default.
- Does elastica-bridge.logging.level affect only Sentry breadcrumbs or all package logging?
- The provided evaluation describes the setting in the context of optional Sentry breadcrumb logging. It notes that it is unclear whether raising the level affects only Sentry breadcrumbs or also application and package logging. Review the package source or test the behavior before assuming the setting limits all Elasticsearch log output.
- Are Elasticsearch request and response bodies redacted before being sent to Sentry?
- Redaction and truncation behavior is not documented in the provided release-note-based evaluation. Because debug-level logging may include full request and response bodies, treat those payloads as potentially sensitive. Confirm redaction and truncation in the package source, and raise the log level if full bodies should not reach Sentry breadcrumbs.
- Is limenet/laravel-elastica-bridge still maintained, and what alternatives exist?
- The v2.2.0 release is described as a non-breaking minor update that adds a configuration-only logging-level setting, which suggests low ongoing maintenance for current users. Maintenance status still depends on the repository's recent commits, issue activity, and supported-version matrix. Alternatives include using the official Elasticsearch PHP client directly, Elastica without the Laravel bridge, or Laravel Scout with a compatible Elasticsearch driver.