Weave Code
Socom Bundle Laravel Package
mobiledev-pro/socom-bundle
mobiledev-pro/socom-bundle is a Composer-installable Laravel/PHP bundle that packages SOCoM functionality into a reusable dependency. Add it to your project to simplify integration, then check the repository for setup, configuration, and usage details.
mobiledev-pro/socom-bundle packages SOCOM-related services into a single, drop-in PHP bundle, so you can wire configuration, service definitions and shared helpers without duplicating boilerplate across projects. It follows standard bundle conventions, letting Composer autoloading and container registration do the heavy lifting while you focus on application logic.
- PSR-4 autoloaded classes under a predictable namespace
- Centralized configuration that can be published and overridden per project
- Service container registration through one bundle entry point
- Dependencies declared and resolved via Composer
- Small footprint with no framework lock-in
Frequently asked questions about Socom Bundle
- Can I install mobiledev-pro/socom-bundle in a Laravel application?
- No. MDSocomBundle is a Symfony bundle with no Laravel service provider, facade, or publishable config, so Laravel's bootstrap never registers it. Even if Composer resolves symfony/framework-bundle alongside Laravel, booting a Symfony kernel inside a Laravel request risks container collisions, error-handler takeover, and config-cache path conflicts. Treat the bundle as a specification and re-implement a first-party integration instead.
- Is mobiledev-pro/socom-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. The repository is MDSocomBundle, and it depends on Symfony's kernel bundle-registration phase, DI extension classes, and Resources/config/services.yaml. None of those mechanisms exist in Laravel's Illuminate\Foundation\Application bootstrap, so out-of-the-box Laravel fit is effectively zero.
- How do I install mobiledev-pro/socom-bundle with Composer?
- First verify where it lives: Packagist, a private Satis repository, or GitHub only. Check the composer.json name, the require block (php, symfony/framework-bundle, ext-soap or ext-com, PSR dependencies), and the PSR-4 map. There is a single release dated 2024-08-28, so confirm dist archives and semver tags exist before relying on composer require.
- Which Laravel and PHP versions work with mobiledev-pro/socom-bundle?
- The bundle was published in August 2024, so it most likely targets Symfony 6.4 or 7.x rather than any Laravel release. Laravel 11 and 12 pin their own symfony/* minor versions, so transitive conflicts are plausible and may surface during a framework upgrade. Plan for PHP 8.2+ and confirm ext-* requirements before estimating effort.
- What is SOCOM and which protocol does the bundle use?
- SOCOM is not publicly documented; the description only says the bundle serves MobileDev's specific needs. It could be an internal system, a third-party SaaS, a SOAP/WSDL service, or Windows COM. If it touches Windows COM, it is a hard no for Linux containers; if it is SOAP, expect ext-soap and brittle deserialization on PHP 8.2+.
- How do I port mobiledev-pro/socom-bundle logic to Laravel?
- Read the bundle as a specification, extract the outbound calls and DTOs, and re-implement a first-party client behind a SocomClient interface. Add a SocomServiceProvider with mergeConfigFrom for config/socom.php, and use Http::withToken() or SoapClient behind the interface. Preserve the vendor's request/response DTOs and validation rules verbatim to hold wire compatibility, and rewrite only the framework glue.
- Does mobiledev-pro/socom-bundle have tests or CI?
- No published test suite is visible, so treat all behavior as unverified until you write tests. Record real SOCOM requests and responses and use them as golden-file contract tests around your Laravel client. If there is a commercial relationship with MobileDev-pro, ask whether the vendor runs its own CI and can share fixtures.
- Is mobiledev-pro/socom-bundle safe for production use?
- It is an early-stage package with 0 stars, 0 dependents, a single release, and bus factor 1, with no CVE watch or security advisories upstream. The MIT license removes legal lock-in because you can fork it. There are no field-tested edge cases beyond the vendor's own deployment, so evaluate carefully and never assume upstream triage.
- What are the alternatives to mobiledev-pro/socom-bundle for Laravel?
- Build a first-party integration under app/Integrations/Socom or as a private Composer package. Laravel's Http client, explicit DTOs or JsonResource, and Log facade cover the Symfony HttpClient, Serializer, and Monolog equivalents. The reusable asset is the endpoint, auth, payload contract, and error codes, which survive repackaging unchanged even though the bundle's packaging does not.
- How is mobiledev-pro/socom-bundle maintained?
- Maintenance is unclear: one release on 2024-08-28, no visible cadence, no dependents, and a single-vendor bus factor. Check the commit history and semver tags before committing. Because the license is MIT, forking into your own private package is a viable fallback if the vendor goes quiet.
Weaver
How can I help you explore Laravel packages today?