- Can I use this package with Laravel instead of Symfony? No, this package is built for Symfony 6.2+ and Monofony/Skeleton, not Laravel. It relies on Symfony bundles like SyliusTaxonomyBundle and API Platform, which are incompatible with Laravel’s ecosystem.
- This package is designed exclusively for Symfony-based projects using Monofony/Skeleton. Laravel projects would require a different approach, such as custom Laravel packages or Symfony-to-Laravel bridges, as it leverages Symfony’s bundles, API Platform, and Doctrine migrations.
- What Laravel versions does this package support? It doesn’t support Laravel at all. It’s for Symfony 6.2+ projects only.
- This package is not compatible with Laravel. It is built for Symfony 6.2+ applications using Monofony/Skeleton, which includes Sylius bundles and API Platform. If you need a Laravel-compatible demo backend, explore Laravel-specific packages like Laravel Breeze or custom Sylius-like packages for Laravel.
- How do I install this package in an existing Monofony/Skeleton project? Follow the README’s steps: run `composer require allekslar/monofony-demo-backend`, then execute the post-install script to copy routes, add Sylius bundles to `config/bundles.php`, and run migrations (`doctrine:migrations:diff`, `migrate`, `assets:install`).
- Installation requires running `composer require allekslar/monofony-demo-backend` followed by the post-install script to copy routing files. Next, add `SyliusTaxonomyBundle` and `SyliusLocaleBundle` to `config/bundles.php`. Finally, update your database with `doctrine:migrations:diff` and `migrate`, then install assets with `assets:install`.
- Will this package conflict with existing Sylius bundles in my project? Yes, it may. The package includes SyliusTaxonomyBundle and SyliusLocaleBundle, which could override or conflict with existing configurations. Audit your `config/bundles.php` and Sylius entity mappings before installation.
- This package introduces SyliusTaxonomyBundle and SyliusLocaleBundle, which may conflict with existing Sylius configurations in your project. Before installing, check for overlapping bundle definitions in `config/bundles.php` and review Doctrine entity mappings to avoid naming collisions or duplicate functionality.
- Does this package support GraphQL or only REST APIs? It supports both REST and GraphQL via API Platform 3.0, but GraphQL requires additional configuration.
- The package includes API Platform 3.0, which supports both REST and GraphQL out of the box. However, GraphQL endpoints may need explicit configuration in your `config/packages/api_platform.yaml` to enable the GraphQL bundle and define schemas. REST endpoints are pre-configured and ready to use.
- How do I customize the demo backend for my specific product catalog? Customization requires extending Sylius entities (e.g., Product, Taxon) and overriding workflows in `config/packages/workflow.yaml`. Start by reviewing the Sylius documentation for entity customization and API Platform’s resource configuration.
- To customize the product catalog, extend Sylius entities like `Product` or `Taxon` by creating custom bundles or overriding existing ones. Modify workflows in `config/packages/workflow.yaml` to adjust state machines (e.g., order processing). Use API Platform’s resource configuration to expose or hide fields as needed.
- What Symfony version is required, and will it work with Symfony 7.0? It requires Symfony 6.2.x and is not guaranteed to work with Symfony 7.0 due to potential breaking changes in dependencies like API Platform or Doctrine.
- This package is tested and requires Symfony 6.2.x. Symfony 7.0 may introduce breaking changes in core components or dependencies like API Platform or Doctrine, which could cause compatibility issues. Always test in a staging environment before upgrading.
- How do I handle database migrations if my project already has Doctrine entities? Run `doctrine:migrations:diff` in a staging environment first to preview changes, then resolve conflicts manually. Avoid running migrations directly in production without thorough testing.
- Before applying migrations, run `doctrine:migrations:diff` in a staging environment to identify potential conflicts with existing Doctrine entities. Manually resolve naming clashes or overlapping fields, then test migrations thoroughly. Never run migrations in production without validation.
- Is there a way to use this package without Sylius bundles? No, the package is tightly coupled with SyliusTaxonomyBundle and SyliusLocaleBundle. Removing these dependencies would break core functionality like taxonomies or multilingual support.
- This package depends on SyliusTaxonomyBundle and SyliusLocaleBundle for core features like product categorization and multilingual support. Attempting to remove these bundles would disable critical demo functionality, such as taxonomies or locale management.
- What are the alternatives if I need a Laravel-compatible demo backend? Consider Laravel-specific packages like Laravel Breeze, Jetstream, or custom Sylius-like packages for Laravel (e.g., Spatie’s Laravel packages). For Symfony, explore Sylius standalone or other API Platform-based demos.
- For Laravel, alternatives include Laravel Breeze or Jetstream for authentication and scaffolding, or custom packages like Spatie’s Laravel Media Library for media management. If you’re committed to Symfony, consider Sylius standalone or other API Platform-based demos that don’t rely on Monofony/Skeleton.