- How do I install baks-dev/wildberries-manufacture in a Laravel application?
- Install the package with Composer by running composer require baks-dev/wildberries-manufacture. The package requires PHP 8.4 or newer. After installation, run php bin/console baks:assets:install to install configuration and file assets, then apply the Doctrine migrations for the module.
- Which Laravel and PHP versions are supported by baks-dev/wildberries-manufacture?
- The README states a minimum of PHP 8.4, and the package uses Symfony Console, Doctrine Migrations, and PHPUnit. The README does not explicitly pin a Laravel version, so check the composer.json constraints and test against your target Laravel release before adopting it. A sandbox install is the safest way to confirm compatibility with your application.
- How do I install the configuration and assets for the Wildberries manufacture module?
- Run php bin/console baks:assets:install as shown in the README. This installs the package configuration and file resources needed by the module. Keep these resources isolated in a dedicated namespace or path so they do not conflict with existing Laravel configuration or public assets.
- How do I run database migrations for baks-dev/wildberries-manufacture?
- Use php bin/console doctrine:migrations:diff to generate schema changes, then php bin/console doctrine:migrations:migrate to apply them. Review the generated migrations before running them in production because the package may add or alter tables related to Wildberries order production. Back up your database and plan a rollback strategy before migrating an existing application.
- How do I test baks-dev/wildberries-manufacture?
- The README provides php bin/phpunit --group=wildberries-manufacture for the package test group. That scope appears limited to PHPUnit tests, so add your own integration tests around order production workflows. Mock Wildberries API calls where possible to avoid relying on live external services during testing.
- Which Wildberries APIs does this package call?
- The README does not document which Wildberries APIs the package interacts with, and the evaluation flags this as an integration risk. Ask the maintainer for API specifications or inspect the source to identify endpoints and data contracts. Mock external calls in tests and monitor for Wildberries API changes that could break production workflows.
- Is baks-dev/wildberries-manufacture safe to use in production?
- It can be viable for production if you review the Doctrine migrations, configuration, and asset installation carefully first. The package is specialized for Wildberries order manufacturing and may depend on undocumented Wildberries APIs, so add error handling, retries, and logging around production workflows. Monitor maintenance activity and test upgrades in a staging environment before deploying.
- Can I customize Wildberries production workflows or add hooks without forking the package?
- The README does not document extension points, hooks, or workflow customization. The package appears self-contained, so you may need to override Laravel service bindings or inspect the source for injectable services. If you need significant custom behavior, evaluate whether a thin wrapper or a fork is more maintainable.
- Does baks-dev/wildberries-manufacture support batch processing, retries, rate limits, or error handling?
- The provided documentation does not describe batch processing, retry logic, rate-limit handling, or detailed error behavior. For high-volume Wildberries order production, test throughput and add your own queueing, retry, and monitoring layers as needed. Confirm API failure behavior with the maintainer or by reviewing the source.
- What are the alternatives and maintenance concerns for baks-dev/wildberries-manufacture?
- There is no standard alternative named in the README; the main options are this package, a custom Wildberries API integration, or an official Wildberries client combined with your own manufacturing workflow. The package is MIT licensed and currently listed at version 7.4.19. Because it is a specialized module, monitor releases for compatibility and be prepared to fork if maintenance slows.