- What is baks-dev/ozon-support actually used for?
- It registers an Ozon Support user profile type inside an application that already runs the BaksDev users subsystem, so support contexts can be classified as Ozon-related. It is a small plumbing and classification module, not an Ozon marketplace or Seller API client. No OAuth2, order, refund, inventory, webhook or payment logic is documented in the repository.
- Is baks-dev/ozon-support a Laravel package or a Symfony bundle?
- The documented install and test commands are Symfony-shaped: php bin/console and php bin/phpunit, not artisan. The README does not describe a Laravel service provider or a configuration publish step. If you are on Laravel, verify the composer.json requires and check whether it pulls the wider BaksDev footprint before committing.
- How do I install baks-dev/ozon-support?
- Run composer require baks-dev/ozon-support, then execute php bin/console baks:users-profile-type:ozon-support to register the Ozon Support profile type. Skipping that command leaves the module effectively inert. Afterward, run the test group with php bin/phpunit --group=ozon-support to confirm the environment is wired correctly.
- What PHP version does baks-dev/ozon-support require?
- The package declares a hard PHP 8.4+ floor. That constrains hosting, CI base images and any legacy services in the estate. Confirm every environment where the host application runs can meet that minimum before adopting.
- Does baks-dev/ozon-support talk to the Ozon Seller API?
- There is no evidence in the README or the artifacts of outbound Ozon calls, OAuth2 flows, order or refund services, inventory sync, webhooks, Ozon Pay or delivery integration. Treat any claim of marketplace capability as unverified until you prove it in a spike. If your actual goal is selling on Ozon, this package does not address it and that integration should be scoped separately.
- How do I run the tests for baks-dev/ozon-support?
- Use php bin/phpunit --group=ozon-support as documented in the README. Note there is no CI badge, no visible pipeline and no integration tests against a live Ozon surface, so a green local run only proves the unit-level group passes. Add your own smoke test around the profile-type registration command.
- What are the dependencies of baks-dev/ozon-support?
- The README does not list them, so you must audit composer.json for require and conflict entries. The package is a satellite of the BaksDev ecosystem and assumes a pre-existing users and profile-type subsystem plus a Symfony-style console. Installing it may force a wider BaksDev footprint, so check before making a planning commitment.
- Is baks-dev/ozon-support production-ready and maintained?
- Adoption signals are weak: zero stars, zero dependents, no changelog, no community and a roughly 20-line README. The MIT license makes it forkable and there is no vendor lock-in, which limits the downside. Treat it as high adoption risk and budget for vendoring or a fork if you come to depend on it.
- What changed in versions 7.4.13 to 7.4.17 of baks-dev/ozon-support?
- The releases only repeat the version string, so there is no bugfix, feature or breaking-change signal. The numbering appears to track a monorepo lockstep rather than semantic versioning of this module alone. Ask the author directly for a backwards-compatibility policy before upgrading in production.
- What are the alternatives to baks-dev/ozon-support?
- If you already run BaksDev, this is the natural way to register an Ozon support profile type, so the realistic alternative is a small in-house migration. If you need an Ozon Seller or marketplace API client, look at dedicated Ozon SDKs instead, because this package does not cover orders, refunds, stock or webhooks. For a generic Laravel application with no BaksDev stack, the honest recommendation is not to adopt.