- What Laravel versions does this package support, and will it work with Laravel 10?
- The package officially targets Laravel 7.4+, but due to Symfony 5.x dependencies, it may conflict with Laravel 8+ or later. Testing on Laravel 10 is unconfirmed, and the PHP 8.4+ requirement could introduce compatibility issues with newer Laravel releases. Check the GitHub issues for updates or consider a hybrid Doctrine/Eloquent approach if upgrading.
- How do I install and configure the package for production?
- Run `composer require baks-dev/yandex-market baks-dev/yandex-market-products`, then execute `php bin/console baks:assets:install` to set up configs and assets. Use `doctrine:migrations:diff` and `doctrine:migrations:migrate` for database schema updates. Ensure your `.env` includes Yandex Market API credentials, but note the package lacks explicit `.env` variable documentation for sensitive keys.
- Can I use this package with Eloquent instead of Doctrine ORM?
- No, the package is tightly coupled with Doctrine ORM for migrations and entities. To use Eloquent, you’d need to manually map Doctrine schemas to Eloquent models or adopt a hybrid ORM approach, which may require significant refactoring. The package does not provide Eloquent model stubs or migration tools.
- What PHP version is required, and why does it enforce PHP 8.4+?
- The package mandates PHP 8.4+ due to dependencies like Symfony 5.x and potential use of PHP 8.4 features (e.g., named arguments, new attributes). If your project uses PHP 8.2/8.3, you’ll face deprecation risks or may need to fork the package. The requirement also limits compatibility with older Laravel versions.
- How do I generate the Yandex Market YML feed for my products?
- The package likely includes YML generation via Artisan commands (check `baks:assets:install` or custom commands). Ensure your Doctrine entities are properly configured with product attributes (e.g., `price`, `availability`). Test the output with Yandex Market’s validation tool before full deployment, as malformed YML can cause sync failures.
- Are there performance concerns for large catalogs (e.g., 50K+ products)?
- The package’s performance for large catalogs is untested in public benchmarks. Batch processing may be required for sync operations to avoid timeouts or memory issues. Monitor PHP error logs for `Allowed memory exhausted` errors and consider splitting syncs into smaller batches or optimizing Doctrine queries.
- What alternatives exist if this package isn’t a good fit?
- For lightweight Yandex Market integration, use the official [Yandex Market API](https://yandex.ru/dev/market/doc/dg/concepts/about-docpage/) directly with a custom Laravel service. Commercial alternatives like Webasyst or Bitrix24 offer pre-built solutions but may lack Laravel-native flexibility. Open-source options like `spatie/laravel-yandex-market` (if available) could be simpler for basic needs.
- How do I handle API rate limits or failed syncs in production?
- The package does not explicitly document rate limit handling, so implement retry logic with exponential backoff in your Artisan commands or cron jobs. Log failed syncs using Laravel’s logging system and set up alerts for repeated failures. Consider caching API responses to reduce call frequency during peak times.
- Is the package actively maintained, and where can I get support?
- As of the last release (placeholder: 2026-07-03), maintenance status is unclear due to lack of stars/contributors. Check the GitHub repository for open issues or contact the author via the README’s provided channels. No paid support or community forums are advertised, so expect slower responses for critical bugs.
- How do I migrate existing product data to this package’s schema?
- Use Doctrine migrations to adapt your current schema, but manual mapping may be needed for custom fields. Test migrations in a staging environment first, as data loss risks exist if relationships or constraints aren’t aligned. The package lacks built-in data import tools, so consider writing a custom seeder or script to transform legacy data.