Weave Code
Service Bundle Laravel Package
retailcrm/service-bundle
Symfony bundle for integrating RetailCRM into your application. It wires the RetailCRM API client into Symfony's service container, provides configuration, and offers convenient services for working with orders, customers, catalogs, and reference data.
Core bundle for RetailCRM integration services
Frequently asked questions about Service Bundle
- Is retailcrm/service-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It registers through Symfony's bundle system and its configuration and dependency injection container, and the documented integration path is Symfony only. Laravel teams can still evaluate it, but do not expect a Laravel service provider, facade, or config/app.php registration. Treat any Laravel adoption as custom integration work rather than a drop-in Composer install.
- How do I install retailcrm/service-bundle with Composer?
- Install it with composer require retailcrm/service-bundle and pin the exact tag, such as v1.0.6, for a first adoption. Because the v1.0.6 release notes were empty, capture the resolved dependency graph with composer why output before merging. Commit composer.lock so the graph is reproducible across environments. In a Laravel app the package will not be auto-discovered as a bundle, so expect extra wiring.
- Does retailcrm/service-bundle support Laravel package auto-discovery?
- No. Laravel auto-discovery depends on a service provider declared in the package's composer.json extra.laravel block, and this package is built as a Symfony bundle instead. You would need to write your own service provider and bind the RetailCRM client yourself. Verify this by reading the package's composer.json before you plan any work.
- How do I configure RetailCRM API credentials per environment?
- The bundle is designed around Symfony configuration with environment-specific credentials rather than committed secrets. In Laravel the equivalent pattern is environment variables read through config files, with the client bound in a service provider and cached via config:cache. Never edit files inside vendor to change credentials, since those edits are lost on the next composer update. Keep production keys out of version control and load them from your deployment environment.
- Which RetailCRM features does the bundle expose as services?
- The package description points to convenient services for working with orders, customers, catalogs, and reference data, plus a preconfigured RetailCRM API client. The exact service identifiers and method coverage are not detailed in the supplied README excerpt, so confirm them against the source before depending on them. Boundary-level HTTP services like these carry far less upgrade risk than anything decorating the ORM or the container.
- Does retailcrm/service-bundle support dependency injection and autowiring?
- Yes, dependency injection and autowiring support are part of the stated feature set, alongside preconfigured RetailCRM client and service definitions. In Symfony this works through the bundle's service configuration without manual wiring. In Laravel you would recreate equivalent bindings in a service provider and check for registration-order conflicts with your existing providers.
- What Laravel and PHP versions does retailcrm/service-bundle support?
- The provided context does not state supported Laravel or PHP ranges, so read the composer.json constraints and run a resolution spike in a throwaway branch. Do not judge compatibility from the constraint string alone, because Composer can resolve a compatible graph while runtime behaviour still breaks on an untested PHP minor. A one-minor mismatch is a normal accommodation; a two-minor gap usually means you are adopting an unmaintained branch.
- Does the bundle publish migrations or modify my database?
- Nothing in the description indicates that the bundle publishes migrations; it is presented as a lightweight integration for existing applications. Confirm this in the source before deploying, because any migration that runs in production is effectively irreversible. If migrations do exist, require them to be additive-only and forward-only with a tested rollback, and do not alter existing tables in the first deploy.
- How can I test the RetailCRM integration safely?
- Point the client at a sandbox account or mocked HTTP layer instead of production credentials, and boot the application both with and without cached config. Caching masks discovery and binding problems locally that then surface in production. Roll it out behind a feature flag in one non-critical path and widen only after a full release cycle of clean operation.
- Is retailcrm/service-bundle actively maintained, and what are the alternatives for Laravel?
- The context shows v1.0.6 under consideration with empty release notes, so release cadence, maintainer count, and security disclosure process are unverified and should be checked on the repository. A package with a single maintainer and no release in twelve months is a fork-and-own decision rather than an adoption decision. For Laravel, the more natural alternative is a package that ships a service provider, config publishing, and Laravel version constraints you can test against; compare dependency weight and supported Laravel minors before choosing.
Weaver
How can I help you explore Laravel packages today?