- Can I use javer/influxdb-data-fixtures-bundle in a Laravel application?
- Not directly. It is a Symfony bundle with no Laravel service provider, facade, or config stub; it registers through Kernel::registerBundles() and depends on Symfony's DI container. In a Laravel-only stack you would need to reimplement the Alice loader plus custom InfluxDB persister or run a separate Symfony CLI tool.
- What does javer/influxdb-data-fixtures-bundle actually do?
- It integrates an InfluxDB ODM with Nelmio Alice so YAML or PHP fixture definitions can be loaded and persisted as InfluxDB data points. It is a thin dev and test-time adapter for seeding time-series measurements, not a production runtime library. The real functionality comes from the underlying InfluxDB ODM and Alice.
- How do I install javer/influxdb-data-fixtures-bundle?
- Install it with Composer as a dev dependency in a Symfony project, then register the bundle in Kernel::registerBundles() and configure its extension. There is no Laravel package discovery or artisan command; Laravel users must adapt or reimplement the pattern. Verify dependency conflicts with composer why-not before committing.
- Which InfluxDB versions does this fixture bundle support?
- The bundle sits on an InfluxDB ODM that likely targets InfluxDB 1.x concepts such as databases, retention policies, and line protocol writes. The available context does not establish support for InfluxDB 2.x buckets, orgs, and tokens or for 3.x. Pin your server version and verify the ODM write API before using it.
- Does this package support Laravel 10 or Laravel 11?
- No. It has no Laravel service provider or framework integration, so Laravel 10 and 11 are not supported targets. Its compatibility surface is Symfony bundle registration and Symfony DI conventions instead. For Laravel, use a hand-written InfluxDB seeder with influxdata/influxdb-client-php.
- How do I load InfluxDB fixtures with Nelmio Alice in Symfony?
- Define fixtures in YAML or PHP for Nelmio Alice, then let the bundle's InfluxDB ODM persister write the loaded objects as time-series points. You need a Symfony kernel with the bundle registered and the ODM configured for your server. Expect friction around tags, fields, timestamps, and precision because Alice was designed for relational object graphs.
- Is javer/influxdb-data-fixtures-bundle safe to use in production?
- It is intended for dev and test fixture loading, not production runtime seeding. Fixtures themselves should never be a production dependency, and the bundle has a single maintainer, zero stars, and a last release around January 2024. Treat it as frozen and keep it dev-only if you use it at all.
- What is the best way to seed InfluxDB fixtures in Laravel?
- Reimplement the pattern instead of installing the Symfony bundle: write a Laravel seeder or command that builds points and writes them through influxdata/influxdb-client-php. If you want Alice-style definitions, add a loader that maps fixture data to InfluxDB tags, fields, and timestamps. This avoids inheriting Symfony kernel dependencies and an unmaintained bundle.
- What are the risks of using this bundle in CI?
- The main risks are dependency-graph conflicts from Alice, Symfony FrameworkBundle, and the InfluxDB ODM, plus no community evidence that those constraints resolve cleanly. Pin the InfluxDB server version, test in an isolated branch with composer why-not, and run seeding in an ephemeral container. Gate the CI job so fixture failures do not block unrelated work.
- Are there alternatives to javer/influxdb-data-fixtures-bundle?
- Yes. For Laravel, a custom seeder or command using influxdata/influxdb-client-php is the pragmatic alternative. In Symfony, you can keep Nelmio Alice and write your own InfluxDB persister, or fork the small glue code while pinning the ODM. A hand-written seeder is often simpler than maintaining a zero-star bundle.