- Can I use doyo/alice-bundle in a Laravel application?
- No, doyo/alice-bundle is a Symfony bundle and does not map onto Laravel's container, package auto-discovery, or Artisan command registration. It relies on Doctrine's ObjectManager for persistence, and Eloquent exposes no Doctrine metadata, so an Eloquent persister would have to be written from scratch. For Laravel, use Eloquent model factories with fakerphp/faker instead.
- Does doyo/alice-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony 3/4-era stacks and pins old Symfony constraints rather than Laravel framework versions. It also typically depends on the abandoned fzaninotto/faker rather than fakerphp/faker, so Composer resolution against a modern Laravel matrix is likely to fail. Run a composer why-not audit before spending any engineering time.
- How do I install doyo/alice-bundle?
- You would install it with Composer in a Symfony application, then register the bundle and configure Alice fixture paths. There is no Laravel service provider or auto-discovery support, so composer require alone will not wire it into a Laravel app. In practice, installation in Laravel is not supported and the package is not recommended for that stack.
- What is the Laravel equivalent of doyo/alice-bundle?
- Laravel ships first-party fixture tooling: model factories, DatabaseSeeder, and fakerphp/faker. Together they cover realistic data generation and relationship handling without an adapter. If you specifically need Alice's YAML DSL, adopt nelmio/alice standalone with a hand-written Eloquent persister, and only after proving the DSL earns its keep over factories.
- Does doyo/alice-bundle work with Eloquent models?
- No, it persists fixtures through Doctrine's ObjectManager, and Eloquent models do not expose Doctrine metadata. Supporting Eloquent would require a custom persister written from scratch. That adapter cost sits on top of an unmaintained dependency, which is why the recommendation is to reject it for Eloquent-only codebases.
- Is doyo/alice-bundle actively maintained?
- There is no strong adoption signal: the repository is a vendor/repo mismatch (doyo/alice-bundle pointing at kilip/alice-bundle) with zero stars, zero dependents, and a score of zero. It is best treated as a stale fork of the hautelook/AliceBundle lineage. If you must use it, pin the version, vendor the source, and name a fork owner.
- How does doyo/alice-bundle compare to Laravel model factories?
- Model factories are first-party, upgrade-safe, and integrate directly with Eloquent, DatabaseSeeder, and fakerphp/faker. doyo/alice-bundle offers Alice's YAML/PHP fixture DSL and Faker-powered generation, but only inside Symfony with Doctrine. For a Laravel roadmap the comparison is build-vs-buy-vs-fork against a capability the framework already ships, and factories win on cost and maintenance.
- Can I load YAML fixtures into a Laravel database with doyo/alice-bundle?
- Not directly. The bundle's console command is layered on doctrine:fixtures:load, which Laravel does not provide, and its persistence path expects Doctrine entities. You could theoretically use nelmio/alice standalone to parse YAML and write a custom Eloquent persister, but that is a substitution project, not a package install. Prove the YAML DSL is genuinely required before taking that on.
- What PHP, Symfony, and Doctrine versions does doyo/alice-bundle require?
- It is built for Symfony 3/4-era applications on PHP 7.x with Doctrine, and its Composer constraints typically pin those older ranges. Exact versions should be confirmed with a composer why-not audit against your target PHP and Symfony matrix. That audit is a hard go/no-go gate because dependency resolution alone is likely to terminate the evaluation.
- Is doyo/alice-bundle safe for production data seeding?
- It is a dev/test tool and should never touch staging or production databases. The supply-chain surface from unmaintained transitive test dependencies is a real risk, so isolate it to dev and CI. Write a policy that fixtures are dev/test only and enforce it in code review.